Home
last modified time | relevance | path

Searched full:presses (Results 1 – 25 of 40) sorted by relevance

12

/kernel/linux/linux-5.10/drivers/char/
Dnwbutton.c29 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
Dnwbutton.h14 #define NUM_PRESSES_REBOOT 2 /* How many presses to activate shutdown */
DKconfig177 The number of presses to initiate the shutdown is two by default,
180 driver as a module, you can specify the number of presses at load
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/power/reset/
Drestart-poweroff.txt5 user presses a button.
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/input/
Datmel,captouch.txt16 be used for reporting button presses. The array can
Dinput.yaml20 button presses.
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/input/touchscreen/
Dhideep.txt18 be used for reporting button presses. The array can
/kernel/linux/linux-5.10/drivers/power/reset/
Drestart-poweroff.c4 * until the user presses a button for example.
DKconfig185 user presses a key. u-boot then boots into Linux.
/kernel/linux/linux-5.10/drivers/hid/
Dhid-speedlink.c31 * able to map keyboard events to the button presses. in speedlink_input_mapping()
Dhid-plantronics.c130 if (!value) /* Handle key presses only. */ in plantronics_event()
Dhid-holtek-kbd.c22 * - The report descriptor reports on caps/scroll/num lock key presses, but
/kernel/linux/linux-5.10/Documentation/ABI/testing/
Dsysfs-platform-msi-laptop51 If user presses Fn+F10 too frequent, turbo mode state is not
/kernel/linux/linux-5.10/drivers/platform/x86/
Dpeaq-wmi.c28 * We ignore events for 0.5s after the first event to avoid reporting 2 presses.
/kernel/linux/linux-5.10/drivers/input/misc/
Daxp20x-pek.c276 * and otherwise we end up reporting all presses twice. in axp20x_pek_should_register_input()
399 * Clear interrupts from button presses during suspend, to avoid in axp20x_pek_resume_noirq()
/kernel/linux/linux-5.10/Documentation/firmware-guide/acpi/
Dvideo_extension.rst79 i) For some laptops, when user presses the hotkey, a scancode will be
/kernel/linux/linux-5.10/Documentation/driver-api/
Drfkill.rst16 The subsystem also provides the ability to react on button presses and
/kernel/linux/linux-5.10/arch/arm/boot/dts/
Dtegra30-asus-nexus7-tilapia.dtsi206 * and this results in unwanted key-presses handled by
/kernel/linux/linux-5.10/drivers/input/keyboard/
Dimx_keypad.c255 * interrupt for future key presses (clear the KDI in imx_keypad_check_for_events()
269 * attempt to detect multiple key presses and enable in imx_keypad_check_for_events()
Dtegra-kbc.c180 * 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()
/kernel/linux/linux-5.10/Documentation/admin-guide/laptops/
Dthinkpad-acpi.rst188 some important events and also keyboard hot key presses to the operating
200 Some of these events refer to hot key presses, but not all of them.
324 will cause hot key presses that require NVRAM polling
424 key presses until a S3 or S4 ACPI
1151 normal key presses to the operating system (thinkpad-acpi is not
/kernel/linux/linux-5.10/Documentation/ABI/obsolete/
Dsysfs-driver-hid-roccat-isku24 windows and application keys, to prevent accidental presses.
Dsysfs-driver-hid-roccat-ryos85 windows and application keys, to prevent accidental presses.
/kernel/linux/linux-5.10/Documentation/input/joydev/
Djoystick-api.rst146 presses happened at the same time, and similar.
/kernel/linux/linux-5.10/Documentation/userspace-api/media/rc/
Drc-protos.rst425 describes both button presses and pointer movements. The protocol encodes

12