1 # SPDX-License-Identifier: GPL-2.0-only
3 # Input core configuration
5 menuconfig INPUT_KEYBOARD
9 Say Y here, and a list of supported keyboards will be displayed.
10 This option doesn't affect the kernel.
17 tristate "ADC Ladder Buttons"
21 This driver implements support for buttons connected
22 to an ADC using a resistor ladder.
24 Say Y here if your device has such buttons connected to an ADC. Your
25 board-specific setup logic must also provide a configuration data
26 for mapping voltages to buttons.
28 To compile this driver as a module, choose M here: the
29 module will be called adc_keys.
31 config KEYBOARD_ADP5520
32 tristate "Keypad Support for ADP5520 PMIC"
33 depends on PMIC_ADP5520
35 This option enables support for the keypad scan matrix
36 on Analog Devices ADP5520 PMICs.
38 To compile this driver as a module, choose M here: the module will
39 be called adp5520-keys.
41 config KEYBOARD_ADP5588
42 tristate "ADP5588/87 I2C QWERTY Keypad and IO Expander"
45 Say Y here if you want to use a ADP5588/87 attached to your
48 To compile this driver as a module, choose M here: the
49 module will be called adp5588-keys.
51 config KEYBOARD_ADP5589
52 tristate "ADP5585/ADP5589 I2C QWERTY Keypad and IO Expander"
55 Say Y here if you want to use a ADP5585/ADP5589 attached to your
58 To compile this driver as a module, choose M here: the
59 module will be called adp5589-keys.
62 tristate "Amiga keyboard"
65 Say Y here if you are running Linux on any AMIGA and have a keyboard
68 To compile this driver as a module, choose M here: the
69 module will be called amikbd.
74 config KEYBOARD_APPLESPI
75 tristate "Apple SPI keyboard and trackpad"
76 depends on ACPI && EFI
78 depends on X86 || COMPILE_TEST
82 Say Y here if you are running Linux on any Apple MacBook8,1 or later,
83 or any MacBookPro13,* or MacBookPro14,*.
85 You will also need to enable appropriate SPI master controllers:
86 spi_pxa2xx_platform and spi_pxa2xx_pci for MacBook8,1, and
87 spi_pxa2xx_platform and intel_lpss_pci for the rest.
89 To compile this driver as a module, choose M here: the
90 module will be called applespi.
93 tristate "Atari keyboard"
97 Say Y here if you are running Linux on any Atari and have a keyboard
100 To compile this driver as a module, choose M here: the
101 module will be called atakbd.
103 config KEYBOARD_ATKBD
104 tristate "AT keyboard"
108 select SERIO_I8042 if ARCH_MIGHT_HAVE_PC_SERIO
109 select SERIO_GSCPS2 if GSC
111 Say Y here if you want to use a standard AT or PS/2 keyboard. Usually
112 you'll need this, unless you have a different type keyboard (USB, ADB
113 or other). This also works for AT and PS/2 keyboards connected over a
114 PS/2 to serial converter.
118 To compile this driver as a module, choose M here: the
119 module will be called atkbd.
121 config KEYBOARD_ATKBD_HP_KEYCODES
122 bool "Use HP keyboard scancodes"
123 depends on PARISC && KEYBOARD_ATKBD
126 Say Y here if you have a PA-RISC machine and want to use an AT or
127 PS/2 keyboard, and your keyboard uses keycodes that are specific to
130 Say N if you use a standard keyboard.
132 config KEYBOARD_ATKBD_RDI_KEYCODES
133 bool "Use PrecisionBook keyboard scancodes"
134 depends on KEYBOARD_ATKBD_HP_KEYCODES
137 If you have an RDI PrecisionBook, say Y here if you want to use its
138 built-in keyboard (as opposed to an external keyboard).
140 The PrecisionBook has five keys that conflict with those used by most
141 AT and PS/2 keyboards. These are as follows:
143 PrecisionBook Standard AT or PS/2
149 Left 102nd key (the key to the right of Left Shift)
151 If you say N here, and use the PrecisionBook keyboard, then each key
152 in the left-hand column will be interpreted as the corresponding key
153 in the right-hand column.
155 If you say Y here, and use an external keyboard, then each key in the
156 right-hand column will be interpreted as the key shown in the
159 config KEYBOARD_QT1050
160 tristate "Microchip AT42QT1050 Touch Sensor Chip"
164 Say Y here if you want to use Microchip AT42QT1050 QTouch
165 Sensor chip as input device.
167 To compile this driver as a module, choose M here:
168 the module will be called qt1050
170 config KEYBOARD_QT1070
171 tristate "Atmel AT42QT1070 Touch Sensor Chip"
174 Say Y here if you want to use Atmel AT42QT1070 QTouch
175 Sensor chip as input device.
177 To compile this driver as a module, choose M here:
178 the module will be called qt1070
180 config KEYBOARD_QT2160
181 tristate "Atmel AT42QT2160 Touch Sensor Chip"
184 If you say yes here you get support for Atmel AT42QT2160 Touch
185 Sensor chip as a keyboard input.
187 This driver can also be built as a module. If so, the module
188 will be called qt2160.
190 config KEYBOARD_CLPS711X
191 tristate "CLPS711X Keypad support"
192 depends on OF_GPIO && (ARCH_CLPS711X || COMPILE_TEST)
193 select INPUT_MATRIXKMAP
196 Say Y here to enable the matrix keypad on the Cirrus Logic
199 To compile this driver as a module, choose M here: the
200 module will be called clps711x-keypad.
202 config KEYBOARD_DLINK_DIR685
203 tristate "D-Link DIR-685 touchkeys support"
207 If you say yes here you get support for the D-Link DIR-685
210 To compile this driver as a module, choose M here: the
211 module will be called dlink-dir685-touchkeys.
213 config KEYBOARD_LKKBD
214 tristate "DECstation/VAXstation LK201/LK401 keyboard"
217 Say Y here if you want to use a LK201 or LK401 style serial
218 keyboard. This keyboard is also useable on PCs if you attach
219 it with the inputattach program. The connector pinout is
220 described within lkkbd.c.
222 To compile this driver as a module, choose M here: the
223 module will be called lkkbd.
225 config KEYBOARD_EP93XX
226 tristate "EP93xx Matrix Keypad support"
227 depends on ARCH_EP93XX || COMPILE_TEST
228 select INPUT_MATRIXKMAP
230 Say Y here to enable the matrix keypad on the Cirrus EP93XX.
232 To compile this driver as a module, choose M here: the
233 module will be called ep93xx_keypad.
236 tristate "GPIO Buttons"
237 depends on GPIOLIB || COMPILE_TEST
239 This driver implements support for buttons connected
240 to GPIO pins of various CPUs (and some other chips).
242 Say Y here if your device has buttons connected
243 directly to such GPIO pins. Your board-specific
244 setup logic must also provide a platform device,
245 with configuration data saying which GPIOs are used.
247 To compile this driver as a module, choose M here: the
248 module will be called gpio_keys.
250 config KEYBOARD_GPIO_POLLED
251 tristate "Polled GPIO buttons"
255 This driver implements support for buttons connected
256 to GPIO pins that are not capable of generating interrupts.
258 Say Y here if your device has buttons connected
259 directly to such GPIO pins. Your board-specific
260 setup logic must also provide a platform device,
261 with configuration data saying which GPIOs are used.
263 To compile this driver as a module, choose M here: the
264 module will be called gpio_keys_polled.
266 config KEYBOARD_TCA6416
267 tristate "TCA6416/TCA6408A Keypad Support"
270 This driver implements basic keypad functionality
271 for keys connected through TCA6416/TCA6408A IO expanders.
273 Say Y here if your device has keys connected to
274 TCA6416/TCA6408A IO expander. Your board-specific setup logic
275 must also provide pin-mask details(of which TCA6416 pins
276 are used for keypad).
278 If enabled the entire TCA6416 device will be managed through
281 To compile this driver as a module, choose M here: the
282 module will be called tca6416_keypad.
284 config KEYBOARD_TCA8418
285 tristate "TCA8418 Keypad Support"
287 select INPUT_MATRIXKMAP
289 This driver implements basic keypad functionality
290 for keys connected through TCA8418 keypad decoder.
292 Say Y here if your device has keys connected to
293 TCA8418 keypad decoder.
295 If enabled the complete TCA8418 device will be managed through
298 To compile this driver as a module, choose M here: the
299 module will be called tca8418_keypad.
301 config KEYBOARD_MATRIX
302 tristate "GPIO driven matrix keypad support"
303 depends on GPIOLIB || COMPILE_TEST
304 select INPUT_MATRIXKMAP
306 Enable support for GPIO driven matrix keypad.
308 To compile this driver as a module, choose M here: the
309 module will be called matrix_keypad.
311 config KEYBOARD_HIL_OLD
312 tristate "HP HIL keyboard support (simple driver)"
313 depends on GSC || HP300
316 The "Human Interface Loop" is a older, 8-channel USB-like
317 controller used in several Hewlett Packard models. This driver
318 was adapted from the one written for m68k/hp300, and implements
319 support for a keyboard attached to the HIL port, but not for
320 any other types of HIL input devices like mice or tablets.
321 However, it has been thoroughly tested and is stable.
323 If you want full HIL support including support for multiple
324 keyboards, mice, and tablets, you have to enable the
325 "HP System Device Controller i8042 Support" in the input/serio
329 tristate "HP HIL keyboard/pointer support"
330 depends on GSC || HP300
336 The "Human Interface Loop" is a older, 8-channel USB-like
337 controller used in several Hewlett Packard models.
338 This driver implements support for HIL-keyboards and pointing
339 devices (mice, tablets, touchscreens) attached
340 to your machine, so normally you should say Y here.
342 config KEYBOARD_HP6XX
343 tristate "HP Jornada 6xx keyboard"
347 Say Y here if you have a HP Jornada 620/660/680/690 and want to
348 support the built-in keyboard.
350 To compile this driver as a module, choose M here: the
351 module will be called jornada680_kbd.
353 config KEYBOARD_HP7XX
354 tristate "HP Jornada 7xx keyboard"
355 depends on SA1100_JORNADA720_SSP && SA1100_SSP
357 Say Y here if you have a HP Jornada 710/720/728 and want to
358 support the built-in keyboard.
360 To compile this driver as a module, choose M here: the
361 module will be called jornada720_kbd.
363 config KEYBOARD_LM8323
364 tristate "LM8323 keypad chip"
366 depends on LEDS_CLASS
368 If you say yes here you get support for the National Semiconductor
369 LM8323 keypad controller.
371 To compile this driver as a module, choose M here: the
372 module will be called lm8323.
374 config KEYBOARD_LM8333
375 tristate "LM8333 keypad chip"
377 select INPUT_MATRIXKMAP
379 If you say yes here you get support for the National Semiconductor
380 LM8333 keypad controller.
382 To compile this driver as a module, choose M here: the
383 module will be called lm8333.
385 config KEYBOARD_LOCOMO
386 tristate "LoCoMo Keyboard Support"
387 depends on SHARP_LOCOMO
389 Say Y here if you are running Linux on a Sharp Zaurus Collie or Poodle based PDA
391 To compile this driver as a module, choose M here: the
392 module will be called locomokbd.
394 config KEYBOARD_LPC32XX
395 tristate "LPC32XX matrix key scanner support"
396 depends on ARCH_LPC32XX && OF
397 select INPUT_MATRIXKMAP
399 Say Y here if you want to use NXP LPC32XX SoC key scanner interface,
400 connected to a key matrix.
402 To compile this driver as a module, choose M here: the
403 module will be called lpc32xx-keys.
405 config KEYBOARD_MAPLE
406 tristate "Maple bus keyboard"
407 depends on SH_DREAMCAST && MAPLE
409 Say Y here if you have a Dreamcast console running Linux and have
410 a keyboard attached to its Maple bus.
412 To compile this driver as a module, choose M here: the
413 module will be called maple_keyb.
415 config KEYBOARD_MAX7359
416 tristate "Maxim MAX7359 Key Switch Controller"
417 select INPUT_MATRIXKMAP
420 If you say yes here you get support for the Maxim MAX7359 Key
421 Switch Controller chip. This providers microprocessors with
422 management of up to 64 key switches
424 To compile this driver as a module, choose M here: the
425 module will be called max7359_keypad.
428 tristate "MELFAS MCS Touchkey"
431 Say Y here if you have the MELFAS MCS5000/5080 touchkey controller
436 To compile this driver as a module, choose M here: the
437 module will be called mcs_touchkey.
439 config KEYBOARD_MPR121
440 tristate "Freescale MPR121 Touchkey"
443 Say Y here if you have Freescale MPR121 touchkey controller
448 To compile this driver as a module, choose M here: the
449 module will be called mpr121_touchkey.
451 config KEYBOARD_SNVS_PWRKEY
452 tristate "IMX SNVS Power Key Driver"
453 depends on ARCH_MXC || COMPILE_TEST
456 This is the snvs powerkey driver for the Freescale i.MX application
457 processors that are newer than i.MX6 SX.
459 To compile this driver as a module, choose M here; the
460 module will be called snvs_pwrkey.
463 tristate "IMX keypad support"
465 select INPUT_MATRIXKMAP
467 Enable support for IMX keypad port.
469 To compile this driver as a module, choose M here: the
470 module will be called imx_keypad.
472 config KEYBOARD_NEWTON
473 tristate "Newton keyboard"
476 Say Y here if you have a Newton keyboard on a serial port.
478 To compile this driver as a module, choose M here: the
479 module will be called newtonkbd.
481 config KEYBOARD_NOMADIK
482 tristate "ST-Ericsson Nomadik SKE keyboard"
483 depends on (ARCH_NOMADIK || ARCH_U8500)
484 select INPUT_MATRIXKMAP
486 Say Y here if you want to use a keypad provided on the SKE controller
487 used on the Ux500 and Nomadik platforms
489 To compile this driver as a module, choose M here: the
490 module will be called nmk-ske-keypad.
492 config KEYBOARD_NSPIRE
493 tristate "TI-NSPIRE built-in keyboard"
494 depends on ARCH_NSPIRE && OF
495 select INPUT_MATRIXKMAP
497 Say Y here if you want to use the built-in keypad on TI-NSPIRE.
499 To compile this driver as a module, choose M here: the
500 module will be called nspire-keypad.
502 config KEYBOARD_TEGRA
503 tristate "NVIDIA Tegra internal matrix keyboard controller support"
504 depends on ARCH_TEGRA && OF
505 select INPUT_MATRIXKMAP
507 Say Y here if you want to use a matrix keyboard connected directly
508 to the internal keyboard controller on Tegra SoCs.
510 To compile this driver as a module, choose M here: the
511 module will be called tegra-kbc.
513 config KEYBOARD_OPENCORES
514 tristate "OpenCores Keyboard Controller"
517 Say Y here if you want to use the OpenCores Keyboard Controller
518 http://www.opencores.org/project,keyboardcontroller
520 To compile this driver as a module, choose M here; the
521 module will be called opencores-kbd.
523 config KEYBOARD_PXA27x
524 tristate "PXA27x/PXA3xx keypad support"
525 depends on PXA27x || PXA3xx || ARCH_MMP
526 select INPUT_MATRIXKMAP
528 Enable support for PXA27x/PXA3xx keypad controller.
530 To compile this driver as a module, choose M here: the
531 module will be called pxa27x_keypad.
533 config KEYBOARD_PXA930_ROTARY
534 tristate "PXA930/PXA935 Enhanced Rotary Controller Support"
535 depends on CPU_PXA930 || CPU_PXA935
537 Enable support for PXA930/PXA935 Enhanced Rotary Controller.
539 To compile this driver as a module, choose M here: the
540 module will be called pxa930_rotary.
542 config KEYBOARD_PMIC8XXX
543 tristate "Qualcomm PMIC8XXX keypad support"
544 depends on MFD_PM8XXX
545 select INPUT_MATRIXKMAP
547 Say Y here if you want to enable the driver for the PMIC8XXX
548 keypad provided as a reference design from Qualcomm. This is intended
549 to support upto 18x8 matrix based keypad design.
551 To compile this driver as a module, choose M here: the module will
552 be called pmic8xxx-keypad.
554 config KEYBOARD_SAMSUNG
555 tristate "Samsung keypad support"
557 select INPUT_MATRIXKMAP
559 Say Y here if you want to use the keypad on your Samsung mobile
562 To compile this driver as a module, choose M here: the
563 module will be called samsung-keypad.
565 config KEYBOARD_GOLDFISH_EVENTS
566 depends on GOLDFISH || COMPILE_TEST
567 tristate "Generic Input Event device for Goldfish"
569 Say Y here to get an input event device for the Goldfish virtual
572 To compile this driver as a module, choose M here: the
573 module will be called goldfish-events.
575 config KEYBOARD_STOWAWAY
576 tristate "Stowaway keyboard"
579 Say Y here if you have a Stowaway keyboard on a serial port.
580 Stowaway compatible keyboards like Dicota Input-PDA keyboard
581 are also supported by this driver.
583 To compile this driver as a module, choose M here: the
584 module will be called stowaway.
586 config KEYBOARD_ST_KEYSCAN
587 tristate "STMicroelectronics keyscan support"
588 depends on ARCH_STI || COMPILE_TEST
589 select INPUT_MATRIXKMAP
591 Say Y here if you want to use a keypad attached to the keyscan block
592 on some STMicroelectronics SoC devices.
594 To compile this driver as a module, choose M here: the
595 module will be called st-keyscan.
597 config KEYBOARD_SUNKBD
598 tristate "Sun Type 4 and Type 5 keyboard"
601 Say Y here if you want to use a Sun Type 4 or Type 5 keyboard,
602 connected either to the Sun keyboard connector or to an serial
603 (RS-232) port via a simple adapter.
605 To compile this driver as a module, choose M here: the
606 module will be called sunkbd.
608 config KEYBOARD_SH_KEYSC
609 tristate "SuperH KEYSC keypad support"
610 depends on ARCH_SHMOBILE || COMPILE_TEST
612 Say Y here if you want to use a keypad attached to the KEYSC block
613 on SuperH processors such as sh7722 and sh7343.
615 To compile this driver as a module, choose M here: the
616 module will be called sh_keysc.
618 config KEYBOARD_STMPE
619 tristate "STMPE keypad support"
622 select INPUT_MATRIXKMAP
624 Say Y here if you want to use the keypad controller on STMPE I/O
627 To compile this driver as a module, choose M here: the module will be
630 config KEYBOARD_SUN4I_LRADC
631 tristate "Allwinner sun4i low res adc attached tablet keys support"
632 depends on ARCH_SUNXI
634 This selects support for the Allwinner low res adc attached tablet
635 keys found on Allwinner sunxi SoCs.
637 To compile this driver as a module, choose M here: the
638 module will be called sun4i-lradc-keys.
640 config KEYBOARD_DAVINCI
641 tristate "TI DaVinci Key Scan"
642 depends on ARCH_DAVINCI_DM365
644 Say Y to enable keypad module support for the TI DaVinci
647 To compile this driver as a module, choose M here: the
648 module will be called davinci_keyscan.
650 config KEYBOARD_IPAQ_MICRO
651 tristate "Buttons on Micro SoC (iPaq h3100,h3600,h3700)"
652 depends on MFD_IPAQ_MICRO
654 Say Y to enable support for the buttons attached to
655 Micro peripheral controller on iPAQ h3100/h3600/h3700
657 To compile this driver as a module, choose M here: the
658 module will be called ipaq-micro-keys.
661 tristate "TI OMAP keypad support"
662 depends on ARCH_OMAP1
663 select INPUT_MATRIXKMAP
665 Say Y here if you want to use the OMAP keypad.
667 To compile this driver as a module, choose M here: the
668 module will be called omap-keypad.
670 config KEYBOARD_OMAP4
671 tristate "TI OMAP4+ keypad support"
672 depends on OF || ARCH_OMAP2PLUS
673 select INPUT_MATRIXKMAP
675 Say Y here if you want to use the OMAP4+ keypad.
677 To compile this driver as a module, choose M here: the
678 module will be called omap4-keypad.
680 config KEYBOARD_SPEAR
681 tristate "ST SPEAR keyboard support"
682 depends on PLAT_SPEAR
683 select INPUT_MATRIXKMAP
685 Say Y here if you want to use the SPEAR keyboard.
687 To compile this driver as a module, choose M here: the
688 module will be called spear-keboard.
690 config KEYBOARD_TC3589X
691 tristate "TC3589X Keypad support"
692 depends on MFD_TC3589X
693 select INPUT_MATRIXKMAP
695 Say Y here if you want to use the keypad controller on
696 TC35892/3 I/O expander.
698 To compile this driver as a module, choose M here: the
699 module will be called tc3589x-keypad.
701 config KEYBOARD_TM2_TOUCHKEY
702 tristate "TM2 touchkey support"
704 depends on LEDS_CLASS
706 Say Y here to enable device driver for tm2-touchkey with
707 LED control for the Exynos5433 TM2 board.
709 To compile this driver as a module, choose M here.
710 module will be called tm2-touchkey.
712 config KEYBOARD_TWL4030
713 tristate "TI TWL4030/TWL5030/TPS659x0 keypad support"
714 depends on TWL4030_CORE
715 select INPUT_MATRIXKMAP
717 Say Y here if your board use the keypad controller on
718 TWL4030 family chips. It's safe to say enable this
719 even on boards that don't use the keypad controller.
721 To compile this driver as a module, choose M here: the
722 module will be called twl4030_keypad.
724 config KEYBOARD_XTKBD
725 tristate "XT keyboard"
728 Say Y here if you want to use the old IBM PC/XT keyboard (or
729 compatible) on your system. This is only possible with a
730 parallel port keyboard adapter, you cannot connect it to the
731 keyboard port on a PC that runs Linux.
733 To compile this driver as a module, choose M here: the
734 module will be called xtkbd.
736 config KEYBOARD_CROS_EC
737 tristate "ChromeOS EC keyboard"
738 select INPUT_MATRIXKMAP
741 Say Y here to enable the matrix keyboard used by ChromeOS devices
742 and implemented on the ChromeOS EC. You must enable one bus option
743 (CROS_EC_I2C or CROS_EC_SPI) to use this.
745 To compile this driver as a module, choose M here: the
746 module will be called cros_ec_keyb.
748 config KEYBOARD_CAP11XX
749 tristate "Microchip CAP11XX based touch sensors"
753 Say Y here to enable the CAP11XX touch sensor driver.
755 To compile this driver as a module, choose M here: the
756 module will be called cap11xx.
759 tristate "Broadcom keypad driver"
760 depends on OF && HAVE_CLK
761 select INPUT_MATRIXKMAP
762 default ARCH_BCM_CYGNUS
764 Say Y here if you want to use Broadcom keypad.
766 To compile this driver as a module, choose M here: the
767 module will be called bcm-keypad.
769 config KEYBOARD_MTK_PMIC
770 tristate "MediaTek PMIC keys support"
771 depends on MFD_MT6397
773 Say Y here if you want to use the pmic keys (powerkey/homekey).
775 To compile this driver as a module, choose M here: the
776 module will be called pmic-keys.