/linux/drivers/char/ |
H A D | nwbutton.c | 29 static int button_press_count; /* The count of button presses */ 38 static int reboot_count = NUM_PRESSES_REBOOT; /* Number of presses to reboot */ 42 * to be called when a particular number of button presses occurs. 45 * to be performed by the kernel on different numbers of button presses ;). 106 * matches the current count of button presses. It starts at the beginning 126 * mean you have ended the sequence of key presses, and this function is
|
H A D | nwbutton.h | 14 #define NUM_PRESSES_REBOOT 2 /* How many presses to activate shutdown */
|
H A D | Kconfig | 179 The number of presses to initiate the shutdown is two by default, 182 driver as a module, you can specify the number of presses at load
|
/linux/Documentation/devicetree/bindings/power/reset/ |
H A D | restart-poweroff.txt | 5 user presses a button.
|
/linux/drivers/power/reset/ |
H A D | restart-poweroff.c | 4 * until the user presses a button for example.
|
H A D | Kconfig | 211 user presses a key. u-boot then boots into Linux.
|
/linux/Documentation/devicetree/bindings/input/touchscreen/ |
H A D | hideep.txt | 18 be used for reporting button presses. The array can
|
/linux/Documentation/devicetree/bindings/input/ |
H A D | input.yaml | 20 button presses.
|
/linux/drivers/accessibility/speakup/ |
H A D | fakekey.c | 3 * Functions for simulating key presses.
|
/linux/drivers/hid/ |
H A D | hid-speedlink.c | 31 * able to map keyboard events to the button presses. in speedlink_input_mapping()
|
H A D | hid-holtek-kbd.c | 22 * - The report descriptor reports on caps/scroll/num lock key presses, but
|
H A D | hid-letsketch.c | 13 * resp. "e" key presses.
|
/linux/drivers/input/misc/ |
H A D | axp20x-pek.c | 288 * and otherwise we end up reporting all presses twice. in axp20x_pek_should_register_input() 372 * Clear interrupts from button presses during suspend, to avoid in axp20x_pek_resume_noirq()
|
/linux/Documentation/ABI/testing/ |
H A D | sysfs-platform-msi-laptop | 51 If user presses Fn+F10 too frequent, turbo mode state is not
|
/linux/drivers/platform/x86/dell/ |
H A D | dell-wmi-privacy.c | 84 * 1) User presses key. HW does stuff with this key (timeout is started) 327 * Unlike keys where only presses matter, userspace may act in dell_privacy_wmi_probe()
|
/linux/Documentation/firmware-guide/acpi/ |
H A D | video_extension.rst | 79 i) For some laptops, when user presses the hotkey, a scancode will be
|
/linux/Documentation/driver-api/ |
H A D | rfkill.rst | 16 The subsystem also provides the ability to react on button presses and
|
/linux/drivers/input/keyboard/ |
H A D | imx_keypad.c | 257 * interrupt for future key presses (clear the KDI in imx_keypad_check_for_events() 271 * attempt to detect multiple key presses and enable in imx_keypad_check_for_events()
|
H A D | tegra-kbc.c | 180 * If so ignore the key presses for this iteration. in tegra_kbc_report_keys() 215 /* Ignore the key presses for this iteration? */ in tegra_kbc_report_keys()
|
/linux/arch/arm/boot/dts/nvidia/ |
H A D | tegra30-asus-nexus7-tilapia.dtsi | 190 * and this results in unwanted key-presses handled by
|
/linux/arch/parisc/kernel/ |
H A D | process.c | 125 /* reboot if user presses RETURN key */ in machine_power_off()
|
/linux/Documentation/admin-guide/laptops/ |
H A D | thinkpad-acpi.rst | 191 some important events and also keyboard hot key presses to the operating 203 Some of these events refer to hot key presses, but not all of them. 327 will cause hot key presses that require NVRAM polling 427 key presses until a S3 or S4 ACPI 1163 normal key presses to the operating system (thinkpad-acpi is not
|
/linux/Documentation/ABI/obsolete/ |
H A D | sysfs-driver-hid-roccat-isku | 24 windows and application keys, to prevent accidental presses.
|
H A D | sysfs-driver-hid-roccat-ryos | 85 windows and application keys, to prevent accidental presses.
|
/linux/Documentation/input/joydev/ |
H A D | joystick-api.rst | 146 presses happened at the same time, and similar.
|