Home
last modified time | relevance | path

Searched full:safe (Results 1 – 25 of 1538) sorted by relevance

12345678910>>...62

/linux/tools/testing/selftests/ublk/
H A Dtest_generic_16.sh8 _prep_test "null" "stop --safe command"
16 # Test 1: stop --safe on idle device should succeed
20 # Device is idle (no openers), stop --safe should succeed
21 if ! ${UBLK_PROG} stop -n "${dev_id}" --safe; then
22 echo "stop --safe on idle device failed unexpectedly!"
30 # Test 2: stop --safe on device with active opener should fail
41 # Device has active opener, stop --safe should fail with -EBUSY
42 if ${UBLK_PROG} stop -n "${dev_id}" --safe 2>/dev/null; then
43 echo "stop --safe on busy device succeeded unexpectedly!"
/linux/arch/nios2/include/asm/
H A Dasm-macros.h36 * 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 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/Documentation/devicetree/bindings/power/supply/
H A Dqcom,pm8916-lbc.yaml63 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 Dqcom,pm8941-charger.yaml66 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/rust/kernel/io/
H A Dresource.rs42 // SAFETY: Safe as per the invariant of `Region`. in deref()
60 // SAFETY: Safe as per the invariant of `Region`. in drop()
65 // SAFETY: `Region` only holds a pointer to a C `struct resource`, which is safe to be used from
70 // safe to be used from any thread.
109 // - Safe as per the invariant of `Resource`. in request_region()
111 // safe as we own it and it will not be dropped until the `Region` is in request_region()
132 // SAFETY: Safe as per the invariants of `Resource`. in size()
139 // SAFETY: Safe as per the invariants of `Resource`. in start()
147 // SAFETY: Safe as per the invariants of `Resource`. in name()
164 // SAFETY: Safe a in flags()
[all...]
/linux/arch/um/drivers/
H A DKconfig38 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 DKconfig32 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/drivers/of/
H A DKconfig43 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/rust/kernel/
H A Dusb.rs53 // SAFETY: It's safe to set the fields of `struct usb_driver` on initialization. in register()
86 // does not add additional invariants, so it's safe to transmute. in probe_callback()
229 // additional invariants, so it's safe to transmute to `RawType`. in from_device_and_interface_info()
395 // SAFETY: It is safe to send a &Interface to another thread because we do not in dec_ref()
459 // SAFETY: It is safe to send a &Device to another thread because we do not in as_ref()
H A Dtask.rs101 // 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.
223 // SAFETY: It's always safe to call `task_uid` on a valid task. in euid()
230 // SAFETY: It's always safe to call `signal_pending` on a valid task. in signal_pending()
259 // thus pass a null pointer. The underlying C function is safe to be used with NULL in tgid_nr_ns()
267 // SAFETY: It's always safe to call `wake_up_process` on a valid task, even if the task in wake_up()
291 // This is safe even if `kthread_use_mm()`/`kthread_unuse_mm()` are used. There are two in mm()
312 // SAFETY: It is safe to call `task_active_pid_ns` without RCU protection when calling it in active_pid_ns()
325 // safe an in active_pid_ns()
[all...]
H A Dregulator.rs254 // SAFETY: Safe as per the type invariants of `Regulator`. in set_voltage()
266 // SAFETY: Safe as per the type invariants of `Regulator`. in get_voltage()
274 // SAFETY: It is safe to call `regulator_get()`, on a device pointer in get_internal()
287 // SAFETY: Safe as per the type invariants of `Regulator`. in enable_internal()
292 // SAFETY: Safe as per the type invariants of `Regulator`. in disable_internal()
354 // SAFETY: Safe as per the type invariants of `Regulator`. in is_enabled()
363 // reference on the enabled refcount, so it is safe to relinquish it in drop()
368 // so it is safe to relinquish it now. in drop()
373 // SAFETY: It is safe to send a `Regulator<T>` across threads. In particular, a
377 // SAFETY: It is safe to send a &Regulator<T> across threads because the C side
/linux/rust/kernel/drm/gem/
H A Dshmem.rs122 // SAFETY: All GEM objects are thread-safe. in new()
125 // SAFETY: All GEM objects are thread-safe. in new()
144 #[allow(unused_unsafe, reason = "Safe since Rust 1.82.0")] in new()
183 // - We're in free_callback - so this function is safe to call. in deref()
228 // SAFETY: We checked that this is not an iomem allocation, making it safe to read
247 // - This function is safe to call with the DMA reservation lock held.
334 // safe to modify this field.
339 // to have exclusive access - thus making this safe to hold a mutable reference to.
372 // - Our immutable reference is proof that this is safe to dereference.
563 // - `obj` is fully initialized, making this function safe t
[all...]
/linux/Documentation/scsi/
H A Ddc395x.rst10 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 Dnvidia,tegra124-sor.yaml119 - 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/drivers/gpu/drm/msm/disp/dpu1/
H A Ddpu_hw_top.h46 * struct dpu_danger_safe_status: danger and safe status signals
113 * @status: Pointer to danger safe status
127 * @get_safe_status: get safe status
129 * @status: Pointer to danger safe status
/linux/Documentation/admin-guide/hw-vuln/
H A Dindirect-target-selection.rst63 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/rust/kernel/sync/
H A Dbarrier.rs63 // SAFETY: barrier methods are safe to call.
/linux/arch/arm64/include/asm/
H A Dcpufeature.h32 * The safe value of a CPUID feature field is dependent on the implications
39 * a field when EXACT is specified, failing which, the safe value specified
44 FTR_EXACT, /* Use a predefined safe value */
45 FTR_LOWER_SAFE, /* Smaller value is safe */
46 FTR_HIGHER_SAFE, /* Bigger value is safe */
47 FTR_HIGHER_OR_ZERO_SAFE, /* Bigger value is safe, but 0 is biggest */
69 s64 safe_val; /* safe value for FTR_EXACT features */
97 * @sys_val Safe value across the CPUs (system view)
173 * kernel), the kernel should make sure that it is safe to use the CPU,
274 /* Is it safe for a late CPU to miss this capability when system has it */
[all …]
/linux/drivers/mfd/
H A Dda9052-i2c.c22 /* 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/Documentation/devicetree/bindings/dma/
H A Dti-dma-crossbar.txt16 - ti,dma-safe-map: Safe routing value for unused request lines
52 ti,dma-safe-map = <0>;
/linux/arch/x86/include/asm/
H A Dnospec-branch.h173 * On PBRSB-vulnerable CPUs, it is not safe for a RET to be executed
183 * Safe-RET. If Safe-RET is interrupted after the CALL or LEA the RSB may get
186 * The Safe-RET sequence is:
197 * 1. Userspace runs and poisons the BTB around the safe-RET routine
205 * to an interrupted safe-RET
208 * speculatively does a safe-RET. But this is unsafe since it was never
212 * Note that this LFENCE only occurs if safe-RET was actually interrupted (so
/linux/drivers/gpu/drm/nouveau/nvkm/subdev/clk/
H A Dgm20b.c137 /* safe frequency we can use at minimum voltage */
486 * Compute PLL parameters that are always safe for the current voltage
495 /* remove a safe margin of 10% */ in gm20b_dvfs_calc_safe_pll()
585 * frequency to be safe at DVFS coeff = 0. in gm20b_clk_prog()
588 * - safe frequency target matches the lowest - old - frequency in gm20b_clk_prog()
594 * - safe frequency target matches the lowest - new - frequency in gm20b_clk_prog()
598 * Interim step can be skipped if old frequency is below safe minimum, in gm20b_clk_prog()
599 * i.e., it is low enough to be safe at any voltage in operating range in gm20b_clk_prog()
607 /* voltage will raise: safe frequency is current one */ in gm20b_clk_prog()
610 /* voltage will drop: safe frequency is new one */ in gm20b_clk_prog()
[all …]
/linux/tools/include/linux/
H A Dlist.h211 * can only be safe if the only activity that can happen
441 * list_for_each_safe - iterate over a list safe against removal of list entry
451 * list_for_each_prev_safe - iterate over a list backwards safe against removal of list entry
535 * list_for_each_entry_safe - iterate over list of given type safe against removal of list entry
548 * list_for_each_entry_safe_continue - continue list iteration safe against removal
555 * safe against removal of list entry.
564 * list_for_each_entry_safe_from - iterate over list from current point safe against removal
570 * Iterate over list of given type from current point, safe against
579 * list_for_each_entry_safe_reverse - iterate backwards over list safe against removal
585 * Iterate backwards over list of given type, safe against removal
[all …]
/linux/arch/x86/lib/
H A Dretpoline.S195 * As a result, srso_alias_safe_ret() becomes a safe return.
218 * Safe-RET sequence. If you need to change it, adjust
227 /* End of Safe-RET sequence */
247 * thus a "safe" one to use.
263 * Safe-RET sequence. If you need to change it, adjust
268 /* End of Safe-RET sequence */

12345678910>>...62