Home
last modified time | relevance | path

Searched refs:keyboard (Results 1 – 25 of 145) sorted by relevance

123456

/Linux-v4.19/drivers/input/serio/
DKconfig10 * standard AT keyboard and PS/2 mouse *
24 communicate with keyboard, mouse, etc.
33 i8042 is the chip over which the standard AT keyboard and PS/2
71 tristate "Q40 keyboard controller"
75 tristate "Parallel port keyboard adapter"
79 an additional AT keyboard, XT keyboard or PS/2 mouse.
89 tristate "Acorn RiscPC keyboard controller"
94 keyboard connected to its keyboard controller.
100 tristate "AMBA KMI keyboard controller"
104 tristate "Intel SA1111 keyboard controller"
[all …]
/Linux-v4.19/drivers/input/keyboard/
DKconfig61 tristate "Amiga keyboard"
64 Say Y here if you are running Linux on any AMIGA and have a keyboard
74 tristate "Atari keyboard"
78 Say Y here if you are running Linux on any Atari and have a keyboard
85 tristate "AT keyboard"
92 Say Y here if you want to use a standard AT or PS/2 keyboard. Usually
93 you'll need this, unless you have a different type keyboard (USB, ADB
103 bool "Use HP keyboard scancodes"
108 PS/2 keyboard, and your keyboard uses keycodes that are specific to
111 Say N if you use a standard keyboard.
[all …]
/Linux-v4.19/Documentation/devicetree/bindings/input/
Dnvidia,tegra20-kbc.txt1 * Tegra keyboard controller
24 matrix-keyboard bindings:
27 matrix-keyboard-controller spec but to be used when the KEY_FN modifier
32 - wakeup-source: configure keyboard as a wakeup source for suspend/resume
37 keyboard: keyboard {
Dspear-keyboard.txt1 * SPEAr keyboard controller
7 matrix-keyboard bindings:
9 - st,mode: keyboard mode: 0 - 9x9, 1 - 6x6, 2 - 2x2
Dcros-ec-keyb.txt3 Google's ChromeOS EC Keyboard is a simple matrix keyboard implemented on
15 keyboard. This is recommended if the EC does not have its own logic or
29 * The values below are for a US keyboard layout and
Dgpio-keys.txt1 Device-Tree bindings for input/keyboard/gpio_keys.c keyboard driver
/Linux-v4.19/Documentation/ABI/testing/
Dsysfs-platform-dell-laptop7 This file allows to control the automatic keyboard
28 turn on the keyboard backlight illumination that is
37 For example, to enable the keyboard as trigger run:
38 echo +keyboard > /sys/class/leds/dell::kbd_backlight/start_triggers
40 echo -keyboard > /sys/class/leds/dell::kbd_backlight/start_triggers
51 keyboard illumination is disabled because of inactivity.
Dsysfs-driver-toshiba_acpi5 Description: This file controls the keyboard backlight operation mode, valid
22 Description: This file controls the timeout of the keyboard backlight
26 keyboard type, the kernel 3.16 added support for the second
52 Description: This file shows the supported keyboard backlight modes
58 Note that not all keyboard types support the listed modes.
66 Description: This file shows the current keyboard backlight type,
/Linux-v4.19/drivers/misc/ibmasm/
Dremote.c150 input->data.keyboard.key_code, in print_input()
151 input->data.keyboard.key_code, in print_input()
152 input->data.keyboard.key_flag, in print_input()
153 input->data.keyboard.key_down in print_input()
174 unsigned short code = input->data.keyboard.key_code; in send_keyboard_event()
180 input_report_key(dev, key, input->data.keyboard.key_down); in send_keyboard_event()
/Linux-v4.19/drivers/staging/unisys/visorinput/
DKconfig10 console (keyboard and mouse) that is accessible through the
13 still boot with visible output in the partition desktop, but keyboard
/Linux-v4.19/Documentation/input/
Dnotifier.rst5 One can use register_keyboard_notifier to get called back on keyboard
9 - 'vc' always provide the VC for which the keyboard event applies;
25 order to "eat" the event: the notify loop is stopped and the keyboard event is
Dinput.rst37 For the most usual configuration, with one USB mouse and one USB keyboard,
48 After this, the USB keyboard will work straight away, and the USB mouse
73 When you do all of the above, you can use your USB mouse and keyboard.
109 keyboard subsection
112 ``keyboard`` is in-kernel input handler and is a part of VT code. It
113 consumes keyboard keystrokes and handles user input for VT consoles.
242 Typing a couple keys on the keyboard should be enough to check that
243 a keyboard works and is correctly connected to the kernel keyboard
/Linux-v4.19/Documentation/input/devices/
Datarikbd.rst9 The Atari Corp. Intelligent Keyboard (ikbd) is a general purpose keyboard
11 products without modification. The keyboard, with its microcontroller,
20 different applications of the keyboard, joysticks, or mouse. Limited use of
27 The keyboard always returns key make/break scan codes. The ikbd generates
28 keyboard scan codes for each key press and release. The key scan make (key
31 exists in that position on a particular keyboard. The break code for each key
61 within the ikbd, or by converting mouse motion into keyboard cursor control
64 keyboard keys.
76 relative mouse motion events will be generated: (a) while the keyboard has
77 been 'paused' ( the event will be stored until keyboard communications is
[all …]
Dbcm5974.rst42 The Apple multi-touch trackpads report both mouse and keyboard events via
45 HID mouse and keyboard, and claim the whole device. To remedy, the usb
/Linux-v4.19/Documentation/media/kapi/
Drc-core.rst8 remote controller keyboard keystrokes and mouse events.
13 a normal keyboard or mouse is handled internally on Linux\ [#f1]_. So, the
19 The main difference is that, on keyboard events, the keyboard controller
/Linux-v4.19/Documentation/ABI/obsolete/
Dsysfs-driver-hid-roccat-arvo14 Description: The keyboard can store short macros with consist of 1 button with
34 Description: The keyboard lets the user deactivate 5 certain keys like the
47 Description: The keyboard has a condensed layout without num-lock key.
/Linux-v4.19/drivers/hid/usbhid/
DKconfig15 You can't use this driver and the HIDBP (Boot Protocol) keyboard
55 to use the generic HID driver for your USB keyboard and prefer
56 to use the keyboard in its limited Boot Protocol mode instead.
/Linux-v4.19/Documentation/usb/
Dgadget_hid.txt24 /* hid descriptor for a keyboard */
92 device type (keyboard / mouse / joystick) - E.G.:
94 # hid_gadget_test /dev/hidg0 keyboard
98 values are listed at program start. In keyboard mode you can
336 printf(" keyboard options:\n"
340 printf("\n keyboard values:\n"
376 fprintf(stderr, "Usage: %s devname mouse|keyboard|joystick\n",
/Linux-v4.19/Documentation/
DSAK.txt14 From the PC keyboard, Linux has two similar but different ways of
23 SAK works correctly when the keyboard is in raw mode. This means that
46 2. On the PC keyboard, SAK kills all applications which have
/Linux-v4.19/drivers/staging/nvec/
DKconfig16 Say Y here to enable support for a keyboard connected to
20 called keyboard-nvec
/Linux-v4.19/drivers/input/
DKconfig9 tristate "Generic input layer (needed for keyboard, mouse, ...)" if EXPERT
12 Say Y here if you have any input device (mouse, keyboard, tablet,
15 keyboard and mouse.
17 Say N here if you have a headless (no monitor, no keyboard) system.
189 source "drivers/input/keyboard/Kconfig"
/Linux-v4.19/drivers/hid/
DKconfig153 Support for Asus notebook built-in keyboard and touchpad via i2c, and
154 the Asus Republic of Gamers laptop keyboard special keys.
169 tristate "Belkin Flip KVM and Wireless keyboard"
173 Support for Belkin Flip KVM and Wireless keyboard.
186 tristate "Cherry Cymotion keyboard"
190 Support for Cherry Cymotion keyboard.
227 - Prodikeys PC-MIDI keyboard.
232 multimedia keyboard, but will lack support for the musical keyboard
313 tristate "Ezkey BTC 8193 keyboard"
317 Support for Ezkey BTC 8193 keyboard.
[all …]
/Linux-v4.19/Documentation/x86/
Dusb-legacy-support.txt8 feature that allows one to use the USB mouse and keyboard as if they were
9 their classic PS/2 counterparts. This means one can use an USB keyboard to
/Linux-v4.19/drivers/staging/unisys/Documentation/
Doverview.txt15 * visorinput - keyboard and mouse
30 devices), or "console partition" (for virtual keyboard and mouse devices).
47 provide a guest graphics console are for keyboard and mouse (via visorinput).
165 (controls keyboard, video, and mouse), whereas bus 2 corresponds to the
209 "keyboard". Note that this name is provided by
288 (e.g., /sys/class/input/) for virtual keyboard and virtual mouse devices.
289 A s-Par virtual keyboard device maps 1-to-1 with a Linux input device
294 automatically find and properly use s-Par virtual keyboard and mouse devices.
295 As the s-Par back-end reports keyboard and mouse activity via events on the
/Linux-v4.19/drivers/tty/vt/
DMakefile8 selection.o keyboard.o

123456