| /linux/Documentation/w1/slaves/ |
| H A D | w1_therm.rst | 45 powered devices are detected on the bus (and strong pullup is enabled
57 A strong pullup will be applied during the conversion if required.
100 strong pullup, 1 to enable autodetection or 2 to force strong pullup.
103 If so, it will activate the master's strong pullup.
105 (seems to be the case with some DS18S20) the strong pullup can
108 If the strong pullup is enabled, the master's strong pullup will be
110 does support the strong pullup (or it falls back to a pullup
113 sufficient. The strong pullup is designed to provide the additional
|
| /linux/drivers/hid/ |
| H A D | hid-emsff.c | 27 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()
|
| H A D | hid-lg2ff.c | 27 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()
|
| H A D | hid-mf.c | 38 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()
|
| H A D | hid-pl.c | 43 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()
|
| H A D | hid-dr.c | 36 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()
|
| H A D | hid-holtekff.c | 43 * 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
|
| H A D | hid-megaworld.c | 21 s32 *strong; member
30 *mwctrl->strong = effect->u.rumble.strong_magnitude >> 8; in mwctrl_play()
82 mwctrl->strong = &report->field[2]->value[0]; in mwctrl_init()
|
| /linux/tools/memory-model/ |
| H A D | linux-kernel.cat | 65 let strong-fence = mb | gp
67 let nonrw-fence = strong-fence | po-rel | acq-po
97 (* Propagation: Ordering from release operations and strong fences. *)
100 let cumul-fence = [Marked] ; (A-cumul(strong-fence | po-rel) | wmb |
116 (* Propagation: Each non-rf link needs a strong fence. *)
117 let pb = prop ; strong-fence ; hb* ; [Marked]
140 * The synchronize_rcu() strong fence is special in that it can order not
149 * inter-CPU strong fence.
166 let strong-fence = strong
[all...] |
| /linux/arch/xtensa/boot/lib/ |
| H A D | Makefile | 23 CFLAGS_REMOVE_inflate.o += -fstack-protector -fstack-protector-strong
24 CFLAGS_REMOVE_zmem.o += -fstack-protector -fstack-protector-strong
25 CFLAGS_REMOVE_inftrees.o += -fstack-protector -fstack-protector-strong
26 CFLAGS_REMOVE_inffast.o += -fstack-protector -fstack-protector-strong
|
| /linux/Documentation/locking/ |
| H A D | lockdep-design.rst | 512 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/drivers/w1/ |
| H A D | w1_io.c | 97 * 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/include/linux/ |
| H A D | w1.h | 115 * @set_pullup: Put out a strong pull-up pulse of the specified duration.
189 * @enable_pullup: allows a strong pullup
190 * @pullup_duration: time for the next strong pullup
225 /** 5V strong pullup enabled flag, 1 enabled, zero disabled. */
227 /** 5V strong pullup duration in milliseconds, zero disabled. */
|
| H A D | connector.h | 97 * fail under strong memory pressure.
123 * fail under strong memory pressure.
|
| /linux/tools/testing/selftests/bpf/progs/ |
| H A D | linked_vars2.c | 9 /* when an extern is defined as both strong and weak, resulting symbol will be strong */
|
| /linux/drivers/media/dvb-frontends/ |
| H A D | au8522_dig.c | 696 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/tools/memory-model/Documentation/ |
| H A D | explanation.txt | 833 Strong fences, including smp_mb() and synchronize_rcu(), force
864 Any store which propagates to C before a strong fence is
867 the strong fence are executed on C.
869 The propagation ordering enforced by release fences and strong fences
873 strong fences are A-cumulative. By contrast, smp_wmb() fences are not
885 The fences which affect propagation order (i.e., strong, release, and
896 A strong fence event occurs between some X and F in program
1039 at least as strong as atomic updates with release-barrier semantics.)
1056 A strong (smp_mb() or synchronize_rcu()) fence occurs between
1229 The LKMM requires that smp_rmb(), acquire fences, and strong fences
[all …]
|
| /linux/Documentation/devicetree/bindings/pinctrl/ |
| H A D | spacemit,k1-pinctrl.yaml | 69 typical value for selecting bias pull up or strong pull up.
71 1: strong bias pull up
|
| H A D | thead,th1520-pinctrl.yaml | 28 addition to a special strong pull up.
99 description: Enable the strong 2.1kOhm pull-up or regular 48kOhm pull-up
|
| /linux/Documentation/w1/masters/ |
| H A D | ds2490.rst | 25 - 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/drivers/w1/masters/ |
| H A D | ds2490.c | 92 #define ST_SPUA 0x01 /* Strong Pull-up is active */
133 /* Strong PullUp
137 /* spu_bit contains COMM_SPU or 0 depending on if the strong pullup
229 dev_dbg(dev, "strong pullup duration: 0x%02x", buf[2]); in ds_dump_status()
299 /* Always allow strong pullup which allow individual writes to use in ds_reset_device()
300 * the strong pullup. in ds_reset_device()
304 "%s: Error allowing strong pullup\n", __func__); in ds_reset_device()
305 /* Chip strong pullup time was cleared. */ in ds_reset_device()
|
| /linux/drivers/power/supply/ |
| H A D | isp1704_charger.c | 103 /* 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/tools/perf/util/ |
| H A D | setup.py | 42 if not clang_has_option("-fstack-protector-strong"):
43 vars[var] = sub("-fstack-protector-strong", "", vars[var])
|
| /linux/fs/crypto/ |
| H A D | fname.c | 38 * bytes), so we also need to use a strong hash to abbreviate long names.
43 * no-key names that abbreviate the ciphertext using the strong hash to fit in
67 * the strong hash and thus includes the 'sha256' field. This isn't simply
384 /* Compute strong hash of remaining part of name. */ in fscrypt_fname_disk_to_usr()
507 * we'll need to match against a fscrypt_nokey_name that includes a strong hash.
|
| /linux/mm/kasan/ |
| H A D | sw_tags.c | 59 * Ideally the tags use strong randomness to prevent any attempts to predict
60 * them during explicit exploit attempts. But strong randomness is expensive,
|