Home
last modified time | relevance | path

Searched full:strong (Results 1 – 25 of 178) sorted by relevance

12345678

/Linux-v5.15/Documentation/w1/slaves/
Dw1_therm.rst44 powered devices are detected on the bus (and strong pullup is enabled
56 A strong pullup will be applied during the conversion if required.
99 strong pullup, 1 to enable autodetection or 2 to force strong pullup.
102 If so, it will activate the master's strong pullup.
104 (seems to be the case with some DS18S20) the strong pullup can
107 If the strong pullup is enabled, the master's strong pullup will be
109 does support the strong pullup (or it falls back to a pullup
112 sufficient. The strong pullup is designed to provide the additional
/Linux-v5.15/tools/memory-model/
Dlinux-kernel.cat43 let strong-fence = mb | gp
45 let nonrw-fence = strong-fence | po-rel | acq-po
75 (* Propagation: Ordering from release operations and strong fences. *)
77 let cumul-fence = [Marked] ; (A-cumul(strong-fence | po-rel) | wmb |
93 (* Propagation: Each non-rf link needs a strong fence. *)
94 let pb = prop ; strong-fence ; hb* ; [Marked]
117 * The synchronize_rcu() strong fence is special in that it can order not
126 * inter-CPU strong fence.
143 let strong-fence = strong-fence | rcu-fence
171 ((strong-fence ; [Marked] ; xbstar) | (xbstar & int))
[all …]
/Linux-v5.15/drivers/hid/
Dhid-emsff.c27 int weak, strong; in emsff_play() local
30 strong = effect->u.rumble.strong_magnitude; in emsff_play()
32 dbg_hid("called with 0x%04x 0x%04x\n", strong, weak); in emsff_play()
35 strong = strong * 0xff / 0xffff; in emsff_play()
38 emsff->report->field[0]->value[2] = strong; in emsff_play()
40 dbg_hid("running with 0x%02x 0x%02x\n", strong, weak); in emsff_play()
Dhid-lg2ff.c27 int weak, strong; in play_effect() local
29 strong = effect->u.rumble.strong_magnitude; in play_effect()
32 if (weak || strong) { in play_effect()
34 strong = strong * 0xff / 0xffff; in play_effect()
38 lg2ff->report->field[0]->value[4] = strong; in play_effect()
Dhid-mf.c38 int strong, weak; in mf_play() local
40 strong = effect->u.rumble.strong_magnitude; in mf_play()
43 dbg_hid("Called with 0x%04x 0x%04x.\n", strong, weak); in mf_play()
45 strong = strong * 0xff / 0xffff; in mf_play()
48 dbg_hid("Running with 0x%02x 0x%02x.\n", strong, weak); in mf_play()
51 mf->report->field[0]->value[1] = strong; in mf_play()
Dhid-pl.c43 s32 *strong; member
61 *plff->strong = left; in hid_plff_play()
80 s32 *strong; in plff_init() local
120 strong = &report->field[0]->value[2]; in plff_init()
133 strong = &report->field[2]->value[0]; in plff_init()
158 plff->strong = strong; in plff_init()
162 *strong = 0x00; in plff_init()
Dhid-dr.c36 int strong, weak; in drff_play() local
38 strong = effect->u.rumble.strong_magnitude; in drff_play()
41 dbg_hid("called with 0x%04x 0x%04x", strong, weak); in drff_play()
43 if (strong || weak) { in drff_play()
44 strong = strong * 0xff / 0xffff; in drff_play()
48 this value is set, it causes the strong rumble to function in drff_play()
56 drff->report->field[0]->value[4] = strong; in drff_play()
68 dbg_hid("running with 0x%02x 0x%02x", strong, weak); in drff_play()
Dhid-holtekff.c43 * 1: very strong rumble
45 * 3: very strong rumble
50 * 8: strong periodic rumble, short intervals
51 * 9: very strong rumble
53 * b: very strong periodic rumble, very short intervals
56 * bit 7: left (strong) motor enabled
/Linux-v5.15/arch/xtensa/boot/lib/
DMakefile20 CFLAGS_REMOVE_inflate.o += -fstack-protector -fstack-protector-strong
21 CFLAGS_REMOVE_zmem.o += -fstack-protector -fstack-protector-strong
22 CFLAGS_REMOVE_inftrees.o += -fstack-protector -fstack-protector-strong
23 CFLAGS_REMOVE_inffast.o += -fstack-protector -fstack-protector-strong
/Linux-v5.15/Documentation/locking/
Dlockdep-design.rst512 Dependency types and strong dependency paths:
571 "strong" path, which indicates the strong dependency throughout each dependency
573 -(xR)-> and -(Sx)->. In other words, a "strong" path is a path from a lock
579 We will see why the path is called "strong" in next section.
588 If there is a closed strong path (i.e. a strong circle), then there is a
589 combination of locking sequences that causes deadlock. I.e. a strong circle is
594 If there is no closed strong path (i.e. strong circle), then there is no
595 combination of locking sequences that could cause deadlock. I.e. strong
598 With these two Lemmas, we can easily say a closed strong path is both sufficient
599 and necessary for deadlocks, therefore a closed strong path is equivalent to
[all …]
/Linux-v5.15/drivers/w1/
Dw1_io.c97 * Pre-write operation, currently only supporting strong pullups.
98 * Program the hardware for a strong pullup, if one has been requested and
114 * Post-write operation, currently only supporting strong pullups.
115 * If a strong pullup was requested, clear it if the hardware supports
432 * w1_next_pullup() - register for a strong pullup
436 * Put out a strong pull-up of the specified duration after the next write
437 * operation. Not all hardware supports strong pullups. Hardware that
438 * doesn't support strong pullups will sleep for the given time after the
439 * write operation without a strong pullup. This is a one shot request for
/Linux-v5.15/drivers/android/
Dbinder.c755 static int binder_inc_node_nilocked(struct binder_node *node, int strong, in binder_inc_node_nilocked() argument
764 if (strong) { in binder_inc_node_nilocked()
771 pr_err("invalid inc strong node for %d\n", in binder_inc_node_nilocked()
804 static int binder_inc_node(struct binder_node *node, int strong, int internal, in binder_inc_node() argument
810 ret = binder_inc_node_nilocked(node, strong, internal, target_list); in binder_inc_node()
817 int strong, int internal) in binder_dec_node_nilocked() argument
824 if (strong) { in binder_dec_node_nilocked()
876 static void binder_dec_node(struct binder_node *node, int strong, int internal) in binder_dec_node() argument
881 free_node = binder_dec_node_nilocked(node, strong, internal); in binder_dec_node()
948 * and cleanup is needed. Calling with strong=0 and internal=1 in binder_dec_node_tmpref()
[all …]
Dbinder_internal.h206 * @internal_strong_refs: used to take strong references when
213 * @local_strong_refs: strong user refs from local process
226 * @has_strong_ref: userspace notified of strong ref
229 * @pending_strong_ref: userspace has acked notification of strong ref
303 * @strong: strong ref count (debugging only if not locked)
314 int strong; member
/Linux-v5.15/include/linux/
Dw1.h114 * @set_pullup: Put out a strong pull-up pulse of the specified duration.
188 * @enable_pullup: allows a strong pullup
189 * @pullup_duration: time for the next strong pullup
224 /** 5V strong pullup enabled flag, 1 enabled, zero disabled. */
226 /** 5V strong pullup duration in milliseconds, zero disabled. */
Dconnector.h95 * fail under strong memory pressure.
118 * fail under strong memory pressure.
/Linux-v5.15/tools/testing/selftests/bpf/progs/
Dlinked_vars2.c9 /* when an extern is defined as both strong and weak, resulting symbol will be strong */
/Linux-v5.15/tools/memory-model/Documentation/
Dexplanation.txt780 Strong fences, including smp_mb() and synchronize_rcu(), force
811 Any store which propagates to C before a strong fence is
814 the strong fence are executed on C.
816 The propagation ordering enforced by release fences and strong fences
820 strong fences are A-cumulative. By contrast, smp_wmb() fences are not
832 The fences which affect propagation order (i.e., strong, release, and
843 A strong fence event occurs between some X and F in program
973 A strong (smp_mb() or synchronize_rcu()) fence occurs between
1146 The LKMM requires that smp_rmb(), acquire fences, and strong fences
1150 case of a strong fence, the CPU first has to wait for all of its
[all …]
/Linux-v5.15/drivers/media/dvb-frontends/
Dau8522_dig.c696 u16 strong; in au8522_led_status() local
705 strong = led_config->qam256_strong; in au8522_led_status()
707 strong = led_config->qam64_strong; in au8522_led_status()
709 strong = led_config->vsb8_strong; in au8522_led_status()
711 if (*snr >= strong) in au8522_led_status()
717 (((strong < *snr) ? (*snr - strong) : (strong - *snr)) <= 10)) in au8522_led_status()
762 * strong signals that can show at 100% in au8522_read_signal_strength()
/Linux-v5.15/tools/perf/util/
Dsetup.py22 if not clang_has_option("-fstack-protector-strong"):
23 vars[var] = sub("-fstack-protector-strong", "", vars[var])
/Linux-v5.15/Documentation/w1/masters/
Dds2490.rst25 - The 5V strong pullup is supported with a minimum of 5.9mA and a
35 buffer, and strong pullup all in one command, instead of the current
/Linux-v5.15/drivers/input/
Dff-memless.c248 unsigned int strong, weak, i; in ml_combine_effects() local
272 strong = (u32)new->u.rumble.strong_magnitude * gain / 0xffff; in ml_combine_effects()
275 if (effect->u.rumble.strong_magnitude + strong) in ml_combine_effects()
279 new->direction, strong); in ml_combine_effects()
288 min(strong + effect->u.rumble.strong_magnitude, in ml_combine_effects()
/Linux-v5.15/drivers/w1/masters/
Dds2490.c92 #define ST_SPUA 0x01 /* Strong Pull-up is active */
131 /* Strong PullUp
135 /* spu_bit contains COMM_SPU or 0 depending on if the strong pullup
230 ds_print_msg(buf, "strong pullup duration", 2); in ds_dump_status()
303 /* Always allow strong pullup which allow individual writes to use in ds_reset_device()
304 * the strong pullup. in ds_reset_device()
307 pr_err("ds_reset_device: Error allowing strong pullup\n"); in ds_reset_device()
308 /* Chip strong pullup time was cleared. */ in ds_reset_device()
/Linux-v5.15/drivers/power/supply/
Disp1704_charger.c103 /* Enable strong pull-up on DP (1.5K) and reset */ in isp1704_charger_type()
142 /* Enable strong pull-up on DP (1.5K) and reset */ in isp1704_charger_verify()
149 /* Disable strong pull-up on DP (1.5K) */ in isp1704_charger_verify()
161 /* Disable strong pull-up on DP (1.5K) */ in isp1704_charger_verify()
/Linux-v5.15/mm/kasan/
Dsw_tags.c54 * Ideally the tags use strong randomness to prevent any attempts to predict
55 * them during explicit exploit attempts. But strong randomness is expensive,
/Linux-v5.15/kernel/entry/
DMakefile9 CFLAGS_REMOVE_common.o = -fstack-protector -fstack-protector-strong

12345678