| /linux-4.4.14/drivers/hid/ |
| D | hid-lg2ff.c | 39 int weak, strong; in play_effect() local
41 strong = effect->u.rumble.strong_magnitude; in play_effect()
44 if (weak || strong) { in play_effect()
46 strong = strong * 0xff / 0xffff; in play_effect()
50 lg2ff->report->field[0]->value[4] = strong; in play_effect()
|
| D | hid-emsff.c | 39 int weak, strong; in emsff_play() local
42 strong = effect->u.rumble.strong_magnitude; in emsff_play()
44 dbg_hid("called with 0x%04x 0x%04x\n", strong, weak); in emsff_play()
47 strong = strong * 0xff / 0xffff; in emsff_play()
50 emsff->report->field[0]->value[2] = strong; in emsff_play()
52 dbg_hid("running with 0x%02x 0x%02x\n", strong, weak); in emsff_play()
|
| D | hid-pl.c | 55 s32 *strong; member
73 *plff->strong = left; in hid_plff_play()
92 s32 *strong; in plff_init() local
132 strong = &report->field[0]->value[2]; in plff_init()
145 strong = &report->field[2]->value[0]; in plff_init()
170 plff->strong = strong; in plff_init()
174 *strong = 0x00; in plff_init()
|
| D | hid-dr.c | 48 int strong, weak; in drff_play() local
50 strong = effect->u.rumble.strong_magnitude; in drff_play()
53 dbg_hid("called with 0x%04x 0x%04x", strong, weak); in drff_play()
55 if (strong || weak) { in drff_play()
56 strong = strong * 0xff / 0xffff; in drff_play()
68 drff->report->field[0]->value[4] = strong; in drff_play()
80 dbg_hid("running with 0x%02x 0x%02x", strong, weak); in drff_play()
|
| /linux-4.4.14/Documentation/w1/slaves/ |
| D | w1_therm | 39 strong pullup, 1 to enable autodetection or 2 to force strong pullup.
42 If so, it will activate the master's strong pullup.
44 (seems to be the case with some DS18S20) the strong pullup can
46 If the strong pullup is enabled, the master's strong pullup will be
48 does support the strong pullup (or it falls back to a pullup
51 sufficient. The strong pullup is designed to provide the additional
|
| D | w1_ds28e04 | 17 attribute "crccheck". The strong pull-up can optionally be enabled/disabled
|
| /linux-4.4.14/drivers/media/dvb-frontends/ |
| D | au8522_dig.c | 709 u16 strong; in au8522_led_status() local
718 strong = led_config->qam256_strong; in au8522_led_status()
720 strong = led_config->qam64_strong; in au8522_led_status()
722 strong = led_config->vsb8_strong; in au8522_led_status()
724 if (*snr >= strong) in au8522_led_status()
730 (((strong < *snr) ? (*snr - strong) : (strong - *snr)) <= 10)) in au8522_led_status()
|
| /linux-4.4.14/drivers/android/ |
| D | binder.c | 267 int strong; member
926 static int binder_inc_node(struct binder_node *node, int strong, int internal, in binder_inc_node() argument
929 if (strong) { in binder_inc_node()
961 static int binder_dec_node(struct binder_node *node, int strong, int internal) in binder_dec_node() argument
963 if (strong) { in binder_dec_node()
1099 if (ref->strong) in binder_delete_ref()
1115 static int binder_inc_ref(struct binder_ref *ref, int strong, in binder_inc_ref() argument
1120 if (strong) { in binder_inc_ref()
1121 if (ref->strong == 0) { in binder_inc_ref()
1126 ref->strong++; in binder_inc_ref()
[all …]
|
| /linux-4.4.14/drivers/input/ |
| D | ff-memless.c | 260 unsigned int strong, weak, i; in ml_combine_effects() local
284 strong = (u32)new->u.rumble.strong_magnitude * gain / 0xffff; in ml_combine_effects()
287 if (effect->u.rumble.strong_magnitude + strong) in ml_combine_effects()
291 new->direction, strong); in ml_combine_effects()
300 min(strong + effect->u.rumble.strong_magnitude, in ml_combine_effects()
|
| /linux-4.4.14/drivers/input/joystick/ |
| D | xpad.c | 802 __u16 strong; in xpad_play_effect() local
808 strong = effect->u.rumble.strong_magnitude; in xpad_play_effect()
816 xpad->odata[3] = strong / 256; /* left actuator */ in xpad_play_effect()
826 xpad->odata[3] = strong / 256; /* left actuator? */ in xpad_play_effect()
840 xpad->odata[5] = strong / 256; in xpad_play_effect()
859 xpad->odata[8] = strong / 256; /* left actuator */ in xpad_play_effect()
|
| /linux-4.4.14/Documentation/w1/masters/ |
| D | ds2490 | 22 - The 5V strong pullup is supported with a minimum of 5.9mA and a
32 buffer, and strong pullup all in one command, instead of the current
|
| /linux-4.4.14/tools/perf/bench/ |
| D | numa.c | 882 static void calc_convergence_compression(int *strong) in calc_convergence_compression() argument
894 *strong = 0; in calc_convergence_compression()
904 *strong = 1; in calc_convergence_compression()
906 *strong = 0; in calc_convergence_compression()
919 int strong; in calc_convergence() local
1000 calc_convergence_compression(&strong); in calc_convergence()
1002 if (strong && process_groups == g->p.nr_proc) { in calc_convergence()
|
| /linux-4.4.14/Documentation/devicetree/bindings/mtd/ |
| D | partition.txt | 4 on platforms which have strong conventions about which portions of a flash are
|
| /linux-4.4.14/drivers/media/usb/dvb-usb/ |
| D | af9005-fe.c | 57 int strong; member
483 if (temp != state->strong) { in af9005_fe_read_status()
485 state->strong = temp; in af9005_fe_read_status()
1225 state->strong = -1; in af9005_fe_set_frontend()
|
| /linux-4.4.14/drivers/net/wireless/iwlwifi/mvm/ |
| D | rs.c | 2024 s32 sr, int weak, int strong, in rs_get_tpc_action() argument
2060 strong != TPC_INVALID) { in rs_get_tpc_action()
2097 int weak, strong; in rs_tpc_perform() local
2124 rs_get_adjacent_txp(mvm, cur, &weak, &strong); in rs_tpc_perform()
2132 if (strong != TPC_INVALID) in rs_tpc_perform()
2133 strong_tpt = window[strong].average_tpt; in rs_tpc_perform()
2137 cur, current_tpt, sr, weak, strong, in rs_tpc_perform()
2140 action = rs_get_tpc_action(mvm, sr, weak, strong, in rs_tpc_perform()
2147 } else if (strong == TPC_INVALID && in rs_tpc_perform()
2159 lq_sta->lq.reduced_tpc = strong; in rs_tpc_perform()
|
| /linux-4.4.14/fs/btrfs/ |
| D | Kconfig | 19 expected to change unless there are strong reasons to do so. If there
|
| /linux-4.4.14/Documentation/video4linux/ |
| D | README.pvrusb2 | 26 This driver has a strong separation of layers. They are very
51 simultaneously access the driver. I have a strong sense of fairness
|
| /linux-4.4.14/Documentation/filesystems/pohmelfs/ |
| D | design_notes.txt | 65 POHMELFS is capable of full data channel encryption and/or strong crypto hashing.
|
| /linux-4.4.14/Documentation/w1/ |
| D | w1.generic | 87 w1_master_pullup - (rw) 5V strong pullup 0 enabled, 1 disabled
|
| /linux-4.4.14/Documentation/security/ |
| D | keys-trusted-encrypted.txt | 126 trusted key provides strong guarantees that the EVM key has not been
|
| /linux-4.4.14/Documentation/filesystems/nfs/ |
| D | knfsd-stats.txt | 94 a strong indication, for a couple of reasons:
|
| /linux-4.4.14/arch/arm/boot/dts/ |
| D | vexpress-v2m-rs1.dtsi | 13 * original variant (vexpress-v2m.dtsi), but there is a strong
|
| D | vexpress-v2m.dtsi | 13 * RS1 variant (vexpress-v2m-rs1.dtsi), but there is a strong
|
| /linux-4.4.14/arch/arm64/boot/dts/arm/ |
| D | vexpress-v2m-rs1.dtsi | 13 * original variant (vexpress-v2m.dtsi), but there is a strong
|
| /linux-4.4.14/Documentation/connector/ |
| D | connector.txt | 79 softirq context, but may silently fail under strong memory pressure.
|
| /linux-4.4.14/Documentation/input/ |
| D | ff.txt | 151 factor depending on how strong they want effects to be. This setting is
|
| D | input.txt | 131 all do. If you don't have any strong reason to use this module, use usbhid
|
| /linux-4.4.14/Documentation/timers/ |
| D | NO_HZ.txt | 77 is strong motivation to avoid sending scheduling-clock interrupts to
117 again strong motivation to avoid sending scheduling-clock interrupts.
|
| /linux-4.4.14/ |
| D | Makefile | 658 stackp-flag := -fstack-protector-strong
661 -fstack-protector-strong not supported by compiler)
|
| /linux-4.4.14/Documentation/ |
| D | stable_api_nonsense.txt | 23 tree, all of which has made Linux into such a strong, stable, and mature
|
| D | CodingStyle | 783 difficult-to-find bugs. If the C language included a strong distinction
|
| /linux-4.4.14/Documentation/powerpc/ |
| D | firmware-assisted-dump.txt | 28 dump offers several strong, practical advantages:
|
| /linux-4.4.14/Documentation/sound/alsa/soc/ |
| D | DPCM.txt | 164 components (as some DSPs have strong requirements for the ordering DAI/DSP
|
| /linux-4.4.14/Documentation/dvb/ |
| D | avermedia.txt | 195 onto. (i.e. any whose signal is strong enough at your
|
| /linux-4.4.14/arch/ |
| D | Kconfig | 418 gcc with the feature backported ("-fstack-protector-strong").
|
| /linux-4.4.14/Documentation/development-process/ |
| D | 1.Intro | 165 the mainline. No matter how strong the original developer's skills are,
|
| D | 2.Process | 412 the Cc: header for all involved. In the absence of a strong reason (such
|
| /linux-4.4.14/Documentation/power/ |
| D | swsusp.txt | 180 Q: I do not understand why you have such strong objections to idea of
|
| /linux-4.4.14/arch/arm/mm/ |
| D | Kconfig | 281 <http://developer.intel.com/design/strong/sa110.htm>.
|
| /linux-4.4.14/Documentation/sysctl/ |
| D | vm.txt | 698 panic_on_oom=2+kdump gives you very strong tool to investigate
|
| /linux-4.4.14/Documentation/networking/ |
| D | filter.txt | 966 They had to be carried over from classic to have strong performance of
|
| /linux-4.4.14/Documentation/RCU/ |
| D | RTFP.txt | 374 Concurrent access to skip lists. Has both weak and strong search.
|