Home
last modified time | relevance | path

Searched refs:scancodes (Results 1 – 14 of 14) sorted by relevance

/Linux-v5.4/drivers/input/keyboard/
Dtegra-kbc.c131 unsigned char scancodes[], in tegra_kbc_report_pressed_keys() argument
138 input_event(input, EV_MSC, MSC_SCAN, scancodes[i]); in tegra_kbc_report_pressed_keys()
145 unsigned char scancodes[KBC_MAX_KPENT]; in tegra_kbc_report_keys() local
164 scancodes[num_down] = scancode; in tegra_kbc_report_keys()
185 u8 curr_col = scancodes[i] & 0x07; in tegra_kbc_report_keys()
186 u8 curr_row = scancodes[i] >> KBC_ROW_SHIFT; in tegra_kbc_report_keys()
193 u8 col = scancodes[j] & 0x07; in tegra_kbc_report_keys()
194 u8 row = scancodes[j] >> KBC_ROW_SHIFT; in tegra_kbc_report_keys()
210 scancodes[i] += kbc->max_keys; in tegra_kbc_report_keys()
211 keycodes[i] = kbc->keycode[scancodes[i]]; in tegra_kbc_report_keys()
[all …]
DKconfig122 bool "Use HP keyboard scancodes"
133 bool "Use PrecisionBook keyboard scancodes"
/Linux-v5.4/Documentation/media/uapi/rc/
Drc-sysfs-nodes.rst72 supports it then scancodes which do not match the filter will be
86 filter to allow all valid scancodes to be processed.
88 If the hardware supports it then scancodes which do not match the filter
131 scancodes which match the filter will wake the system from e.g. suspend
148 scancodes which match the filter will wake the system from e.g. suspend
Dlirc-dev-intro.rst17 a bi-directional interface for transporting raw IR and decoded scancodes
21 decoded scancodes to and fro, the essential fops are read, write and ioctl.
24 raw IR into scancodes.
Drc-protos.rst29 how scancodes are encoded for each protocol.
81 This is done so it the scancodes and encoding is compatible with existing
336 their inverted versions, but these are not present in the scancodes.
Dlirc-read.rst63 in this mode scancodes which are either decoded by software decoders, or
/Linux-v5.4/Documentation/ABI/testing/
Dsysfs-class-rc44 If the hardware supports it then scancodes which do not match
58 scancodes to be processed.
59 If the hardware supports it then scancodes which do not match
93 scancodes which match the filter will wake the system from e.g.
108 scancodes which match the filter will wake the system from e.g.
/Linux-v5.4/drivers/media/rc/
Dlirc_dev.c129 if (kfifo_put(&fh->scancodes, *lsc)) in ir_lirc_scancode_event()
162 if (kfifo_alloc(&fh->scancodes, 32, GFP_KERNEL)) { in ir_lirc_open()
193 kfifo_free(&fh->scancodes); in ir_lirc_open()
217 kfifo_free(&fh->scancodes); in ir_lirc_close()
613 !kfifo_is_empty(&fh->scancodes)) in ir_lirc_poll()
675 if (kfifo_is_empty(&fh->scancodes)) { in ir_lirc_read_scancode()
680 !kfifo_is_empty(&fh->scancodes) || in ir_lirc_read_scancode()
692 ret = kfifo_to_user(&fh->scancodes, buffer, length, &copied); in ir_lirc_read_scancode()
DKconfig39 These eBPF programs can be used to decode IR into scancodes, for
/Linux-v5.4/include/media/
Drc-core.h77 DECLARE_KFIFO_PTR(scancodes, struct lirc_scancode);
/Linux-v5.4/arch/m68k/q40/
DREADME123 the PC scancodes x86 Linux uses. So by theory every national keyboard should
/Linux-v5.4/Documentation/admin-guide/laptops/
Dsony-laptop.rst23 The "scancodes" passed to the input system (that can be remapped with udev)
/Linux-v5.4/Documentation/input/
Dinput-programming.rst250 The keycode is an array used to map from scancodes to input system keycodes.
/Linux-v5.4/drivers/input/misc/
DKconfig368 The events will show up as scancodes F1 through F9 via evdev.