2 # Input core configuration
4 menuconfig INPUT_KEYBOARD
5 bool "Keyboards" if EXPERT || !X86
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" if EXPERT || !X86
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_LKKBD
155 tristate "DECstation/VAXstation LK201/LK401 keyboard"
158 Say Y here if you want to use a LK201 or LK401 style serial
159 keyboard. This keyboard is also useable on PCs if you attach
160 it with the inputattach program. The connector pinout is
161 described within lkkbd.c.
163 To compile this driver as a module, choose M here: the
164 module will be called lkkbd.
166 config KEYBOARD_EP93XX
167 tristate "EP93xx Matrix Keypad support"
168 depends on ARCH_EP93XX
169 select INPUT_MATRIXKMAP
171 Say Y here to enable the matrix keypad on the Cirrus EP93XX.
173 To compile this driver as a module, choose M here: the
174 module will be called ep93xx_keypad.
177 tristate "GPIO Buttons"
180 This driver implements support for buttons connected
181 to GPIO pins of various CPUs (and some other chips).
183 Say Y here if your device has buttons connected
184 directly to such GPIO pins. Your board-specific
185 setup logic must also provide a platform device,
186 with configuration data saying which GPIOs are used.
188 To compile this driver as a module, choose M here: the
189 module will be called gpio_keys.
191 config KEYBOARD_GPIO_POLLED
192 tristate "Polled GPIO buttons"
196 This driver implements support for buttons connected
197 to GPIO pins that are not capable of generating interrupts.
199 Say Y here if your device has buttons connected
200 directly to such GPIO pins. Your board-specific
201 setup logic must also provide a platform device,
202 with configuration data saying which GPIOs are used.
204 To compile this driver as a module, choose M here: the
205 module will be called gpio_keys_polled.
207 config KEYBOARD_TCA6416
208 tristate "TCA6416/TCA6408A Keypad Support"
211 This driver implements basic keypad functionality
212 for keys connected through TCA6416/TCA6408A IO expanders.
214 Say Y here if your device has keys connected to
215 TCA6416/TCA6408A IO expander. Your board-specific setup logic
216 must also provide pin-mask details(of which TCA6416 pins
217 are used for keypad).
219 If enabled the entire TCA6416 device will be managed through
222 To compile this driver as a module, choose M here: the
223 module will be called tca6416_keypad.
225 config KEYBOARD_TCA8418
226 tristate "TCA8418 Keypad Support"
227 depends on I2C && GENERIC_HARDIRQS
228 select INPUT_MATRIXKMAP
230 This driver implements basic keypad functionality
231 for keys connected through TCA8418 keypad decoder.
233 Say Y here if your device has keys connected to
234 TCA8418 keypad decoder.
236 If enabled the complete TCA8418 device will be managed through
239 To compile this driver as a module, choose M here: the
240 module will be called tca8418_keypad.
242 config KEYBOARD_MATRIX
243 tristate "GPIO driven matrix keypad support"
245 select INPUT_MATRIXKMAP
247 Enable support for GPIO driven matrix keypad.
249 To compile this driver as a module, choose M here: the
250 module will be called matrix_keypad.
252 config KEYBOARD_HIL_OLD
253 tristate "HP HIL keyboard support (simple driver)"
254 depends on GSC || HP300
257 The "Human Interface Loop" is a older, 8-channel USB-like
258 controller used in several Hewlett Packard models. This driver
259 was adapted from the one written for m68k/hp300, and implements
260 support for a keyboard attached to the HIL port, but not for
261 any other types of HIL input devices like mice or tablets.
262 However, it has been thoroughly tested and is stable.
264 If you want full HIL support including support for multiple
265 keyboards, mice, and tablets, you have to enable the
266 "HP System Device Controller i8042 Support" in the input/serio
270 tristate "HP HIL keyboard/pointer support"
271 depends on GSC || HP300
277 The "Human Interface Loop" is a older, 8-channel USB-like
278 controller used in several Hewlett Packard models.
279 This driver implements support for HIL-keyboards and pointing
280 devices (mice, tablets, touchscreens) attached
281 to your machine, so normally you should say Y here.
283 config KEYBOARD_HP6XX
284 tristate "HP Jornada 6xx keyboard"
288 Say Y here if you have a HP Jornada 620/660/680/690 and want to
289 support the built-in keyboard.
291 To compile this driver as a module, choose M here: the
292 module will be called jornada680_kbd.
294 config KEYBOARD_HP7XX
295 tristate "HP Jornada 7xx keyboard"
296 depends on SA1100_JORNADA720_SSP && SA1100_SSP
298 Say Y here if you have a HP Jornada 710/720/728 and want to
299 support the built-in keyboard.
301 To compile this driver as a module, choose M here: the
302 module will be called jornada720_kbd.
304 config KEYBOARD_LM8323
305 tristate "LM8323 keypad chip"
306 depends on I2C && GENERIC_HARDIRQS
307 depends on LEDS_CLASS
309 If you say yes here you get support for the National Semiconductor
310 LM8323 keypad controller.
312 To compile this driver as a module, choose M here: the
313 module will be called lm8323.
315 config KEYBOARD_LM8333
316 tristate "LM8333 keypad chip"
318 select INPUT_MATRIXKMAP
320 If you say yes here you get support for the National Semiconductor
321 LM8333 keypad controller.
323 To compile this driver as a module, choose M here: the
324 module will be called lm8333.
326 config KEYBOARD_LOCOMO
327 tristate "LoCoMo Keyboard Support"
328 depends on SHARP_LOCOMO
330 Say Y here if you are running Linux on a Sharp Zaurus Collie or Poodle based PDA
332 To compile this driver as a module, choose M here: the
333 module will be called locomokbd.
335 config KEYBOARD_LPC32XX
336 tristate "LPC32XX matrix key scanner support"
337 depends on ARCH_LPC32XX && OF
338 select INPUT_MATRIXKMAP
340 Say Y here if you want to use NXP LPC32XX SoC key scanner interface,
341 connected to a key matrix.
343 To compile this driver as a module, choose M here: the
344 module will be called lpc32xx-keys.
346 config KEYBOARD_MAPLE
347 tristate "Maple bus keyboard"
348 depends on SH_DREAMCAST && MAPLE
350 Say Y here if you have a Dreamcast console running Linux and have
351 a keyboard attached to its Maple bus.
353 To compile this driver as a module, choose M here: the
354 module will be called maple_keyb.
356 config KEYBOARD_MAX7359
357 tristate "Maxim MAX7359 Key Switch Controller"
360 If you say yes here you get support for the Maxim MAX7359 Key
361 Switch Controller chip. This providers microprocessors with
362 management of up to 64 key switches
364 To compile this driver as a module, choose M here: the
365 module will be called max7359_keypad.
368 tristate "MELFAS MCS Touchkey"
371 Say Y here if you have the MELFAS MCS5000/5080 touchkey controller
376 To compile this driver as a module, choose M here: the
377 module will be called mcs_touchkey.
379 config KEYBOARD_MPR121
380 tristate "Freescale MPR121 Touchkey"
383 Say Y here if you have Freescale MPR121 touchkey controller
388 To compile this driver as a module, choose M here: the
389 module will be called mpr121_touchkey.
392 tristate "IMX keypad support"
394 select INPUT_MATRIXKMAP
396 Enable support for IMX keypad port.
398 To compile this driver as a module, choose M here: the
399 module will be called imx_keypad.
401 config KEYBOARD_NEWTON
402 tristate "Newton keyboard"
405 Say Y here if you have a Newton keyboard on a serial port.
407 To compile this driver as a module, choose M here: the
408 module will be called newtonkbd.
410 config KEYBOARD_NOMADIK
411 tristate "ST-Ericsson Nomadik SKE keyboard"
412 depends on (ARCH_NOMADIK || ARCH_U8500)
413 select INPUT_MATRIXKMAP
415 Say Y here if you want to use a keypad provided on the SKE controller
416 used on the Ux500 and Nomadik platforms
418 To compile this driver as a module, choose M here: the
419 module will be called nmk-ske-keypad.
421 config KEYBOARD_TEGRA
422 tristate "NVIDIA Tegra internal matrix keyboard controller support"
423 depends on ARCH_TEGRA && OF
424 select INPUT_MATRIXKMAP
426 Say Y here if you want to use a matrix keyboard connected directly
427 to the internal keyboard controller on Tegra SoCs.
429 To compile this driver as a module, choose M here: the
430 module will be called tegra-kbc.
432 config KEYBOARD_OPENCORES
433 tristate "OpenCores Keyboard Controller"
436 Say Y here if you want to use the OpenCores Keyboard Controller
437 http://www.opencores.org/project,keyboardcontroller
439 To compile this driver as a module, choose M here; the
440 module will be called opencores-kbd.
442 config KEYBOARD_PXA27x
443 tristate "PXA27x/PXA3xx keypad support"
444 depends on PXA27x || PXA3xx || ARCH_MMP
446 Enable support for PXA27x/PXA3xx keypad controller.
448 To compile this driver as a module, choose M here: the
449 module will be called pxa27x_keypad.
451 config KEYBOARD_PXA930_ROTARY
452 tristate "PXA930/PXA935 Enhanced Rotary Controller Support"
453 depends on CPU_PXA930 || CPU_PXA935
455 Enable support for PXA930/PXA935 Enhanced Rotary Controller.
457 To compile this driver as a module, choose M here: the
458 module will be called pxa930_rotary.
460 config KEYBOARD_PMIC8XXX
461 tristate "Qualcomm PMIC8XXX keypad support"
462 depends on MFD_PM8XXX
463 select INPUT_MATRIXKMAP
465 Say Y here if you want to enable the driver for the PMIC8XXX
466 keypad provided as a reference design from Qualcomm. This is intended
467 to support upto 18x8 matrix based keypad design.
469 To compile this driver as a module, choose M here: the module will
470 be called pmic8xxx-keypad.
472 config KEYBOARD_SAMSUNG
473 tristate "Samsung keypad support"
475 select INPUT_MATRIXKMAP
477 Say Y here if you want to use the keypad on your Samsung mobile
480 To compile this driver as a module, choose M here: the
481 module will be called samsung-keypad.
483 config KEYBOARD_GOLDFISH_EVENTS
485 tristate "Generic Input Event device for Goldfish"
487 Say Y here to get an input event device for the Goldfish virtual
490 To compile this driver as a module, choose M here: the
491 module will be called goldfish-events.
493 config KEYBOARD_STOWAWAY
494 tristate "Stowaway keyboard"
497 Say Y here if you have a Stowaway keyboard on a serial port.
498 Stowaway compatible keyboards like Dicota Input-PDA keyboard
499 are also supported by this driver.
501 To compile this driver as a module, choose M here: the
502 module will be called stowaway.
504 config KEYBOARD_SUNKBD
505 tristate "Sun Type 4 and Type 5 keyboard"
508 Say Y here if you want to use a Sun Type 4 or Type 5 keyboard,
509 connected either to the Sun keyboard connector or to an serial
510 (RS-232) port via a simple adapter.
512 To compile this driver as a module, choose M here: the
513 module will be called sunkbd.
515 config KEYBOARD_SH_KEYSC
516 tristate "SuperH KEYSC keypad support"
517 depends on SUPERH || ARCH_SHMOBILE
519 Say Y here if you want to use a keypad attached to the KEYSC block
520 on SuperH processors such as sh7722 and sh7343.
522 To compile this driver as a module, choose M here: the
523 module will be called sh_keysc.
525 config KEYBOARD_STMPE
526 tristate "STMPE keypad support"
528 select INPUT_MATRIXKMAP
530 Say Y here if you want to use the keypad controller on STMPE I/O
533 To compile this driver as a module, choose M here: the module will be
536 config KEYBOARD_DAVINCI
537 tristate "TI DaVinci Key Scan"
538 depends on ARCH_DAVINCI_DM365
540 Say Y to enable keypad module support for the TI DaVinci
543 To compile this driver as a module, choose M here: the
544 module will be called davinci_keyscan.
547 tristate "TI OMAP keypad support"
548 depends on ARCH_OMAP1
549 select INPUT_MATRIXKMAP
551 Say Y here if you want to use the OMAP keypad.
553 To compile this driver as a module, choose M here: the
554 module will be called omap-keypad.
556 config KEYBOARD_OMAP4
557 tristate "TI OMAP4+ keypad support"
558 depends on ARCH_OMAP2PLUS
559 select INPUT_MATRIXKMAP
561 Say Y here if you want to use the OMAP4+ keypad.
563 To compile this driver as a module, choose M here: the
564 module will be called omap4-keypad.
566 config KEYBOARD_SPEAR
567 tristate "ST SPEAR keyboard support"
568 depends on PLAT_SPEAR
569 select INPUT_MATRIXKMAP
571 Say Y here if you want to use the SPEAR keyboard.
573 To compile this driver as a module, choose M here: the
574 module will be called spear-keboard.
576 config KEYBOARD_TC3589X
577 tristate "TC3589X Keypad support"
578 depends on MFD_TC3589X
579 select INPUT_MATRIXKMAP
581 Say Y here if you want to use the keypad controller on
582 TC35892/3 I/O expander.
584 To compile this driver as a module, choose M here: the
585 module will be called tc3589x-keypad.
587 config KEYBOARD_TNETV107X
588 tristate "TI TNETV107X keypad support"
589 depends on ARCH_DAVINCI_TNETV107X
590 select INPUT_MATRIXKMAP
592 Say Y here if you want to use the TNETV107X keypad.
594 To compile this driver as a module, choose M here: the
595 module will be called tnetv107x-keypad.
597 config KEYBOARD_TWL4030
598 tristate "TI TWL4030/TWL5030/TPS659x0 keypad support"
599 depends on TWL4030_CORE
600 select INPUT_MATRIXKMAP
602 Say Y here if your board use the keypad controller on
603 TWL4030 family chips. It's safe to say enable this
604 even on boards that don't use the keypad controller.
606 To compile this driver as a module, choose M here: the
607 module will be called twl4030_keypad.
609 config KEYBOARD_XTKBD
610 tristate "XT keyboard"
613 Say Y here if you want to use the old IBM PC/XT keyboard (or
614 compatible) on your system. This is only possible with a
615 parallel port keyboard adapter, you cannot connect it to the
616 keyboard port on a PC that runs Linux.
618 To compile this driver as a module, choose M here: the
619 module will be called xtkbd.
621 config KEYBOARD_W90P910
622 tristate "W90P910 Matrix Keypad support"
623 depends on ARCH_W90X900
624 select INPUT_MATRIXKMAP
626 Say Y here to enable the matrix keypad on evaluation board
629 To compile this driver as a module, choose M here: the
630 module will be called w90p910_keypad.
632 config KEYBOARD_CROS_EC
633 tristate "ChromeOS EC keyboard"
634 select INPUT_MATRIXKMAP
635 depends on MFD_CROS_EC
637 Say Y here to enable the matrix keyboard used by ChromeOS devices
638 and implemented on the ChromeOS EC. You must enable one bus option
639 (MFD_CROS_EC_I2C or MFD_CROS_EC_SPI) to use this.
641 To compile this driver as a module, choose M here: the
642 module will be called cros_ec_keyb.