Home
last modified time | relevance | path

Searched refs:safe (Results 1 – 25 of 352) sorted by relevance

12345678910>>...15

/linux/drivers/usb/serial/
H A Dsafe_serial.c75 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/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/admin-guide/hw-vuln/
H A Dsrso.rst64 * 'Vulnerable: Microcode, no safe RET':
91 Selected by default or by spec_rstack_overflow=safe-ret
95 Similar protection as "safe RET" above but employs an IBPB barrier on
123 default one is 'Mitigation: safe RET' which should take care of most
132 As one can surmise, 'Mitigation: safe RET' does come at the cost of some
148 the CPU to mispredict every function return using a 'safe return'
152 safe return sequence is itself free from attacker interference. In Zen3
154 untraining function srso_alias_untrain_ret() and the safe return
156 poisoned BTB entry and using that safe one for all function returns.
162 Checking the safe RET mitigation actually works
[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/drivers/gpu/drm/ttm/
H A Dttm_execbuf_util.c93 struct ttm_validate_buffer *safe = entry; in ttm_eu_reserve_buffers() local
95 list_del(&safe->head); in ttm_eu_reserve_buffers()
96 list_add(&safe->head, dups); in ttm_eu_reserve_buffers()
/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/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/gpu/drm/omapdrm/
H A Dtcm.h325 #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/arch/arm/boot/dts/qcom/
H A Dqcom-msm8974pro-sony-xperia-shinano-leo.dts32 qcom,fast-charge-safe-current = <3000000>;
34 qcom,fast-charge-safe-voltage = <4400000>;
H A Dqcom-msm8974pro-sony-xperia-shinano-aries.dts32 qcom,fast-charge-safe-current = <2100000>;
34 qcom,fast-charge-safe-voltage = <4400000>;
H A Dqcom-msm8974pro-sony-xperia-shinano-castor.dts137 qcom,fast-charge-safe-current = <1500000>;
141 qcom,fast-charge-safe-voltage = <4400000>;
/linux/arch/x86/mm/
H A Dextable.c168 struct pt_regs *regs, bool wrmsr, bool safe, int reg) in ex_handler_msr() argument
170 if (__ONCE_LITE_IF(!safe && wrmsr)) { in ex_handler_msr()
177 if (__ONCE_LITE_IF(!safe && !wrmsr)) { in ex_handler_msr()
189 if (safe) in ex_handler_msr()
/linux/arch/arm64/boot/dts/qcom/
H A Dmsm8916-wingtech-wt86518.dts47 qcom,fast-charge-safe-current = <900000>;
48 qcom,fast-charge-safe-voltage = <4300000>;
/linux/fs/dlm/
H A Drequestqueue.c136 struct rq_entry *e, *safe; in dlm_purge_requestqueue() local
139 list_for_each_entry_safe(e, safe, &ls->ls_requestqueue, list) { in dlm_purge_requestqueue()
/linux/arch/powerpc/platforms/52xx/
H A DKconfig20 gpt nodes, then it is safe to use such gpt to reset the board,
56 It is safe to say 'Y' here
/linux/net/batman-adv/
H A Dtranslation-table.c423 struct batadv_tt_change_node *tt_change_node, *entry, *safe; in batadv_tt_local_event() local
444 list_for_each_entry_safe(entry, safe, &bat_priv->tt.changes_list, in batadv_tt_local_event()
939 struct batadv_tt_change_node *entry, *safe; in batadv_tt_tvlv_container_update() local
978 list_for_each_entry_safe(entry, safe, &bat_priv->tt.changes_list, in batadv_tt_tvlv_container_update()
1374 struct batadv_tt_change_node *entry, *safe; in batadv_tt_changes_list_free() local
1378 list_for_each_entry_safe(entry, safe, &bat_priv->tt.changes_list, in batadv_tt_changes_list_free()
1981 struct hlist_node *safe; in batadv_tt_global_del_orig_list() local
1986 hlist_for_each_entry_safe(orig_entry, safe, head, list) in batadv_tt_global_del_orig_list()
2008 struct hlist_node *safe; in batadv_tt_global_del_orig_node() local
2014 hlist_for_each_entry_safe(orig_entry, safe, head, list) { in batadv_tt_global_del_orig_node()
[all …]
/linux/drivers/clocksource/
H A Dem_sti.c254 int safe; in em_sti_clock_event_next() local
257 safe = em_sti_count(p) < (next - 1); in em_sti_clock_event_next()
259 return !safe; in em_sti_clock_event_next()
/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/Documentation/devicetree/bindings/arm/omap/
H A Dcrossbar.txt27 - ti,irqs-safe-map: integer which maps to a safe configuration to use
/linux/scripts/coccinelle/free/
H A Ddevm_free.cocci58 @safe depends on context || org || report exists@
109 position p != safe.p;
/linux/drivers/input/gameport/
H A Dns558.c255 struct ns558 *ns558, *safe; in ns558_exit() local
257 list_for_each_entry_safe(ns558, safe, &ns558_list, node) { in ns558_exit()
/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/Documentation/locking/
H A Dspinlocks.rst18 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
/linux/fs/ocfs2/
H A DKconfig39 It is always safe to say Y here, as the clustering method is
51 It is safe to say Y, as the clustering method is run-time
/linux/arch/x86/xen/
H A DKconfig97 bool "Always use safe MSR accesses in PV guests"
101 Use safe (not faulting) MSR access functions even if the MSR access

12345678910>>...15