Home
last modified time | relevance | path

Searched refs:strong (Results 1 – 25 of 64) sorted by relevance

123

/Linux-v5.10/drivers/hid/
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-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-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()
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-microsoft.c35 __u8 strong; member
299 r->magnitude[MAGNITUDE_STRONG] = ms->strong; /* left actuator */ in ms_ff_worker()
319 ms->strong = ((u32) effect->u.rumble.strong_magnitude * 100) / U16_MAX; in ms_play_effect()
/Linux-v5.10/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.10/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.10/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()
/Linux-v5.10/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
Dw1_ds28e04.rst22 attribute "crccheck". The strong pull-up can optionally be enabled/disabled
/Linux-v5.10/drivers/android/
Dbinder.c365 int strong; member
1161 static int binder_inc_node_nilocked(struct binder_node *node, int strong, in binder_inc_node_nilocked() argument
1170 if (strong) { in binder_inc_node_nilocked()
1210 static int binder_inc_node(struct binder_node *node, int strong, int internal, in binder_inc_node() argument
1216 ret = binder_inc_node_nilocked(node, strong, internal, target_list); in binder_inc_node()
1223 int strong, int internal) in binder_dec_node_nilocked() argument
1230 if (strong) { in binder_dec_node_nilocked()
1282 static void binder_dec_node(struct binder_node *node, int strong, int internal) in binder_dec_node() argument
1287 free_node = binder_dec_node_nilocked(node, strong, internal); in binder_dec_node()
1382 } else if (need_strong_ref && !ref->data.strong) { in binder_get_ref_olocked()
[all …]
/Linux-v5.10/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.10/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.10/kernel/entry/
DMakefile9 CFLAGS_REMOVE_common.o = -fstack-protector -fstack-protector-strong
/Linux-v5.10/tools/thermal/tmon/
DMakefile11 override CFLAGS+= $(call cc-option,-fstack-protector-strong)
/Linux-v5.10/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.10/arch/x86/purgatory/
DMakefile51 PURGATORY_CFLAGS_REMOVE += -fstack-protector-strong
/Linux-v5.10/tools/perf/bench/
Dnuma.c950 static void calc_convergence_compression(int *strong) in calc_convergence_compression() argument
962 *strong = 0; in calc_convergence_compression()
972 *strong = 1; in calc_convergence_compression()
974 *strong = 0; in calc_convergence_compression()
987 int strong; in calc_convergence() local
1073 calc_convergence_compression(&strong); in calc_convergence()
1075 if (strong && process_groups == g->p.nr_proc) { in calc_convergence()
/Linux-v5.10/drivers/input/joystick/
Dxpad.c1228 __u16 strong; in xpad_play_effect() local
1236 strong = effect->u.rumble.strong_magnitude; in xpad_play_effect()
1246 packet->data[3] = strong / 256; /* left actuator */ in xpad_play_effect()
1257 packet->data[3] = strong / 256; /* left actuator? */ in xpad_play_effect()
1272 packet->data[5] = strong / 256; in xpad_play_effect()
1292 packet->data[8] = strong / 512; /* left actuator */ in xpad_play_effect()
/Linux-v5.10/drivers/media/usb/dvb-usb/
Daf9005-fe.c44 int strong; member
470 if (temp != state->strong) { in af9005_fe_read_status()
472 state->strong = temp; in af9005_fe_read_status()
1212 state->strong = -1; in af9005_fe_set_frontend()
/Linux-v5.10/tools/memory-model/Documentation/
Dexplanation.txt811 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
1153 as of that time -- not just the stores received when the strong fence
[all …]
/Linux-v5.10/drivers/net/wireless/intel/iwlwifi/mvm/
Drs.c1946 s32 sr, int weak, int strong, in rs_get_tpc_action() argument
1983 strong != TPC_INVALID) { in rs_get_tpc_action()
2020 int weak, strong; in rs_tpc_perform() local
2047 rs_get_adjacent_txp(mvm, cur, &weak, &strong); in rs_tpc_perform()
2055 if (strong != TPC_INVALID) in rs_tpc_perform()
2056 strong_tpt = window[strong].average_tpt; in rs_tpc_perform()
2060 cur, current_tpt, sr, weak, strong, in rs_tpc_perform()
2063 action = rs_get_tpc_action(mvm, sr, weak, strong, in rs_tpc_perform()
2070 } else if (strong == TPC_INVALID && in rs_tpc_perform()
2082 lq_sta->lq.reduced_tpc = strong; in rs_tpc_perform()
/Linux-v5.10/Documentation/gpu/
Ddrm-kms-helpers.rst5 The DRM subsystem aims for a strong separation between core code and helper
12 This distinction between core code and helpers is especially strong in the
/Linux-v5.10/security/
DKconfig.hardening65 bool "zero-init structs passed by reference (strong)"
83 bool "zero-init anything passed by reference (very strong)"

123