| /linux/arch/nios2/include/asm/ |
| H A 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/Documentation/i2c/ |
| H A 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/Documentation/devicetree/bindings/power/supply/ |
| H A D | qcom,pm8916-lbc.yaml | 63 qcom,fast-charge-safe-voltage:
68 Maximum safe battery voltage in uV; May be pre-set by bootloader,
71 qcom,fast-charge-safe-current:
76 Maximum safe battery charge current in uA; May be pre-set by
86 - qcom,fast-charge-safe-voltage
87 - qcom,fast-charge-safe-current
125 qcom,fast-charge-safe-current = <900000>;
126 qcom,fast-charge-safe-voltage = <4300000>;
|
| H A D | qcom,pm8941-charger.yaml | 66 qcom,fast-charge-safe-voltage:
71 Maximum safe battery voltage in uV; May be pre-set by bootloader, in which case,
75 qcom,fast-charge-safe-current:
80 Maximum safe battery charge current in uA; May pre-set by bootloader, in which case,
|
| /linux/arch/um/drivers/ |
| H A 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.
86 It is safe to leave this unchanged.
96 It is safe to leave this unchanged, although you may wish to change
108 It is safe to leave this unchanged, although you may wish to change
120 It is safe to say 'Y' here.
|
| /linux/drivers/parport/ |
| H A D | Kconfig | 32 and it is safe to compile all the corresponding drivers into the
85 is safe to say N.
101 called parport_ip32. If in doubt, saying N is the safe plan.
110 called parport_amiga. If in doubt, saying N is the safe plan.
119 parport_mfc3. If in doubt, saying N is the safe plan.
128 called parport_atari. If in doubt, saying N is the safe plan.
151 appear in /proc/sys/dev/parport/*/autoprobe*. It is safe to say N.
|
| /linux/include/linux/ |
| H A 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.
273 * This function is safe to call as long as @ref is between init and exit.
304 * This function is safe to call as long as @ref is between init and exit.
324 * 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.
[all …]
|
| /linux/drivers/of/ |
| H A D | Kconfig | 43 If unsure, say N here. This option is not safe to enable.
52 If unsure, say N here, but this option is safe to enable.
62 If unsure, say N here, but this option is safe to enable.
81 # Hardly any platforms need this. It is safe to select, but only do so if you
124 If unsure, say N here, but this option is safe to enable.
|
| /linux/drivers/usb/serial/ |
| H A 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/rust/kernel/ |
| H A D | task.rs | 101 // runs. It is safe for that to happen on any thread, so it is ok for this type to be `Send`.
162 // SAFETY: Getting the current pointer is always safe. in current_raw()
169 /// [`current`] macro because it is safe.
226 // SAFETY: It's always safe to call `task_uid` on a valid task. in uid()
232 // SAFETY: It's always safe to call `task_euid` on a valid task. in euid()
238 // SAFETY: It's always safe to call `signal_pending` on a valid task. in signal_pending()
265 // thus pass a null pointer. The underlying C function is safe to be used with NULL in tgid_nr_ns()
272 // SAFETY: It's always safe to call `wake_up_process` on a valid task, even if the task in wake_up()
296 // This is safe even if `kthread_use_mm()`/`kthread_unuse_mm()` are used. There are two in mm()
317 // SAFETY: It is safe to call `task_active_pid_ns` without RCU protection when calling it in active_pid_ns()
[all …]
|
| H A D | faux.rs | 30 // - `faux_ops` is safe to leave NULL according to the C API in new()
69 // SAFETY: The faux device API is thread-safe as guaranteed by the device core, as long as
74 // SAFETY: The faux device API is thread-safe as guaranteed by the device core, as long as
|
| /linux/Documentation/scsi/ |
| H A D | dc395x.rst | 10 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:
99 dc395x. (eg "dc395x.safe=1")
|
| /linux/Documentation/devicetree/bindings/display/tegra/ |
| H A D | nvidia,tegra124-sor.yaml | 119 - description: safe reference clock for the SOR clock
131 - const: safe
141 - description: safe reference clock for the SOR clock
152 - const: safe
182 clock-names = "sor", "out", "parent", "dp", "safe";
|
| /linux/Documentation/admin-guide/hw-vuln/ |
| H A D | indirect-target-selection.rst | 63 added ITS-safe thunks. These safe thunks consists of indirect branch in the
65 a retpoline site is evaluated to be ITS-safe, it is replaced with an inline
70 From a dynamically allocated pool of safe-thunks, each vulnerable site is
90 safe thunks. Unless user requested the RSB-stuffing mitigation.
158 relocated to safe thunks.
|
| /linux/drivers/gpu/drm/msm/disp/dpu1/ |
| H A D | dpu_hw_top.h | 46 * struct dpu_danger_safe_status: danger and safe status signals
114 * @status: Pointer to danger safe status
128 * get_safe_status - get safe status
130 * @status: Pointer to danger safe status
|
| /linux/security/apparmor/include/ |
| H A D | cred.h | 92 * of the label so it is safe to call when inside of locks.
104 * This fn will not update the tasks cred, so it is safe inside of locks
138 * safe to call inside locks
160 * Not safe to call inside locks
|
| /linux/drivers/mfd/ |
| H A D | da9052-i2c.c | 22 /* I2C safe register check */
52 * This fix is to follow any read or write with a dummy read to a safe
64 /* A dummy read to a safe register address. */ in da9052_i2c_fix()
74 * to a safe place is not required. in da9052_i2c_fix()
|
| /linux/drivers/gpu/drm/nouveau/nvkm/subdev/clk/ |
| H A D | gm20b.c | 136 /* safe frequency we can use at minimum voltage */
485 * Compute PLL parameters that are always safe for the current voltage
494 /* remove a safe margin of 10% */ in gm20b_dvfs_calc_safe_pll()
584 * frequency to be safe at DVFS coeff = 0. in gm20b_clk_prog()
587 * - safe frequency target matches the lowest - old - frequency in gm20b_clk_prog()
593 * - safe frequency target matches the lowest - new - frequency in gm20b_clk_prog()
597 * Interim step can be skipped if old frequency is below safe minimum, in gm20b_clk_prog()
598 * i.e., it is low enough to be safe at any voltage in operating range in gm20b_clk_prog()
606 /* voltage will raise: safe frequency is current one */ in gm20b_clk_prog()
609 /* voltage will drop: safe frequency is new one */ in gm20b_clk_prog()
[all …]
|
| /linux/Documentation/devicetree/bindings/dma/ |
| H A D | ti-dma-crossbar.txt | 16 - ti,dma-safe-map: Safe routing value for unused request lines
52 ti,dma-safe-map = <0>;
|
| /linux/tools/include/linux/ |
| H A D | list.h | 201 * can only be safe if the only activity that can happen
431 * list_for_each_safe - iterate over a list safe against removal of list entry
441 * list_for_each_prev_safe - iterate over a list backwards safe against removal of list entry
525 * list_for_each_entry_safe - iterate over list of given type safe against removal of list entry
538 * list_for_each_entry_safe_continue - continue list iteration safe against removal
545 * safe against removal of list entry.
554 * list_for_each_entry_safe_from - iterate over list from current point safe against removal
560 * Iterate over list of given type from current point, safe against
569 * list_for_each_entry_safe_reverse - iterate backwards over list safe against removal
575 * Iterate backwards over list of given type, safe against removal
[all …]
|
| /linux/Documentation/livepatch/ |
| H A D | livepatch.rst | 70 when it is safe to do so, e.g. when the affected locks are released
73 The theory about how to apply functions a safe way is rather complex.
83 Patches are applied on a per-task basis, when the task is deemed safe to
95 safe to patch tasks:
184 klp_update_patch_state() in a safe location. Kthreads are typically
185 in an infinite loop which does some action repeatedly. The safe
194 There the safe location must be carefully selected on a case-by-case
388 Module removal is only safe when there are no users of functions provided
|
| /linux/Documentation/locking/ |
| H A D | spinlocks.rst | 18 The above is always safe. It will disable interrupts _locally_, but the
45 NOTE! The spin-lock is safe only when you **also** use the lock itself
101 are the most safe ones, and the ones that work under all circumstances,
102 but partly **because** they are safe they are also fairly slow. They are slower
|
| H A D | lockdep-design.rst | 117 A lock is irq-safe means it was ever used in an irq context, while a lock
124 <hardirq-safe> or <hardirq-unsafe>
125 <softirq-safe> or <softirq-unsafe>
127 This is because if a lock can be used in irq context (irq-safe) then it
159 <hardirq-safe> -> <hardirq-unsafe>
160 <softirq-safe> -> <softirq-unsafe>
162 The first rule comes from the fact that a hardirq-safe lock could be
164 thus could result in a lock inversion deadlock. Likewise, a softirq-safe
175 - if a new hardirq-safe lock is discovered, we check whether it
178 - if a new softirq-safe lock is discovered, we check whether it took
[all …]
|
| /linux/drivers/usb/gadget/function/ |
| H A D | f_subset.c | 36 * "SAFE", which happens to have a mode which is identical to the "CDC
42 * descriptors to the CDC Subset code, making this code look like a SAFE
66 * some host side drivers will understand it as a "SAFE" variant.
68 * "SAFE" loosely follows CDC WMC MDLM, violating the spec in various ways.
110 * the submode of "SAFE" which directly matches the CDC Subset.
117 0, /* "SAFE" */
236 [0].s = "CDC Ethernet Subset/SAFE",
|
| /linux/scripts/dtc/libfdt/ |
| H A D | libfdt_internal.h | 86 * For situations where security is not a concern it may be safe to enable
148 * This is safe to enable in most circumstances, even though it may
163 * ability to fix the problem there. This is safe if you know that the
173 * This can generally be considered safe to enable.
|