Home
last modified time | relevance | path

Searched refs:safe (Results 1 – 25 of 357) sorted by relevance

12345678910>>...15

/Linux-v5.4/arch/arm/common/
Ddmabounce.c55 void *safe; member
136 buf->safe = dma_pool_alloc(pool->pool, GFP_ATOMIC, in alloc_safe_buffer()
139 buf->safe = dma_alloc_coherent(dev, size, &buf->safe_dma_addr, in alloc_safe_buffer()
143 if (buf->safe == NULL) { in alloc_safe_buffer()
198 dma_pool_free(buf->pool->pool, buf->safe, buf->safe_dma_addr); in free_safe_buffer()
200 dma_free_coherent(device_info->dev, buf->size, buf->safe, in free_safe_buffer()
262 buf->safe, buf->safe_dma_addr); in map_single()
267 __func__, ptr, buf->safe, size); in map_single()
268 memcpy(buf->safe, ptr, size); in map_single()
283 buf->safe, buf->safe_dma_addr); in unmap_single()
[all …]
/Linux-v5.4/drivers/usb/serial/
Dsafe_serial.c75 static bool safe = true; variable
85 module_param(safe, bool, 0);
86 MODULE_PARM_DESC(safe, "Turn Safe Encapsulation On/Off");
196 if (!safe) in safe_process_read_urb()
232 trailer_len = safe ? 2 : 0; in safe_prepare_write_buffer()
236 if (!safe) in safe_prepare_write_buffer()
/Linux-v5.4/Documentation/i2c/
Ddma-considerations.rst11 Therefore, it is *not* mandatory that the buffer of an I2C message is DMA safe.
13 rarely used. However, it is recommended to use a DMA-safe buffer if your
19 safe buffers always, because USB requires it.
24 For clients, if you use a DMA safe buffer in i2c_msg, set the I2C_M_DMA_SAFE
33 SMBus transactions via I2C, the buffers for block transfers are DMA safe. Users
34 of i2c_master_send() and i2c_master_recv() functions can now use DMA safe
36 know their buffers are DMA safe. Users of i2c_transfer() must set the
42 Bus master drivers wishing to implement safe DMA can use helper functions from
43 the I2C core. One gives you a DMA-safe buffer for a given i2c_msg as long as a
/Linux-v5.4/fs/ntfs/
DKconfig9 safe, write support available. For write support you must also
28 Linux on your computer it is safe to say N.
56 This enables the partial, but safe, write support in the NTFS driver.
66 damaged someones data so we assume it is perfectly safe to use.
68 Note: While write support is safe in this version (a rewrite from
71 is not safe.
79 It is perfectly safe to say N here.
/Linux-v5.4/Documentation/scsi/
Ddc395x.txt7 be safe to use. Testing with hard disks has not been done to any
28 - safe
31 If safe is set to 1 then the adapter will use conservative
32 ("safe") default settings. This sets:
88 dc395x. (eg "dc395x.safe=1")
/Linux-v5.4/drivers/ide/
Dtx4938ide.c62 u8 safe = drive->pio_mode - XFER_PIO_0; in tx4938ide_set_pio_mode() local
67 safe = min_t(u8, safe, pair->pio_mode - XFER_PIO_0); in tx4938ide_set_pio_mode()
68 tx4938ide_tune_ebusc(pdata->ebus_ch, pdata->gbus_clock, safe); in tx4938ide_set_pio_mode()
/Linux-v5.4/drivers/parport/
DKconfig32 and it is safe to compile all the corresponding drivers into the
84 is safe to say N.
100 called parport_ip32. If in doubt, saying N is the safe plan.
109 called parport_amiga. If in doubt, saying N is the safe plan.
118 parport_mfc3. If in doubt, saying N is the safe plan.
127 called parport_atari. If in doubt, saying N is the safe plan.
161 appear in /proc/sys/dev/parport/*/autoprobe*. It is safe to say N.
/Linux-v5.4/drivers/gpu/drm/omapdrm/
Dtcm.h325 #define tcm_for_each_slice(var, area, safe) \ argument
326 for (safe = area, \
327 tcm_slice(&safe, &var); \
328 var.tcm; tcm_slice(&safe, &var))
/Linux-v5.4/drivers/gpu/drm/ttm/
Dttm_execbuf_util.c122 struct ttm_validate_buffer *safe = entry; in ttm_eu_reserve_buffers() local
124 list_del(&safe->head); in ttm_eu_reserve_buffers()
125 list_add(&safe->head, dups); in ttm_eu_reserve_buffers()
/Linux-v5.4/net/ax25/
DTODO2 listen_lock have to be bh-safe?
4 Do the netrom and rose locks have to be bh-safe?
/Linux-v5.4/drivers/of/
DKconfig26 If unsure, say N here, but this option is safe to enable.
36 If unsure, say N here, but this option is safe to enable.
55 # Hardly any platforms need this. It is safe to select, but only do so if you
/Linux-v5.4/drivers/staging/wusbcore/
DKconfig14 To compile this support select Y (built in). It is safe to
28 It is safe to select even if you don't have a compatible
/Linux-v5.4/drivers/staging/uwb/
DKconfig42 is safe to select any even if you do not have the hardware.
58 is safe to select any even if you do not have the hardware.
70 is safe to select any even if you do not have the hardware.
/Linux-v5.4/fs/dlm/
Drequestqueue.c156 struct rq_entry *e, *safe; in dlm_purge_requestqueue() local
159 list_for_each_entry_safe(e, safe, &ls->ls_requestqueue, list) { in dlm_purge_requestqueue()
/Linux-v5.4/Documentation/locking/
Dlockdep-design.rst114 A lock is irq-safe means it was ever used in an irq context, while a lock
121 <hardirq-safe> or <hardirq-unsafe>
122 <softirq-safe> or <softirq-unsafe>
124 This is because if a lock can be used in irq context (irq-safe) then it
156 <hardirq-safe> -> <hardirq-unsafe>
157 <softirq-safe> -> <softirq-unsafe>
159 The first rule comes from the fact that a hardirq-safe lock could be
161 thus could result in a lock inversion deadlock. Likewise, a softirq-safe
172 - if a new hardirq-safe lock is discovered, we check whether it
175 - if a new softirq-safe lock is discovered, we check whether it took
[all …]
/Linux-v5.4/arch/powerpc/platforms/52xx/
DKconfig20 gpt nodes, then it is safe to use such gpt to reset the board,
56 It is safe to say 'Y' here
/Linux-v5.4/Documentation/devicetree/bindings/power/supply/
Dqcom_smbb.txt62 - qcom,fast-charge-safe-voltage:
65 Description: Maximum safe battery voltage; May be pre-set by bootloader, in
69 - qcom,fast-charge-safe-current:
72 Description: Maximum safe battery charge current; May pre-set by bootloader,
/Linux-v5.4/drivers/clocksource/
Dem_sti.c254 int safe; in em_sti_clock_event_next() local
257 safe = em_sti_count(p) < (next - 1); in em_sti_clock_event_next()
259 return !safe; in em_sti_clock_event_next()
/Linux-v5.4/scripts/coccinelle/free/
Ddevm_free.cocci60 @safe depends on context || org || report exists@
115 position p != safe.p;
/Linux-v5.4/drivers/input/gameport/
Dns558.c258 struct ns558 *ns558, *safe; in ns558_exit() local
260 list_for_each_entry_safe(ns558, safe, &ns558_list, node) { in ns558_exit()
/Linux-v5.4/Documentation/devicetree/bindings/dma/
Dti-dma-crossbar.txt16 - ti,dma-safe-map: Safe routing value for unused request lines
52 ti,dma-safe-map = <0>;
/Linux-v5.4/Documentation/devicetree/bindings/arm/omap/
Dcrossbar.txt27 - ti,irqs-safe-map: integer which maps to a safe configuration to use
/Linux-v5.4/Documentation/ABI/obsolete/
Dsysfs-firmware-acpi8 enabling this knob is not safe and thus unsupported.
/Linux-v5.4/net/batman-adv/
Dtranslation-table.c469 struct batadv_tt_change_node *tt_change_node, *entry, *safe; in batadv_tt_local_event() local
489 list_for_each_entry_safe(entry, safe, &bat_priv->tt.changes_list, in batadv_tt_local_event()
996 struct batadv_tt_change_node *entry, *safe; in batadv_tt_tvlv_container_update() local
1026 list_for_each_entry_safe(entry, safe, &bat_priv->tt.changes_list, in batadv_tt_tvlv_container_update()
1505 struct batadv_tt_change_node *entry, *safe; in batadv_tt_changes_list_free() local
1509 list_for_each_entry_safe(entry, safe, &bat_priv->tt.changes_list, in batadv_tt_changes_list_free()
2260 struct hlist_node *safe; in batadv_tt_global_del_orig_list() local
2265 hlist_for_each_entry_safe(orig_entry, safe, head, list) in batadv_tt_global_del_orig_list()
2287 struct hlist_node *safe; in batadv_tt_global_del_orig_node() local
2293 hlist_for_each_entry_safe(orig_entry, safe, head, list) { in batadv_tt_global_del_orig_node()
[all …]
/Linux-v5.4/drivers/remoteproc/
DKconfig24 It's safe to say N here.
42 It's safe to say N here if you're not interested in multimedia
75 It's safe to say n here if you're not interested in multimedia
85 It's safe to say N here if you're not interested in the Keystone

12345678910>>...15