| /Linux-v4.19/arch/arm/common/ |
| D | dmabounce.c | 58 void *safe; member
139 buf->safe = dma_pool_alloc(pool->pool, GFP_ATOMIC, in alloc_safe_buffer()
142 buf->safe = dma_alloc_coherent(dev, size, &buf->safe_dma_addr, in alloc_safe_buffer()
146 if (buf->safe == NULL) { in alloc_safe_buffer()
201 dma_pool_free(buf->pool->pool, buf->safe, buf->safe_dma_addr); in free_safe_buffer()
203 dma_free_coherent(device_info->dev, buf->size, buf->safe, in free_safe_buffer()
265 buf->safe, buf->safe_dma_addr); in map_single()
270 __func__, ptr, buf->safe, size); in map_single()
271 memcpy(buf->safe, ptr, size); in map_single()
286 buf->safe, buf->safe_dma_addr); in unmap_single()
[all …]
|
| /Linux-v4.19/drivers/usb/serial/ |
| D | safe_serial.c | 75 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-v4.19/Documentation/i2c/ |
| D | DMA-considerations | 11 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-v4.19/fs/ntfs/ |
| D | Kconfig | 8 safe, write support available. For write support you must also
27 Linux on your computer it is safe to say N.
55 This enables the partial, but safe, write support in the NTFS driver.
65 damaged someones data so we assume it is perfectly safe to use.
67 Note: While write support is safe in this version (a rewrite from
70 is not safe.
78 It is perfectly safe to say N here.
|
| /Linux-v4.19/Documentation/scsi/ |
| D | dc395x.txt | 7 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-v4.19/drivers/ide/ |
| D | tx4938ide.c | 62 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-v4.19/drivers/parport/ |
| D | Kconfig | 31 and it is safe to compile all the corresponding drivers into the
83 is safe to say N.
99 called parport_ip32. If in doubt, saying N is the safe plan.
108 called parport_amiga. If in doubt, saying N is the safe plan.
117 parport_mfc3. If in doubt, saying N is the safe plan.
126 called parport_atari. If in doubt, saying N is the safe plan.
160 appear in /proc/sys/dev/parport/*/autoprobe*. It is safe to say N.
|
| /Linux-v4.19/drivers/gpu/drm/omapdrm/ |
| D | tcm.h | 325 #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-v4.19/drivers/gpu/drm/ttm/ |
| D | ttm_execbuf_util.c | 121 struct ttm_validate_buffer *safe = entry; in ttm_eu_reserve_buffers() local
123 list_del(&safe->head); in ttm_eu_reserve_buffers()
124 list_add(&safe->head, dups); in ttm_eu_reserve_buffers()
|
| /Linux-v4.19/net/ax25/ |
| D | TODO | 2 listen_lock have to be bh-safe?
4 Do the netrom and rose locks have to be bh-safe?
|
| /Linux-v4.19/drivers/of/ |
| D | Kconfig | 26 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.
54 # Hardly any platforms need this. It is safe to select, but only do so if you
|
| /Linux-v4.19/lib/lz4/ |
| D | lz4_decompress.c | 460 char *dest, int compressedSize, int maxOutputSize, int safe, in LZ4_decompress_usingDict_generic() argument
465 compressedSize, maxOutputSize, safe, full, 0, in LZ4_decompress_usingDict_generic()
470 compressedSize, maxOutputSize, safe, full, 0, in LZ4_decompress_usingDict_generic()
473 maxOutputSize, safe, full, 0, noDict, in LZ4_decompress_usingDict_generic()
477 maxOutputSize, safe, full, 0, usingExtDict, in LZ4_decompress_usingDict_generic()
|
| /Linux-v4.19/drivers/usb/wusbcore/ |
| D | Kconfig | 15 To compile this support select Y (built in). It is safe to
29 It is safe to select even if you don't have a compatible
|
| /Linux-v4.19/drivers/uwb/ |
| D | Kconfig | 41 is safe to select any even if you do not have the hardware.
57 is safe to select any even if you do not have the hardware.
69 is safe to select any even if you do not have the hardware.
|
| /Linux-v4.19/fs/dlm/ |
| D | requestqueue.c | 158 struct rq_entry *e, *safe; in dlm_purge_requestqueue() local
161 list_for_each_entry_safe(e, safe, &ls->ls_requestqueue, list) { in dlm_purge_requestqueue()
|
| /Linux-v4.19/Documentation/locking/ |
| D | spinlocks.txt | 13 The above is always safe. It will disable interrupts _locally_, but the
38 NOTE! The spin-lock is safe only when you _also_ use the lock itself
92 are the most safe ones, and the ones that work under all circumstances,
93 but partly _because_ they are safe they are also fairly slow. They are slower
137 But when you do the write-lock, you have to use the irq-safe version.
142 wake up. So read-locks are safe (which is good: they are very common
|
| D | lockdep-design.txt | 72 <hardirq-safe> and <hardirq-unsafe>
73 <softirq-safe> and <softirq-unsafe>
97 <hardirq-safe> -> <hardirq-unsafe>
98 <softirq-safe> -> <softirq-unsafe>
100 The first rule comes from the fact that a hardirq-safe lock could be
102 thus could result in a lock inversion deadlock. Likewise, a softirq-safe
113 - if a new hardirq-safe lock is discovered, we check whether it
116 - if a new softirq-safe lock is discovered, we check whether it took
120 hardirq-safe lock took it in the past.
123 softirq-safe lock took it in the past.
|
| /Linux-v4.19/arch/powerpc/platforms/52xx/ |
| D | Kconfig | 20 gpt nodes, then it is safe to use such gpt to reset the board,
56 It is safe to say 'Y' here
|
| /Linux-v4.19/Documentation/devicetree/bindings/power/supply/ |
| D | qcom_smbb.txt | 62 - 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-v4.19/drivers/remoteproc/ |
| D | Kconfig | 23 It's safe to say N here.
41 It's safe to say N here if you're not interested in multimedia
74 It's safe to say n here if you're not interested in multimedia
84 It's safe to say N here if you're not interested in the Keystone
|
| /Linux-v4.19/drivers/clocksource/ |
| D | em_sti.c | 266 int safe; in em_sti_clock_event_next() local
269 safe = em_sti_count(p) < (next - 1); in em_sti_clock_event_next()
271 return !safe; in em_sti_clock_event_next()
|
| /Linux-v4.19/arch/x86/realmode/rm/ |
| D | trampoline_32.S | 40 cli # We should be safe anyway
|
| /Linux-v4.19/scripts/coccinelle/free/ |
| D | devm_free.cocci | 59 @safe depends on context || org || report exists@
114 position p != safe.p;
|
| /Linux-v4.19/drivers/input/gameport/ |
| D | ns558.c | 270 struct ns558 *ns558, *safe; in ns558_exit() local
272 list_for_each_entry_safe(ns558, safe, &ns558_list, node) { in ns558_exit()
|
| /Linux-v4.19/Documentation/devicetree/bindings/arm/omap/ |
| D | crossbar.txt | 27 - ti,irqs-safe-map: integer which maps to a safe configuration to use
|
