2 # Input core configuration
4 menuconfig INPUT_KEYBOARD
8 Say Y here, and a list of supported keyboards will be displayed.
9 This option doesn't affect the kernel.
16 tristate "ADC Ladder Buttons"
20 This driver implements support for buttons connected
21 to an ADC using a resistor ladder.
23 Say Y here if your device has such buttons connected to an ADC. Your
24 board-specific setup logic must also provide a configuration data
25 for mapping voltages to buttons.
27 To compile this driver as a module, choose M here: the
28 module will be called adc_keys.
30 config KEYBOARD_ADP5520
31 tristate "Keypad Support for ADP5520 PMIC"
32 depends on PMIC_ADP5520
34 This option enables support for the keypad scan matrix
35 on Analog Devices ADP5520 PMICs.
37 To compile this driver as a module, choose M here: the module will
38 be called adp5520-keys.
40 config KEYBOARD_ADP5588
41 tristate "ADP5588/87 I2C QWERTY Keypad and IO Expander"
44 Say Y here if you want to use a ADP5588/87 attached to your
47 To compile this driver as a module, choose M here: the
48 module will be called adp5588-keys.
50 config KEYBOARD_ADP5589
51 tristate "ADP5585/ADP5589 I2C QWERTY Keypad and IO Expander"
54 Say Y here if you want to use a ADP5585/ADP5589 attached to your
57 To compile this driver as a module, choose M here: the
58 module will be called adp5589-keys.
61 tristate "Amiga keyboard"
64 Say Y here if you are running Linux on any AMIGA and have a keyboard
67 To compile this driver as a module, choose M here: the
68 module will be called amikbd.
74 tristate "Atari keyboard"
78 Say Y here if you are running Linux on any Atari and have a keyboard
81 To compile this driver as a module, choose M here: the
82 module will be called atakbd.
85 tristate "AT keyboard"
89 select SERIO_I8042 if ARCH_MIGHT_HAVE_PC_SERIO
90 select SERIO_GSCPS2 if GSC
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
94 or other). This also works for AT and PS/2 keyboards connected over a
95 PS/2 to serial converter.
99 To compile this driver as a module, choose M here: the
100 module will be called atkbd.
102 config KEYBOARD_ATKBD_HP_KEYCODES
103 bool "Use HP keyboard scancodes"
104 depends on PARISC && KEYBOARD_ATKBD
107 Say Y here if you have a PA-RISC machine and want to use an AT or
108 PS/2 keyboard, and your keyboard uses keycodes that are specific to
111 Say N if you use a standard keyboard.
113 config KEYBOARD_ATKBD_RDI_KEYCODES
114 bool "Use PrecisionBook keyboard scancodes"
115 depends on KEYBOARD_ATKBD_HP_KEYCODES
118 If you have an RDI PrecisionBook, say Y here if you want to use its
119 built-in keyboard (as opposed to an external keyboard).
121 The PrecisionBook has five keys that conflict with those used by most
122 AT and PS/2 keyboards. These are as follows:
124 PrecisionBook Standard AT or PS/2
130 Left 102nd key (the key to the right of Left Shift)
132 If you say N here, and use the PrecisionBook keyboard, then each key
133 in the left-hand column will be interpreted as the corresponding key
134 in the right-hand column.
136 If you say Y here, and use an external keyboard, then each key in the
137 right-hand column will be interpreted as the key shown in the
140 config KEYBOARD_QT1070
141 tristate "Atmel AT42QT1070 Touch Sensor Chip"
144 Say Y here if you want to use Atmel AT42QT1070 QTouch
145 Sensor chip as input device.
147 To compile this driver as a module, choose M here:
148 the module will be called qt1070
150 config KEYBOARD_QT2160
151 tristate "Atmel AT42QT2160 Touch Sensor Chip"
154 If you say yes here you get support for Atmel AT42QT2160 Touch
155 Sensor chip as a keyboard input.
157 This driver can also be built as a module. If so, the module
158 will be called qt2160.
161 tristate "Blackfin BF54x keypad support"
162 depends on (BF54x && !BF544)
164 Say Y here if you want to use the BF54x keypad.
166 To compile this driver as a module, choose M here: the
167 module will be called bf54x-keys.
169 config KEYBOARD_CLPS711X
170 tristate "CLPS711X Keypad support"
171 depends on OF_GPIO && (ARCH_CLPS711X || COMPILE_TEST)
172 select INPUT_MATRIXKMAP
175 Say Y here to enable the matrix keypad on the Cirrus Logic
178 To compile this driver as a module, choose M here: the
179 module will be called clps711x-keypad.
181 config KEYBOARD_LKKBD
182 tristate "DECstation/VAXstation LK201/LK401 keyboard"
185 Say Y here if you want to use a LK201 or LK401 style serial
186 keyboard. This keyboard is also useable on PCs if you attach
187 it with the inputattach program. The connector pinout is
188 described within lkkbd.c.
190 To compile this driver as a module, choose M here: the
191 module will be called lkkbd.
193 config KEYBOARD_EP93XX
194 tristate "EP93xx Matrix Keypad support"
195 depends on ARCH_EP93XX
196 select INPUT_MATRIXKMAP
198 Say Y here to enable the matrix keypad on the Cirrus EP93XX.
200 To compile this driver as a module, choose M here: the
201 module will be called ep93xx_keypad.
204 tristate "GPIO Buttons"
205 depends on GPIOLIB || COMPILE_TEST
207 This driver implements support for buttons connected
208 to GPIO pins of various CPUs (and some other chips).
210 Say Y here if your device has buttons connected
211 directly to such GPIO pins. Your board-specific
212 setup logic must also provide a platform device,
213 with configuration data saying which GPIOs are used.
215 To compile this driver as a module, choose M here: the
216 module will be called gpio_keys.
218 config KEYBOARD_GPIO_POLLED
219 tristate "Polled GPIO buttons"
223 This driver implements support for buttons connected
224 to GPIO pins that are not capable of generating interrupts.
226 Say Y here if your device has buttons connected
227 directly to such GPIO pins. Your board-specific
228 setup logic must also provide a platform device,
229 with configuration data saying which GPIOs are used.
231 To compile this driver as a module, choose M here: the
232 module will be called gpio_keys_polled.
234 config KEYBOARD_TCA6416
235 tristate "TCA6416/TCA6408A Keypad Support"
238 This driver implements basic keypad functionality
239 for keys connected through TCA6416/TCA6408A IO expanders.
241 Say Y here if your device has keys connected to
242 TCA6416/TCA6408A IO expander. Your board-specific setup logic
243 must also provide pin-mask details(of which TCA6416 pins
244 are used for keypad).
246 If enabled the entire TCA6416 device will be managed through
249 To compile this driver as a module, choose M here: the
250 module will be called tca6416_keypad.
252 config KEYBOARD_TCA8418
253 tristate "TCA8418 Keypad Support"
255 select INPUT_MATRIXKMAP
257 This driver implements basic keypad functionality
258 for keys connected through TCA8418 keypad decoder.
260 Say Y here if your device has keys connected to
261 TCA8418 keypad decoder.
263 If enabled the complete TCA8418 device will be managed through
266 To compile this driver as a module, choose M here: the
267 module will be called tca8418_keypad.
269 config KEYBOARD_MATRIX
270 tristate "GPIO driven matrix keypad support"
271 depends on GPIOLIB || COMPILE_TEST
272 select INPUT_MATRIXKMAP
274 Enable support for GPIO driven matrix keypad.
276 To compile this driver as a module, choose M here: the
277 module will be called matrix_keypad.
279 config KEYBOARD_HIL_OLD
280 tristate "HP HIL keyboard support (simple driver)"
281 depends on GSC || HP300
284 The "Human Interface Loop" is a older, 8-channel USB-like
285 controller used in several Hewlett Packard models. This driver
286 was adapted from the one written for m68k/hp300, and implements
287 support for a keyboard attached to the HIL port, but not for
288 any other types of HIL input devices like mice or tablets.
289 However, it has been thoroughly tested and is stable.
291 If you want full HIL support including support for multiple
292 keyboards, mice, and tablets, you have to enable the
293 "HP System Device Controller i8042 Support" in the input/serio
297 tristate "HP HIL keyboard/pointer support"
298 depends on GSC || HP300
304 The "Human Interface Loop" is a older, 8-channel USB-like
305 controller used in several Hewlett Packard models.
306 This driver implements support for HIL-keyboards and pointing
307 devices (mice, tablets, touchscreens) attached
308 to your machine, so normally you should say Y here.
310 config KEYBOARD_HP6XX
311 tristate "HP Jornada 6xx keyboard"
315 Say Y here if you have a HP Jornada 620/660/680/690 and want to
316 support the built-in keyboard.
318 To compile this driver as a module, choose M here: the
319 module will be called jornada680_kbd.
321 config KEYBOARD_HP7XX
322 tristate "HP Jornada 7xx keyboard"
323 depends on SA1100_JORNADA720_SSP && SA1100_SSP
325 Say Y here if you have a HP Jornada 710/720/728 and want to
326 support the built-in keyboard.
328 To compile this driver as a module, choose M here: the
329 module will be called jornada720_kbd.
331 config KEYBOARD_LM8323
332 tristate "LM8323 keypad chip"
334 depends on LEDS_CLASS
336 If you say yes here you get support for the National Semiconductor
337 LM8323 keypad controller.
339 To compile this driver as a module, choose M here: the
340 module will be called lm8323.
342 config KEYBOARD_LM8333
343 tristate "LM8333 keypad chip"
345 select INPUT_MATRIXKMAP
347 If you say yes here you get support for the National Semiconductor
348 LM8333 keypad controller.
350 To compile this driver as a module, choose M here: the
351 module will be called lm8333.
353 config KEYBOARD_LOCOMO
354 tristate "LoCoMo Keyboard Support"
355 depends on SHARP_LOCOMO
357 Say Y here if you are running Linux on a Sharp Zaurus Collie or Poodle based PDA
359 To compile this driver as a module, choose M here: the
360 module will be called locomokbd.
362 config KEYBOARD_LPC32XX
363 tristate "LPC32XX matrix key scanner support"
364 depends on ARCH_LPC32XX && OF
365 select INPUT_MATRIXKMAP
367 Say Y here if you want to use NXP LPC32XX SoC key scanner interface,
368 connected to a key matrix.
370 To compile this driver as a module, choose M here: the
371 module will be called lpc32xx-keys.
373 config KEYBOARD_MAPLE
374 tristate "Maple bus keyboard"
375 depends on SH_DREAMCAST && MAPLE
377 Say Y here if you have a Dreamcast console running Linux and have
378 a keyboard attached to its Maple bus.
380 To compile this driver as a module, choose M here: the
381 module will be called maple_keyb.
383 config KEYBOARD_MAX7359
384 tristate "Maxim MAX7359 Key Switch Controller"
385 select INPUT_MATRIXKMAP
388 If you say yes here you get support for the Maxim MAX7359 Key
389 Switch Controller chip. This providers microprocessors with
390 management of up to 64 key switches
392 To compile this driver as a module, choose M here: the
393 module will be called max7359_keypad.
396 tristate "MELFAS MCS Touchkey"
399 Say Y here if you have the MELFAS MCS5000/5080 touchkey controller
404 To compile this driver as a module, choose M here: the
405 module will be called mcs_touchkey.
407 config KEYBOARD_MPR121
408 tristate "Freescale MPR121 Touchkey"
411 Say Y here if you have Freescale MPR121 touchkey controller
416 To compile this driver as a module, choose M here: the
417 module will be called mpr121_touchkey.
419 config KEYBOARD_SNVS_PWRKEY
420 tristate "IMX SNVS Power Key Driver"
421 depends on SOC_IMX6SX
424 This is the snvs powerkey driver for the Freescale i.MX application
425 processors that are newer than i.MX6 SX.
427 To compile this driver as a module, choose M here; the
428 module will be called snvs_pwrkey.
431 tristate "IMX keypad support"
433 select INPUT_MATRIXKMAP
435 Enable support for IMX keypad port.
437 To compile this driver as a module, choose M here: the
438 module will be called imx_keypad.
440 config KEYBOARD_NEWTON
441 tristate "Newton keyboard"
444 Say Y here if you have a Newton keyboard on a serial port.
446 To compile this driver as a module, choose M here: the
447 module will be called newtonkbd.
449 config KEYBOARD_NOMADIK
450 tristate "ST-Ericsson Nomadik SKE keyboard"
451 depends on (ARCH_NOMADIK || ARCH_U8500)
452 select INPUT_MATRIXKMAP
454 Say Y here if you want to use a keypad provided on the SKE controller
455 used on the Ux500 and Nomadik platforms
457 To compile this driver as a module, choose M here: the
458 module will be called nmk-ske-keypad.
460 config KEYBOARD_NSPIRE
461 tristate "TI-NSPIRE built-in keyboard"
462 depends on ARCH_NSPIRE && OF
463 select INPUT_MATRIXKMAP
465 Say Y here if you want to use the built-in keypad on TI-NSPIRE.
467 To compile this driver as a module, choose M here: the
468 module will be called nspire-keypad.
470 config KEYBOARD_TEGRA
471 tristate "NVIDIA Tegra internal matrix keyboard controller support"
472 depends on ARCH_TEGRA && OF
473 select INPUT_MATRIXKMAP
475 Say Y here if you want to use a matrix keyboard connected directly
476 to the internal keyboard controller on Tegra SoCs.
478 To compile this driver as a module, choose M here: the
479 module will be called tegra-kbc.
481 config KEYBOARD_OPENCORES
482 tristate "OpenCores Keyboard Controller"
485 Say Y here if you want to use the OpenCores Keyboard Controller
486 http://www.opencores.org/project,keyboardcontroller
488 To compile this driver as a module, choose M here; the
489 module will be called opencores-kbd.
491 config KEYBOARD_PXA27x
492 tristate "PXA27x/PXA3xx keypad support"
493 depends on PXA27x || PXA3xx || ARCH_MMP
494 select INPUT_MATRIXKMAP
496 Enable support for PXA27x/PXA3xx keypad controller.
498 To compile this driver as a module, choose M here: the
499 module will be called pxa27x_keypad.
501 config KEYBOARD_PXA930_ROTARY
502 tristate "PXA930/PXA935 Enhanced Rotary Controller Support"
503 depends on CPU_PXA930 || CPU_PXA935
505 Enable support for PXA930/PXA935 Enhanced Rotary Controller.
507 To compile this driver as a module, choose M here: the
508 module will be called pxa930_rotary.
510 config KEYBOARD_PMIC8XXX
511 tristate "Qualcomm PMIC8XXX keypad support"
512 depends on MFD_PM8XXX
513 select INPUT_MATRIXKMAP
515 Say Y here if you want to enable the driver for the PMIC8XXX
516 keypad provided as a reference design from Qualcomm. This is intended
517 to support upto 18x8 matrix based keypad design.
519 To compile this driver as a module, choose M here: the module will
520 be called pmic8xxx-keypad.
522 config KEYBOARD_SAMSUNG
523 tristate "Samsung keypad support"
525 select INPUT_MATRIXKMAP
527 Say Y here if you want to use the keypad on your Samsung mobile
530 To compile this driver as a module, choose M here: the
531 module will be called samsung-keypad.
533 config KEYBOARD_GOLDFISH_EVENTS
534 depends on GOLDFISH || COMPILE_TEST
535 tristate "Generic Input Event device for Goldfish"
537 Say Y here to get an input event device for the Goldfish virtual
540 To compile this driver as a module, choose M here: the
541 module will be called goldfish-events.
543 config KEYBOARD_STOWAWAY
544 tristate "Stowaway keyboard"
547 Say Y here if you have a Stowaway keyboard on a serial port.
548 Stowaway compatible keyboards like Dicota Input-PDA keyboard
549 are also supported by this driver.
551 To compile this driver as a module, choose M here: the
552 module will be called stowaway.
554 config KEYBOARD_ST_KEYSCAN
555 tristate "STMicroelectronics keyscan support"
556 depends on ARCH_STI || COMPILE_TEST
557 select INPUT_MATRIXKMAP
559 Say Y here if you want to use a keypad attached to the keyscan block
560 on some STMicroelectronics SoC devices.
562 To compile this driver as a module, choose M here: the
563 module will be called st-keyscan.
565 config KEYBOARD_SUNKBD
566 tristate "Sun Type 4 and Type 5 keyboard"
569 Say Y here if you want to use a Sun Type 4 or Type 5 keyboard,
570 connected either to the Sun keyboard connector or to an serial
571 (RS-232) port via a simple adapter.
573 To compile this driver as a module, choose M here: the
574 module will be called sunkbd.
576 config KEYBOARD_SH_KEYSC
577 tristate "SuperH KEYSC keypad support"
578 depends on ARCH_SHMOBILE || COMPILE_TEST
580 Say Y here if you want to use a keypad attached to the KEYSC block
581 on SuperH processors such as sh7722 and sh7343.
583 To compile this driver as a module, choose M here: the
584 module will be called sh_keysc.
586 config KEYBOARD_STMPE
587 tristate "STMPE keypad support"
590 select INPUT_MATRIXKMAP
592 Say Y here if you want to use the keypad controller on STMPE I/O
595 To compile this driver as a module, choose M here: the module will be
598 config KEYBOARD_SUN4I_LRADC
599 tristate "Allwinner sun4i low res adc attached tablet keys support"
600 depends on ARCH_SUNXI
602 This selects support for the Allwinner low res adc attached tablet
603 keys found on Allwinner sunxi SoCs.
605 To compile this driver as a module, choose M here: the
606 module will be called sun4i-lradc-keys.
608 config KEYBOARD_DAVINCI
609 tristate "TI DaVinci Key Scan"
610 depends on ARCH_DAVINCI_DM365
612 Say Y to enable keypad module support for the TI DaVinci
615 To compile this driver as a module, choose M here: the
616 module will be called davinci_keyscan.
618 config KEYBOARD_IPAQ_MICRO
619 tristate "Buttons on Micro SoC (iPaq h3100,h3600,h3700)"
620 depends on MFD_IPAQ_MICRO
622 Say Y to enable support for the buttons attached to
623 Micro peripheral controller on iPAQ h3100/h3600/h3700
625 To compile this driver as a module, choose M here: the
626 module will be called ipaq-micro-keys.
629 tristate "TI OMAP keypad support"
630 depends on ARCH_OMAP1
631 select INPUT_MATRIXKMAP
633 Say Y here if you want to use the OMAP keypad.
635 To compile this driver as a module, choose M here: the
636 module will be called omap-keypad.
638 config KEYBOARD_OMAP4
639 tristate "TI OMAP4+ keypad support"
640 depends on OF || ARCH_OMAP2PLUS
641 select INPUT_MATRIXKMAP
643 Say Y here if you want to use the OMAP4+ keypad.
645 To compile this driver as a module, choose M here: the
646 module will be called omap4-keypad.
648 config KEYBOARD_SPEAR
649 tristate "ST SPEAR keyboard support"
650 depends on PLAT_SPEAR
651 select INPUT_MATRIXKMAP
653 Say Y here if you want to use the SPEAR keyboard.
655 To compile this driver as a module, choose M here: the
656 module will be called spear-keboard.
658 config KEYBOARD_TC3589X
659 tristate "TC3589X Keypad support"
660 depends on MFD_TC3589X
661 select INPUT_MATRIXKMAP
663 Say Y here if you want to use the keypad controller on
664 TC35892/3 I/O expander.
666 To compile this driver as a module, choose M here: the
667 module will be called tc3589x-keypad.
669 config KEYBOARD_TM2_TOUCHKEY
670 tristate "TM2 touchkey support"
672 depends on LEDS_CLASS
674 Say Y here to enable device driver for tm2-touchkey with
675 LED control for the Exynos5433 TM2 board.
677 To compile this driver as a module, choose M here.
678 module will be called tm2-touchkey.
680 config KEYBOARD_TWL4030
681 tristate "TI TWL4030/TWL5030/TPS659x0 keypad support"
682 depends on TWL4030_CORE
683 select INPUT_MATRIXKMAP
685 Say Y here if your board use the keypad controller on
686 TWL4030 family chips. It's safe to say enable this
687 even on boards that don't use the keypad controller.
689 To compile this driver as a module, choose M here: the
690 module will be called twl4030_keypad.
692 config KEYBOARD_XTKBD
693 tristate "XT keyboard"
696 Say Y here if you want to use the old IBM PC/XT keyboard (or
697 compatible) on your system. This is only possible with a
698 parallel port keyboard adapter, you cannot connect it to the
699 keyboard port on a PC that runs Linux.
701 To compile this driver as a module, choose M here: the
702 module will be called xtkbd.
704 config KEYBOARD_W90P910
705 tristate "W90P910 Matrix Keypad support"
706 depends on ARCH_W90X900
707 select INPUT_MATRIXKMAP
709 Say Y here to enable the matrix keypad on evaluation board
712 To compile this driver as a module, choose M here: the
713 module will be called w90p910_keypad.
715 config KEYBOARD_CROS_EC
716 tristate "ChromeOS EC keyboard"
717 select INPUT_MATRIXKMAP
718 depends on MFD_CROS_EC
720 Say Y here to enable the matrix keyboard used by ChromeOS devices
721 and implemented on the ChromeOS EC. You must enable one bus option
722 (MFD_CROS_EC_I2C or MFD_CROS_EC_SPI) to use this.
724 To compile this driver as a module, choose M here: the
725 module will be called cros_ec_keyb.
727 config KEYBOARD_CAP11XX
728 tristate "Microchip CAP11XX based touch sensors"
732 Say Y here to enable the CAP11XX touch sensor driver.
734 To compile this driver as a module, choose M here: the
735 module will be called cap11xx.
738 tristate "Broadcom keypad driver"
739 depends on OF && HAVE_CLK
740 select INPUT_MATRIXKMAP
741 default ARCH_BCM_CYGNUS
743 Say Y here if you want to use Broadcom keypad.
745 To compile this driver as a module, choose M here: the
746 module will be called bcm-keypad.