| /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 …]
|
| /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 …]
|
| /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
|
| /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.
|
| /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
|
| /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.
|
| /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
|
| /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()
|
| /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
|
| /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 …]
|
| /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.
|
| /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")
|
| /linux-5.10/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.
55 # Hardly any platforms need this. It is safe to select, but only do so if you
|
| /linux-5.10/drivers/gpu/drm/msm/disp/dpu1/ |
| D | dpu_hw_top.h | 47 * struct dpu_danger_safe_status: danger and safe status signals
108 * @status: Pointer to danger safe status
122 * get_safe_status - get safe status
124 * @status: Pointer to danger safe status
|
| /linux-5.10/drivers/iommu/arm/arm-smmu/ |
| D | arm-smmu-qcom.c | 40 * such as USB and UFS, turn off wait-for-safe on sdm845 based boards, in qcom_sdm845_smmu500_reset()
42 * call handlers to turn on/off the wait-for-safe logic. in qcom_sdm845_smmu500_reset()
46 dev_warn(smmu->dev, "Failed to turn off SAFE logic\n"); in qcom_sdm845_smmu500_reset()
|
| /linux-5.10/kernel/printk/ |
| D | printk_safe.c | 3 * printk_safe.c - Safe printk for printk-deadlock-prone contexts
52 /* Get flushed in a more safe context. */
60 * Add a message to per-CPU context-dependent buffer. NMI and printk-safe
61 * have dedicated buffers, because otherwise printk-safe preempted by
286 * Safe printk() for NMI context. It uses a per-CPU buffer to
384 /* Use extra buffer in NMI when logbuf_lock is taken or in safe mode. */ in vprintk_func()
388 /* Use extra buffer to prevent a recursion deadlock in safe mode. */ in vprintk_func()
|
| /linux-5.10/drivers/gpu/drm/amd/amdgpu/ |
| D | amdgpu_rlc.c | 31 * amdgpu_gfx_rlc_enter_safe_mode - Set RLC into safe mode
35 * Set RLC enter into safe mode if RLC is enabled and haven't in safe mode.
55 * amdgpu_gfx_rlc_exit_safe_mode - Set RLC out of safe mode
59 * Set RLC exit safe mode if RLC is enabled and have entered into safe mode.
|
| /linux-5.10/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-5.10/drivers/mfd/ |
| D | da9052-i2c.c | 25 /* I2C safe register check */
55 * This fix is to follow any read or write with a dummy read to a safe
67 /* A dummy read to a safe register address. */ in da9052_i2c_fix()
77 * to a safe place is not required. in da9052_i2c_fix()
|
| /linux-5.10/arch/x86/realmode/rm/ |
| D | trampoline_64.S | 42 cli # We should be safe anyway
87 cli # We should be safe anyway
120 * then it is safe for us to set the MSR bit and continue. If we
133 * CPU has has not been set. It is safe to set it, so do so.
|
| /linux-5.10/Documentation/devicetree/bindings/dma/ |
| D | ti-dma-crossbar.txt | 16 - ti,dma-safe-map: Safe routing value for unused request lines
52 ti,dma-safe-map = <0>;
|
| /linux-5.10/mm/ |
| D | zpool.c | 149 * Implementations must guarantee this to be thread-safe.
207 * Implementations must guarantee this to be thread-safe,
232 * Implementations must guarantee this to be thread-safe.
248 * Implementations must guarantee this to be thread-safe.
269 * Implementations must guarantee this to be thread-safe.
288 * Implementations must guarantee this to be thread-safe,
311 * Implementations must guarantee this to be thread-safe.
|
| /linux-5.10/tools/include/linux/ |
| D | list.h | 201 * can only be safe if the only activity that can happen
420 * list_for_each_safe - iterate over a list safe against removal of list entry
430 * list_for_each_prev_safe - iterate over a list backwards safe against removal of list entry
514 * list_for_each_entry_safe - iterate over list of given type safe against removal of list entry
527 * list_for_each_entry_safe_continue - continue list iteration safe against removal
534 * safe against removal of list entry.
543 * list_for_each_entry_safe_from - iterate over list from current point safe against removal
549 * Iterate over list of given type from current point, safe against
558 * list_for_each_entry_safe_reverse - iterate backwards over list safe against removal
564 * Iterate backwards over list of given type, safe against removal
[all …]
|
| /linux-5.10/arch/x86/include/asm/ |
| D | edac.h | 5 /* ECC atomic, DMA, SMP and interrupt safe scrub function */
13 * are interrupt, DMA and SMP safe. in edac_atomic_scrub()
|
| /linux-5.10/net/ax25/ |
| D | TODO | 2 listen_lock have to be bh-safe?
4 Do the netrom and rose locks have to be bh-safe?
|