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 X86
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"
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"
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"
372 If you say yes here you get support for the Maxim MAX7359 Key
373 Switch Controller chip. This providers microprocessors with
374 management of up to 64 key switches
376 To compile this driver as a module, choose M here: the
377 module will be called max7359_keypad.
380 tristate "MELFAS MCS Touchkey"
383 Say Y here if you have the MELFAS MCS5000/5080 touchkey controller
388 To compile this driver as a module, choose M here: the
389 module will be called mcs_touchkey.
391 config KEYBOARD_MPR121
392 tristate "Freescale MPR121 Touchkey"
395 Say Y here if you have Freescale MPR121 touchkey controller
400 To compile this driver as a module, choose M here: the
401 module will be called mpr121_touchkey.
404 tristate "IMX keypad support"
406 select INPUT_MATRIXKMAP
408 Enable support for IMX keypad port.
410 To compile this driver as a module, choose M here: the
411 module will be called imx_keypad.
413 config KEYBOARD_NEWTON
414 tristate "Newton keyboard"
417 Say Y here if you have a Newton keyboard on a serial port.
419 To compile this driver as a module, choose M here: the
420 module will be called newtonkbd.
422 config KEYBOARD_NOMADIK
423 tristate "ST-Ericsson Nomadik SKE keyboard"
424 depends on (ARCH_NOMADIK || ARCH_U8500)
425 select INPUT_MATRIXKMAP
427 Say Y here if you want to use a keypad provided on the SKE controller
428 used on the Ux500 and Nomadik platforms
430 To compile this driver as a module, choose M here: the
431 module will be called nmk-ske-keypad.
433 config KEYBOARD_NSPIRE
434 tristate "TI-NSPIRE built-in keyboard"
435 depends on ARCH_NSPIRE && OF
436 select INPUT_MATRIXKMAP
438 Say Y here if you want to use the built-in keypad on TI-NSPIRE.
440 To compile this driver as a module, choose M here: the
441 module will be called nspire-keypad.
443 config KEYBOARD_TEGRA
444 tristate "NVIDIA Tegra internal matrix keyboard controller support"
445 depends on ARCH_TEGRA && OF
446 select INPUT_MATRIXKMAP
448 Say Y here if you want to use a matrix keyboard connected directly
449 to the internal keyboard controller on Tegra SoCs.
451 To compile this driver as a module, choose M here: the
452 module will be called tegra-kbc.
454 config KEYBOARD_OPENCORES
455 tristate "OpenCores Keyboard Controller"
458 Say Y here if you want to use the OpenCores Keyboard Controller
459 http://www.opencores.org/project,keyboardcontroller
461 To compile this driver as a module, choose M here; the
462 module will be called opencores-kbd.
464 config KEYBOARD_PXA27x
465 tristate "PXA27x/PXA3xx keypad support"
466 depends on PXA27x || PXA3xx || ARCH_MMP
467 select INPUT_MATRIXKMAP
469 Enable support for PXA27x/PXA3xx keypad controller.
471 To compile this driver as a module, choose M here: the
472 module will be called pxa27x_keypad.
474 config KEYBOARD_PXA930_ROTARY
475 tristate "PXA930/PXA935 Enhanced Rotary Controller Support"
476 depends on CPU_PXA930 || CPU_PXA935
478 Enable support for PXA930/PXA935 Enhanced Rotary Controller.
480 To compile this driver as a module, choose M here: the
481 module will be called pxa930_rotary.
483 config KEYBOARD_PMIC8XXX
484 tristate "Qualcomm PMIC8XXX keypad support"
485 depends on MFD_PM8XXX
486 select INPUT_MATRIXKMAP
488 Say Y here if you want to enable the driver for the PMIC8XXX
489 keypad provided as a reference design from Qualcomm. This is intended
490 to support upto 18x8 matrix based keypad design.
492 To compile this driver as a module, choose M here: the module will
493 be called pmic8xxx-keypad.
495 config KEYBOARD_SAMSUNG
496 tristate "Samsung keypad support"
498 select INPUT_MATRIXKMAP
500 Say Y here if you want to use the keypad on your Samsung mobile
503 To compile this driver as a module, choose M here: the
504 module will be called samsung-keypad.
506 config KEYBOARD_GOLDFISH_EVENTS
508 tristate "Generic Input Event device for Goldfish"
510 Say Y here to get an input event device for the Goldfish virtual
513 To compile this driver as a module, choose M here: the
514 module will be called goldfish-events.
516 config KEYBOARD_STOWAWAY
517 tristate "Stowaway keyboard"
520 Say Y here if you have a Stowaway keyboard on a serial port.
521 Stowaway compatible keyboards like Dicota Input-PDA keyboard
522 are also supported by this driver.
524 To compile this driver as a module, choose M here: the
525 module will be called stowaway.
527 config KEYBOARD_ST_KEYSCAN
528 tristate "STMicroelectronics keyscan support"
529 depends on ARCH_STI || COMPILE_TEST
530 select INPUT_MATRIXKMAP
532 Say Y here if you want to use a keypad attached to the keyscan block
533 on some STMicroelectronics SoC devices.
535 To compile this driver as a module, choose M here: the
536 module will be called st-keyscan.
538 config KEYBOARD_SUNKBD
539 tristate "Sun Type 4 and Type 5 keyboard"
542 Say Y here if you want to use a Sun Type 4 or Type 5 keyboard,
543 connected either to the Sun keyboard connector or to an serial
544 (RS-232) port via a simple adapter.
546 To compile this driver as a module, choose M here: the
547 module will be called sunkbd.
549 config KEYBOARD_SH_KEYSC
550 tristate "SuperH KEYSC keypad support"
551 depends on SUPERH || ARCH_SHMOBILE || COMPILE_TEST
553 Say Y here if you want to use a keypad attached to the KEYSC block
554 on SuperH processors such as sh7722 and sh7343.
556 To compile this driver as a module, choose M here: the
557 module will be called sh_keysc.
559 config KEYBOARD_STMPE
560 tristate "STMPE keypad support"
562 select INPUT_MATRIXKMAP
564 Say Y here if you want to use the keypad controller on STMPE I/O
567 To compile this driver as a module, choose M here: the module will be
570 config KEYBOARD_DAVINCI
571 tristate "TI DaVinci Key Scan"
572 depends on ARCH_DAVINCI_DM365
574 Say Y to enable keypad module support for the TI DaVinci
577 To compile this driver as a module, choose M here: the
578 module will be called davinci_keyscan.
581 tristate "TI OMAP keypad support"
582 depends on ARCH_OMAP1
583 select INPUT_MATRIXKMAP
585 Say Y here if you want to use the OMAP keypad.
587 To compile this driver as a module, choose M here: the
588 module will be called omap-keypad.
590 config KEYBOARD_OMAP4
591 tristate "TI OMAP4+ keypad support"
592 depends on ARCH_OMAP2PLUS
593 select INPUT_MATRIXKMAP
595 Say Y here if you want to use the OMAP4+ keypad.
597 To compile this driver as a module, choose M here: the
598 module will be called omap4-keypad.
600 config KEYBOARD_SPEAR
601 tristate "ST SPEAR keyboard support"
602 depends on PLAT_SPEAR
603 select INPUT_MATRIXKMAP
605 Say Y here if you want to use the SPEAR keyboard.
607 To compile this driver as a module, choose M here: the
608 module will be called spear-keboard.
610 config KEYBOARD_TC3589X
611 tristate "TC3589X Keypad support"
612 depends on MFD_TC3589X
613 select INPUT_MATRIXKMAP
615 Say Y here if you want to use the keypad controller on
616 TC35892/3 I/O expander.
618 To compile this driver as a module, choose M here: the
619 module will be called tc3589x-keypad.
621 config KEYBOARD_TWL4030
622 tristate "TI TWL4030/TWL5030/TPS659x0 keypad support"
623 depends on TWL4030_CORE
624 select INPUT_MATRIXKMAP
626 Say Y here if your board use the keypad controller on
627 TWL4030 family chips. It's safe to say enable this
628 even on boards that don't use the keypad controller.
630 To compile this driver as a module, choose M here: the
631 module will be called twl4030_keypad.
633 config KEYBOARD_XTKBD
634 tristate "XT keyboard"
637 Say Y here if you want to use the old IBM PC/XT keyboard (or
638 compatible) on your system. This is only possible with a
639 parallel port keyboard adapter, you cannot connect it to the
640 keyboard port on a PC that runs Linux.
642 To compile this driver as a module, choose M here: the
643 module will be called xtkbd.
645 config KEYBOARD_W90P910
646 tristate "W90P910 Matrix Keypad support"
647 depends on ARCH_W90X900
648 select INPUT_MATRIXKMAP
650 Say Y here to enable the matrix keypad on evaluation board
653 To compile this driver as a module, choose M here: the
654 module will be called w90p910_keypad.
656 config KEYBOARD_CROS_EC
657 tristate "ChromeOS EC keyboard"
658 select INPUT_MATRIXKMAP
659 depends on MFD_CROS_EC
661 Say Y here to enable the matrix keyboard used by ChromeOS devices
662 and implemented on the ChromeOS EC. You must enable one bus option
663 (MFD_CROS_EC_I2C or MFD_CROS_EC_SPI) to use this.
665 To compile this driver as a module, choose M here: the
666 module will be called cros_ec_keyb.