| /kernel/linux/linux-4.19/arch/arm/common/ |
| D | dmabounce.c | 56 /* safe buffer info */
58 void *safe; member
106 /* allocate a 'safe' buffer and keep track of it */
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()
167 /* determine if a buffer is from our "safe" pool */
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()
[all …]
|
| /kernel/linux/linux-5.10/arch/arm/common/ |
| D | dmabounce.c | 54 /* safe buffer info */
56 void *safe; member
104 /* allocate a 'safe' buffer and keep track of it */
137 buf->safe = dma_pool_alloc(pool->pool, GFP_ATOMIC, in alloc_safe_buffer()
140 buf->safe = dma_alloc_coherent(dev, size, &buf->safe_dma_addr, in alloc_safe_buffer()
144 if (buf->safe == NULL) { in alloc_safe_buffer()
165 /* determine if a buffer is from our "safe" pool */
199 dma_pool_free(buf->pool->pool, buf->safe, buf->safe_dma_addr); in free_safe_buffer()
201 dma_free_coherent(device_info->dev, buf->size, buf->safe, in free_safe_buffer()
263 buf->safe, buf->safe_dma_addr); in map_single()
[all …]
|
| /kernel/linux/linux-5.10/arch/nios2/include/asm/ |
| D | asm-macros.h | 36 * It is safe to use the same register for reg1 & reg2.
55 * It is safe to use the same register for reg1 & reg2.
75 * It is safe to use the same register for reg1 & reg2.
94 * It is safe to use the same register for reg1 & reg2.
106 * It is safe to use the same register for reg1 & reg2.
118 * It is NOT safe to use the same register for reg1 & reg2.
139 * It is NOT safe to use the same register for reg1 & reg2.
160 * It is NOT safe to use the same register for reg1 & reg2.
182 * It is NOT safe to use the same register for reg1 & reg2.
195 * It is NOT safe to use the same register for reg1 & reg2.
[all …]
|
| /kernel/linux/linux-4.19/arch/nios2/include/asm/ |
| D | asm-macros.h | 47 * It is safe to use the same register for reg1 & reg2.
66 * It is safe to use the same register for reg1 & reg2.
86 * It is safe to use the same register for reg1 & reg2.
105 * It is safe to use the same register for reg1 & reg2.
117 * It is safe to use the same register for reg1 & reg2.
129 * It is NOT safe to use the same register for reg1 & reg2.
150 * It is NOT safe to use the same register for reg1 & reg2.
171 * It is NOT safe to use the same register for reg1 & reg2.
193 * It is NOT safe to use the same register for reg1 & reg2.
206 * It is NOT safe to use the same register for reg1 & reg2.
[all …]
|
| /kernel/linux/linux-4.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
|
| /kernel/linux/linux-5.10/Documentation/i2c/ |
| D | dma-considerations.rst | 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
|
| /kernel/linux/linux-4.19/fs/ntfs/ |
| D | Kconfig | 9 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.
|
| /kernel/linux/linux-5.10/fs/ntfs/ |
| D | Kconfig | 9 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.
|
| /kernel/linux/linux-5.10/drivers/remoteproc/ |
| D | Kconfig | 24 It's safe to say N if you don't want to use this interface.
33 It's safe to say N here.
52 It's safe to say N here.
70 It's safe to say N here if you're not interested in multimedia
115 It's safe to say n here if you're not interested in multimedia
125 It's safe to say N here if you're not interested in the Keystone
275 It's safe to say N here if you're not interested in utilizing
288 It's safe to say N here if you're not interested in utilizing
|
| /kernel/linux/linux-5.10/drivers/parport/ |
| D | Kconfig | 32 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.
|
| /kernel/linux/linux-4.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.
|
| /kernel/linux/linux-4.19/include/linux/ |
| D | percpu-refcount.h | 24 * it's safe to drop the initial ref.
35 * and it's then safe to drop the initial ref with percpu_ref_put().
174 * This function is safe to call as long as @ref is between init and exit.
196 * This function is safe to call as long as @ref is between init and exit.
210 * This function is safe to call as long as @ref is between init and exit.
244 * This function is safe to call as long as @ref is between init and exit.
273 * This function is safe to call as long as @ref is between init and exit.
296 * This function is safe to call as long as @ref is between init and exit.
309 * This function is safe to call as long as @ref is between init and exit
323 * This function is safe to call as long as @ref is between init and exit.
|
| /kernel/linux/linux-4.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")
|
| /kernel/linux/linux-5.10/include/linux/ |
| D | percpu-refcount.h | 24 * it's safe to drop the initial ref.
35 * and it's then safe to drop the initial ref with percpu_ref_put().
196 * This function is safe to call as long as @ref is between init and exit.
218 * This function is safe to call as long as @ref is between init and exit.
233 * This function is safe to call as long as @ref is between init and exit.
262 * This function is safe to call as long as @ref is between init and exit.
282 * This function is safe to call as long as @ref is between init and exit.
311 * This function is safe to call as long as @ref is between init and exit.
334 * This function is safe to call as long as @ref is between init and exit.
347 * This function is safe to call as long as @ref is between init and exit
|
| /kernel/linux/linux-4.19/arch/arm64/include/asm/ |
| D | cpufeature.h | 36 * The safe value of a CPUID feature field is dependent on the implications
43 * a field when EXACT is specified, failing which, the safe value specified
48 FTR_EXACT, /* Use a predefined safe value */
49 FTR_LOWER_SAFE, /* Smaller value is safe */
50 FTR_HIGHER_SAFE, /* Bigger value is safe */
51 FTR_HIGHER_OR_ZERO_SAFE, /* Bigger value is safe, but 0 is biggest */
73 s64 safe_val; /* safe value for FTR_EXACT features */
79 * @sys_val Safe value across the CPUs (system view)
154 * kernel), the kernel should make sure that it is safe to use the CPU,
251 /* Is it safe for a late CPU to miss this capability when system has it */
[all …]
|
| /kernel/linux/linux-5.10/drivers/usb/serial/ |
| D | safe_serial.c | 3 * Safe Encapsulated USB Serial Driver
75 static bool safe = true; variable
79 #define DRIVER_DESC "USB Safe Encapsulated Serial"
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()
|
| /kernel/linux/linux-4.19/drivers/usb/serial/ |
| D | safe_serial.c | 3 * Safe Encapsulated USB Serial Driver
75 static bool safe = true; variable
79 #define DRIVER_DESC "USB Safe Encapsulated Serial"
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()
|
| /kernel/linux/linux-4.19/security/apparmor/include/ |
| D | cred.h | 62 * If @task != current needs to be called in RCU safe critical section
75 * of the label so it is safe to call when inside of locks.
87 * This fn will not update the tasks cred, so it is safe inside of locks
121 * safe to call inside locks
143 * Not safe to call inside locks
|
| /kernel/linux/linux-5.10/security/apparmor/include/ |
| D | cred.h | 72 * If @task != current needs to be called in RCU safe critical section
85 * of the label so it is safe to call when inside of locks.
97 * This fn will not update the tasks cred, so it is safe inside of locks
131 * safe to call inside locks
153 * Not safe to call inside locks
|
| /kernel/linux/linux-4.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.
|
| /kernel/linux/linux-5.10/arch/arm64/include/asm/ |
| D | cpufeature.h | 26 * The safe value of a CPUID feature field is dependent on the implications
33 * a field when EXACT is specified, failing which, the safe value specified
38 FTR_EXACT, /* Use a predefined safe value */
39 FTR_LOWER_SAFE, /* Smaller value is safe */
40 FTR_HIGHER_SAFE, /* Bigger value is safe */
41 FTR_HIGHER_OR_ZERO_SAFE, /* Bigger value is safe, but 0 is biggest */
63 s64 safe_val; /* safe value for FTR_EXACT features */
69 * @sys_val Safe value across the CPUs (system view)
144 * kernel), the kernel should make sure that it is safe to use the CPU,
245 /* Is it safe for a late CPU to miss this capability when system has it */
[all …]
|
| /kernel/linux/linux-5.10/arch/um/drivers/ |
| D | Kconfig | 38 It is safe to say 'Y' here.
48 It is safe to say 'Y' here.
57 It is safe to say 'Y' here.
65 It is safe to say 'Y' here.
79 It is safe to leave this unchanged.
89 It is safe to leave this unchanged, although you may wish to change
101 It is safe to leave this unchanged, although you may wish to change
111 It is safe to say 'Y' here.
|
| /kernel/linux/linux-4.19/arch/um/drivers/ |
| D | Kconfig | 38 It is safe to say 'Y' here.
48 It is safe to say 'Y' here.
57 It is safe to say 'Y' here.
65 It is safe to say 'Y' here.
79 It is safe to leave this unchanged.
89 It is safe to leave this unchanged, although you may wish to change
101 It is safe to leave this unchanged, although you may wish to change
111 It is safe to say 'Y' here.
|
| /kernel/linux/linux-5.10/Documentation/scsi/ |
| D | dc395x.rst | 10 be safe to use. Testing with hard disks has not been done to any
31 safe
34 If safe is set to 1 then the adapter will use conservative
35 ("safe") default settings. This sets:
102 dc395x. (eg "dc395x.safe=1")
|