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.
15 config KEYBOARD_ADP5520
16 tristate "Keypad Support for ADP5520 PMIC"
17 depends on PMIC_ADP5520
19 This option enables support for the keypad scan matrix
20 on Analog Devices ADP5520 PMICs.
22 To compile this driver as a module, choose M here: the module will
23 be called adp5520-keys.
25 config KEYBOARD_ADP5588
26 tristate "ADP5588/87 I2C QWERTY Keypad and IO Expander"
29 Say Y here if you want to use a ADP5588/87 attached to your
32 To compile this driver as a module, choose M here: the
33 module will be called adp5588-keys.
35 config KEYBOARD_ADP5589
36 tristate "ADP5585/ADP5589 I2C QWERTY Keypad and IO Expander"
39 Say Y here if you want to use a ADP5585/ADP5589 attached to your
42 To compile this driver as a module, choose M here: the
43 module will be called adp5589-keys.
46 tristate "Amiga keyboard"
49 Say Y here if you are running Linux on any AMIGA and have a keyboard
52 To compile this driver as a module, choose M here: the
53 module will be called amikbd.
59 tristate "Atari keyboard"
63 Say Y here if you are running Linux on any Atari and have a keyboard
66 To compile this driver as a module, choose M here: the
67 module will be called atakbd.
70 tristate "AT keyboard"
74 select SERIO_I8042 if ARCH_MIGHT_HAVE_PC_SERIO
75 select SERIO_GSCPS2 if GSC
77 Say Y here if you want to use a standard AT or PS/2 keyboard. Usually
78 you'll need this, unless you have a different type keyboard (USB, ADB
79 or other). This also works for AT and PS/2 keyboards connected over a
80 PS/2 to serial converter.
84 To compile this driver as a module, choose M here: the
85 module will be called atkbd.
87 config KEYBOARD_ATKBD_HP_KEYCODES
88 bool "Use HP keyboard scancodes"
89 depends on PARISC && KEYBOARD_ATKBD
92 Say Y here if you have a PA-RISC machine and want to use an AT or
93 PS/2 keyboard, and your keyboard uses keycodes that are specific to
96 Say N if you use a standard keyboard.
98 config KEYBOARD_ATKBD_RDI_KEYCODES
99 bool "Use PrecisionBook keyboard scancodes"
100 depends on KEYBOARD_ATKBD_HP_KEYCODES
103 If you have an RDI PrecisionBook, say Y here if you want to use its
104 built-in keyboard (as opposed to an external keyboard).
106 The PrecisionBook has five keys that conflict with those used by most
107 AT and PS/2 keyboards. These are as follows:
109 PrecisionBook Standard AT or PS/2
115 Left 102nd key (the key to the right of Left Shift)
117 If you say N here, and use the PrecisionBook keyboard, then each key
118 in the left-hand column will be interpreted as the corresponding key
119 in the right-hand column.
121 If you say Y here, and use an external keyboard, then each key in the
122 right-hand column will be interpreted as the key shown in the
125 config KEYBOARD_QT1070
126 tristate "Atmel AT42QT1070 Touch Sensor Chip"
129 Say Y here if you want to use Atmel AT42QT1070 QTouch
130 Sensor chip as input device.
132 To compile this driver as a module, choose M here:
133 the module will be called qt1070
135 config KEYBOARD_QT2160
136 tristate "Atmel AT42QT2160 Touch Sensor Chip"
139 If you say yes here you get support for Atmel AT42QT2160 Touch
140 Sensor chip as a keyboard input.
142 This driver can also be built as a module. If so, the module
143 will be called qt2160.
146 tristate "Blackfin BF54x keypad support"
147 depends on (BF54x && !BF544)
149 Say Y here if you want to use the BF54x keypad.
151 To compile this driver as a module, choose M here: the
152 module will be called bf54x-keys.
154 config KEYBOARD_CLPS711X
155 tristate "CLPS711X Keypad support"
156 depends on OF_GPIO && (ARCH_CLPS711X || COMPILE_TEST)
157 select INPUT_MATRIXKMAP
160 Say Y here to enable the matrix keypad on the Cirrus Logic
163 To compile this driver as a module, choose M here: the
164 module will be called clps711x-keypad.
166 config KEYBOARD_LKKBD
167 tristate "DECstation/VAXstation LK201/LK401 keyboard"
170 Say Y here if you want to use a LK201 or LK401 style serial
171 keyboard. This keyboard is also useable on PCs if you attach
172 it with the inputattach program. The connector pinout is
173 described within lkkbd.c.
175 To compile this driver as a module, choose M here: the
176 module will be called lkkbd.
178 config KEYBOARD_EP93XX
179 tristate "EP93xx Matrix Keypad support"
180 depends on ARCH_EP93XX
181 select INPUT_MATRIXKMAP
183 Say Y here to enable the matrix keypad on the Cirrus EP93XX.
185 To compile this driver as a module, choose M here: the
186 module will be called ep93xx_keypad.
189 tristate "GPIO Buttons"
190 depends on GPIOLIB || COMPILE_TEST
192 This driver implements support for buttons connected
193 to GPIO pins of various CPUs (and some other chips).
195 Say Y here if your device has buttons connected
196 directly to such GPIO pins. Your board-specific
197 setup logic must also provide a platform device,
198 with configuration data saying which GPIOs are used.
200 To compile this driver as a module, choose M here: the
201 module will be called gpio_keys.
203 config KEYBOARD_GPIO_POLLED
204 tristate "Polled GPIO buttons"
208 This driver implements support for buttons connected
209 to GPIO pins that are not capable of generating interrupts.
211 Say Y here if your device has buttons connected
212 directly to such GPIO pins. Your board-specific
213 setup logic must also provide a platform device,
214 with configuration data saying which GPIOs are used.
216 To compile this driver as a module, choose M here: the
217 module will be called gpio_keys_polled.
219 config KEYBOARD_TCA6416
220 tristate "TCA6416/TCA6408A Keypad Support"
223 This driver implements basic keypad functionality
224 for keys connected through TCA6416/TCA6408A IO expanders.
226 Say Y here if your device has keys connected to
227 TCA6416/TCA6408A IO expander. Your board-specific setup logic
228 must also provide pin-mask details(of which TCA6416 pins
229 are used for keypad).
231 If enabled the entire TCA6416 device will be managed through
234 To compile this driver as a module, choose M here: the
235 module will be called tca6416_keypad.
237 config KEYBOARD_TCA8418
238 tristate "TCA8418 Keypad Support"
240 select INPUT_MATRIXKMAP
242 This driver implements basic keypad functionality
243 for keys connected through TCA8418 keypad decoder.
245 Say Y here if your device has keys connected to
246 TCA8418 keypad decoder.
248 If enabled the complete TCA8418 device will be managed through
251 To compile this driver as a module, choose M here: the
252 module will be called tca8418_keypad.
254 config KEYBOARD_MATRIX
255 tristate "GPIO driven matrix keypad support"
256 depends on GPIOLIB || COMPILE_TEST
257 select INPUT_MATRIXKMAP
259 Enable support for GPIO driven matrix keypad.
261 To compile this driver as a module, choose M here: the
262 module will be called matrix_keypad.
264 config KEYBOARD_HIL_OLD
265 tristate "HP HIL keyboard support (simple driver)"
266 depends on GSC || HP300
269 The "Human Interface Loop" is a older, 8-channel USB-like
270 controller used in several Hewlett Packard models. This driver
271 was adapted from the one written for m68k/hp300, and implements
272 support for a keyboard attached to the HIL port, but not for
273 any other types of HIL input devices like mice or tablets.
274 However, it has been thoroughly tested and is stable.
276 If you want full HIL support including support for multiple
277 keyboards, mice, and tablets, you have to enable the
278 "HP System Device Controller i8042 Support" in the input/serio
282 tristate "HP HIL keyboard/pointer support"
283 depends on GSC || HP300
289 The "Human Interface Loop" is a older, 8-channel USB-like
290 controller used in several Hewlett Packard models.
291 This driver implements support for HIL-keyboards and pointing
292 devices (mice, tablets, touchscreens) attached
293 to your machine, so normally you should say Y here.
295 config KEYBOARD_HP6XX
296 tristate "HP Jornada 6xx keyboard"
300 Say Y here if you have a HP Jornada 620/660/680/690 and want to
301 support the built-in keyboard.
303 To compile this driver as a module, choose M here: the
304 module will be called jornada680_kbd.
306 config KEYBOARD_HP7XX
307 tristate "HP Jornada 7xx keyboard"
308 depends on SA1100_JORNADA720_SSP && SA1100_SSP
310 Say Y here if you have a HP Jornada 710/720/728 and want to
311 support the built-in keyboard.
313 To compile this driver as a module, choose M here: the
314 module will be called jornada720_kbd.
316 config KEYBOARD_LM8323
317 tristate "LM8323 keypad chip"
319 depends on LEDS_CLASS
321 If you say yes here you get support for the National Semiconductor
322 LM8323 keypad controller.
324 To compile this driver as a module, choose M here: the
325 module will be called lm8323.
327 config KEYBOARD_LM8333
328 tristate "LM8333 keypad chip"
330 select INPUT_MATRIXKMAP
332 If you say yes here you get support for the National Semiconductor
333 LM8333 keypad controller.
335 To compile this driver as a module, choose M here: the
336 module will be called lm8333.
338 config KEYBOARD_LOCOMO
339 tristate "LoCoMo Keyboard Support"
340 depends on SHARP_LOCOMO
342 Say Y here if you are running Linux on a Sharp Zaurus Collie or Poodle based PDA
344 To compile this driver as a module, choose M here: the
345 module will be called locomokbd.
347 config KEYBOARD_LPC32XX
348 tristate "LPC32XX matrix key scanner support"
349 depends on ARCH_LPC32XX && OF
350 select INPUT_MATRIXKMAP
352 Say Y here if you want to use NXP LPC32XX SoC key scanner interface,
353 connected to a key matrix.
355 To compile this driver as a module, choose M here: the
356 module will be called lpc32xx-keys.
358 config KEYBOARD_MAPLE
359 tristate "Maple bus keyboard"
360 depends on SH_DREAMCAST && MAPLE
362 Say Y here if you have a Dreamcast console running Linux and have
363 a keyboard attached to its Maple bus.
365 To compile this driver as a module, choose M here: the
366 module will be called maple_keyb.
368 config KEYBOARD_MAX7359
369 tristate "Maxim MAX7359 Key Switch Controller"
370 select INPUT_MATRIXKMAP
373 If you say yes here you get support for the Maxim MAX7359 Key
374 Switch Controller chip. This providers microprocessors with
375 management of up to 64 key switches
377 To compile this driver as a module, choose M here: the
378 module will be called max7359_keypad.
381 tristate "MELFAS MCS Touchkey"
384 Say Y here if you have the MELFAS MCS5000/5080 touchkey controller
389 To compile this driver as a module, choose M here: the
390 module will be called mcs_touchkey.
392 config KEYBOARD_MPR121
393 tristate "Freescale MPR121 Touchkey"
396 Say Y here if you have Freescale MPR121 touchkey controller
401 To compile this driver as a module, choose M here: the
402 module will be called mpr121_touchkey.
404 config KEYBOARD_SNVS_PWRKEY
405 tristate "IMX SNVS Power Key Driver"
406 depends on SOC_IMX6SX
409 This is the snvs powerkey driver for the Freescale i.MX application
410 processors that are newer than i.MX6 SX.
412 To compile this driver as a module, choose M here; the
413 module will be called snvs_pwrkey.
416 tristate "IMX keypad support"
418 select INPUT_MATRIXKMAP
420 Enable support for IMX keypad port.
422 To compile this driver as a module, choose M here: the
423 module will be called imx_keypad.
425 config KEYBOARD_NEWTON
426 tristate "Newton keyboard"
429 Say Y here if you have a Newton keyboard on a serial port.
431 To compile this driver as a module, choose M here: the
432 module will be called newtonkbd.
434 config KEYBOARD_NOMADIK
435 tristate "ST-Ericsson Nomadik SKE keyboard"
436 depends on (ARCH_NOMADIK || ARCH_U8500)
437 select INPUT_MATRIXKMAP
439 Say Y here if you want to use a keypad provided on the SKE controller
440 used on the Ux500 and Nomadik platforms
442 To compile this driver as a module, choose M here: the
443 module will be called nmk-ske-keypad.
445 config KEYBOARD_NSPIRE
446 tristate "TI-NSPIRE built-in keyboard"
447 depends on ARCH_NSPIRE && OF
448 select INPUT_MATRIXKMAP
450 Say Y here if you want to use the built-in keypad on TI-NSPIRE.
452 To compile this driver as a module, choose M here: the
453 module will be called nspire-keypad.
455 config KEYBOARD_TEGRA
456 tristate "NVIDIA Tegra internal matrix keyboard controller support"
457 depends on ARCH_TEGRA && OF
458 select INPUT_MATRIXKMAP
460 Say Y here if you want to use a matrix keyboard connected directly
461 to the internal keyboard controller on Tegra SoCs.
463 To compile this driver as a module, choose M here: the
464 module will be called tegra-kbc.
466 config KEYBOARD_OPENCORES
467 tristate "OpenCores Keyboard Controller"
470 Say Y here if you want to use the OpenCores Keyboard Controller
471 http://www.opencores.org/project,keyboardcontroller
473 To compile this driver as a module, choose M here; the
474 module will be called opencores-kbd.
476 config KEYBOARD_PXA27x
477 tristate "PXA27x/PXA3xx keypad support"
478 depends on PXA27x || PXA3xx || ARCH_MMP
479 select INPUT_MATRIXKMAP
481 Enable support for PXA27x/PXA3xx keypad controller.
483 To compile this driver as a module, choose M here: the
484 module will be called pxa27x_keypad.
486 config KEYBOARD_PXA930_ROTARY
487 tristate "PXA930/PXA935 Enhanced Rotary Controller Support"
488 depends on CPU_PXA930 || CPU_PXA935
490 Enable support for PXA930/PXA935 Enhanced Rotary Controller.
492 To compile this driver as a module, choose M here: the
493 module will be called pxa930_rotary.
495 config KEYBOARD_PMIC8XXX
496 tristate "Qualcomm PMIC8XXX keypad support"
497 depends on MFD_PM8XXX
498 select INPUT_MATRIXKMAP
500 Say Y here if you want to enable the driver for the PMIC8XXX
501 keypad provided as a reference design from Qualcomm. This is intended
502 to support upto 18x8 matrix based keypad design.
504 To compile this driver as a module, choose M here: the module will
505 be called pmic8xxx-keypad.
507 config KEYBOARD_SAMSUNG
508 tristate "Samsung keypad support"
510 select INPUT_MATRIXKMAP
512 Say Y here if you want to use the keypad on your Samsung mobile
515 To compile this driver as a module, choose M here: the
516 module will be called samsung-keypad.
518 config KEYBOARD_GOLDFISH_EVENTS
519 depends on GOLDFISH || COMPILE_TEST
520 tristate "Generic Input Event device for Goldfish"
522 Say Y here to get an input event device for the Goldfish virtual
525 To compile this driver as a module, choose M here: the
526 module will be called goldfish-events.
528 config KEYBOARD_STOWAWAY
529 tristate "Stowaway keyboard"
532 Say Y here if you have a Stowaway keyboard on a serial port.
533 Stowaway compatible keyboards like Dicota Input-PDA keyboard
534 are also supported by this driver.
536 To compile this driver as a module, choose M here: the
537 module will be called stowaway.
539 config KEYBOARD_ST_KEYSCAN
540 tristate "STMicroelectronics keyscan support"
541 depends on ARCH_STI || COMPILE_TEST
542 select INPUT_MATRIXKMAP
544 Say Y here if you want to use a keypad attached to the keyscan block
545 on some STMicroelectronics SoC devices.
547 To compile this driver as a module, choose M here: the
548 module will be called st-keyscan.
550 config KEYBOARD_SUNKBD
551 tristate "Sun Type 4 and Type 5 keyboard"
554 Say Y here if you want to use a Sun Type 4 or Type 5 keyboard,
555 connected either to the Sun keyboard connector or to an serial
556 (RS-232) port via a simple adapter.
558 To compile this driver as a module, choose M here: the
559 module will be called sunkbd.
561 config KEYBOARD_SH_KEYSC
562 tristate "SuperH KEYSC keypad support"
563 depends on ARCH_SHMOBILE || COMPILE_TEST
565 Say Y here if you want to use a keypad attached to the KEYSC block
566 on SuperH processors such as sh7722 and sh7343.
568 To compile this driver as a module, choose M here: the
569 module will be called sh_keysc.
571 config KEYBOARD_STMPE
572 tristate "STMPE keypad support"
575 select INPUT_MATRIXKMAP
577 Say Y here if you want to use the keypad controller on STMPE I/O
580 To compile this driver as a module, choose M here: the module will be
583 config KEYBOARD_SUN4I_LRADC
584 tristate "Allwinner sun4i low res adc attached tablet keys support"
585 depends on ARCH_SUNXI
587 This selects support for the Allwinner low res adc attached tablet
588 keys found on Allwinner sunxi SoCs.
590 To compile this driver as a module, choose M here: the
591 module will be called sun4i-lradc-keys.
593 config KEYBOARD_DAVINCI
594 tristate "TI DaVinci Key Scan"
595 depends on ARCH_DAVINCI_DM365
597 Say Y to enable keypad module support for the TI DaVinci
600 To compile this driver as a module, choose M here: the
601 module will be called davinci_keyscan.
603 config KEYBOARD_IPAQ_MICRO
604 tristate "Buttons on Micro SoC (iPaq h3100,h3600,h3700)"
605 depends on MFD_IPAQ_MICRO
607 Say Y to enable support for the buttons attached to
608 Micro peripheral controller on iPAQ h3100/h3600/h3700
610 To compile this driver as a module, choose M here: the
611 module will be called ipaq-micro-keys.
614 tristate "TI OMAP keypad support"
615 depends on ARCH_OMAP1
616 select INPUT_MATRIXKMAP
618 Say Y here if you want to use the OMAP keypad.
620 To compile this driver as a module, choose M here: the
621 module will be called omap-keypad.
623 config KEYBOARD_OMAP4
624 tristate "TI OMAP4+ keypad support"
625 depends on OF || ARCH_OMAP2PLUS
626 select INPUT_MATRIXKMAP
628 Say Y here if you want to use the OMAP4+ keypad.
630 To compile this driver as a module, choose M here: the
631 module will be called omap4-keypad.
633 config KEYBOARD_SPEAR
634 tristate "ST SPEAR keyboard support"
635 depends on PLAT_SPEAR
636 select INPUT_MATRIXKMAP
638 Say Y here if you want to use the SPEAR keyboard.
640 To compile this driver as a module, choose M here: the
641 module will be called spear-keboard.
643 config KEYBOARD_TC3589X
644 tristate "TC3589X Keypad support"
645 depends on MFD_TC3589X
646 select INPUT_MATRIXKMAP
648 Say Y here if you want to use the keypad controller on
649 TC35892/3 I/O expander.
651 To compile this driver as a module, choose M here: the
652 module will be called tc3589x-keypad.
654 config KEYBOARD_TWL4030
655 tristate "TI TWL4030/TWL5030/TPS659x0 keypad support"
656 depends on TWL4030_CORE
657 select INPUT_MATRIXKMAP
659 Say Y here if your board use the keypad controller on
660 TWL4030 family chips. It's safe to say enable this
661 even on boards that don't use the keypad controller.
663 To compile this driver as a module, choose M here: the
664 module will be called twl4030_keypad.
666 config KEYBOARD_XTKBD
667 tristate "XT keyboard"
670 Say Y here if you want to use the old IBM PC/XT keyboard (or
671 compatible) on your system. This is only possible with a
672 parallel port keyboard adapter, you cannot connect it to the
673 keyboard port on a PC that runs Linux.
675 To compile this driver as a module, choose M here: the
676 module will be called xtkbd.
678 config KEYBOARD_W90P910
679 tristate "W90P910 Matrix Keypad support"
680 depends on ARCH_W90X900
681 select INPUT_MATRIXKMAP
683 Say Y here to enable the matrix keypad on evaluation board
686 To compile this driver as a module, choose M here: the
687 module will be called w90p910_keypad.
689 config KEYBOARD_CROS_EC
690 tristate "ChromeOS EC keyboard"
691 select INPUT_MATRIXKMAP
692 depends on MFD_CROS_EC
694 Say Y here to enable the matrix keyboard used by ChromeOS devices
695 and implemented on the ChromeOS EC. You must enable one bus option
696 (MFD_CROS_EC_I2C or MFD_CROS_EC_SPI) to use this.
698 To compile this driver as a module, choose M here: the
699 module will be called cros_ec_keyb.
701 config KEYBOARD_CAP11XX
702 tristate "Microchip CAP11XX based touch sensors"
706 Say Y here to enable the CAP11XX touch sensor driver.
708 To compile this driver as a module, choose M here: the
709 module will be called cap11xx.
712 tristate "Broadcom keypad driver"
713 depends on OF && HAVE_CLK
714 select INPUT_MATRIXKMAP
715 default ARCH_BCM_CYGNUS
717 Say Y here if you want to use Broadcom keypad.
719 To compile this driver as a module, choose M here: the
720 module will be called bcm-keypad.