ARM: plat-nomadik: move MTU, kill plat-nomadik
[deliverable/linux.git] / drivers / input / keyboard / Kconfig
1 #
2 # Input core configuration
3 #
4 menuconfig INPUT_KEYBOARD
5 bool "Keyboards" if EXPERT || !X86
6 default y
7 help
8 Say Y here, and a list of supported keyboards will be displayed.
9 This option doesn't affect the kernel.
10
11 If unsure, say Y.
12
13 if INPUT_KEYBOARD
14
15 config KEYBOARD_ADP5520
16 tristate "Keypad Support for ADP5520 PMIC"
17 depends on PMIC_ADP5520
18 help
19 This option enables support for the keypad scan matrix
20 on Analog Devices ADP5520 PMICs.
21
22 To compile this driver as a module, choose M here: the module will
23 be called adp5520-keys.
24
25 config KEYBOARD_ADP5588
26 tristate "ADP5588/87 I2C QWERTY Keypad and IO Expander"
27 depends on I2C
28 help
29 Say Y here if you want to use a ADP5588/87 attached to your
30 system I2C bus.
31
32 To compile this driver as a module, choose M here: the
33 module will be called adp5588-keys.
34
35 config KEYBOARD_ADP5589
36 tristate "ADP5585/ADP5589 I2C QWERTY Keypad and IO Expander"
37 depends on I2C
38 help
39 Say Y here if you want to use a ADP5585/ADP5589 attached to your
40 system I2C bus.
41
42 To compile this driver as a module, choose M here: the
43 module will be called adp5589-keys.
44
45 config KEYBOARD_AMIGA
46 tristate "Amiga keyboard"
47 depends on AMIGA
48 help
49 Say Y here if you are running Linux on any AMIGA and have a keyboard
50 attached.
51
52 To compile this driver as a module, choose M here: the
53 module will be called amikbd.
54
55 config ATARI_KBD_CORE
56 bool
57
58 config KEYBOARD_ATARI
59 tristate "Atari keyboard"
60 depends on ATARI
61 select ATARI_KBD_CORE
62 help
63 Say Y here if you are running Linux on any Atari and have a keyboard
64 attached.
65
66 To compile this driver as a module, choose M here: the
67 module will be called atakbd.
68
69 config KEYBOARD_ATKBD
70 tristate "AT keyboard" if EXPERT || !X86
71 default y
72 select SERIO
73 select SERIO_LIBPS2
74 select SERIO_I8042 if X86
75 select SERIO_GSCPS2 if GSC
76 help
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.
81
82 If unsure, say Y.
83
84 To compile this driver as a module, choose M here: the
85 module will be called atkbd.
86
87 config KEYBOARD_ATKBD_HP_KEYCODES
88 bool "Use HP keyboard scancodes"
89 depends on PARISC && KEYBOARD_ATKBD
90 default y
91 help
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
94 PA-RISC keyboards.
95
96 Say N if you use a standard keyboard.
97
98 config KEYBOARD_ATKBD_RDI_KEYCODES
99 bool "Use PrecisionBook keyboard scancodes"
100 depends on KEYBOARD_ATKBD_HP_KEYCODES
101 default n
102 help
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).
105
106 The PrecisionBook has five keys that conflict with those used by most
107 AT and PS/2 keyboards. These are as follows:
108
109 PrecisionBook Standard AT or PS/2
110
111 F1 F12
112 Left Ctrl Left Alt
113 Caps Lock Left Ctrl
114 Right Ctrl Caps Lock
115 Left 102nd key (the key to the right of Left Shift)
116
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.
120
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
123 left-hand column.
124
125 config KEYBOARD_QT1070
126 tristate "Atmel AT42QT1070 Touch Sensor Chip"
127 depends on I2C
128 help
129 Say Y here if you want to use Atmel AT42QT1070 QTouch
130 Sensor chip as input device.
131
132 To compile this driver as a module, choose M here:
133 the module will be called qt1070
134
135 config KEYBOARD_QT2160
136 tristate "Atmel AT42QT2160 Touch Sensor Chip"
137 depends on I2C && EXPERIMENTAL
138 help
139 If you say yes here you get support for Atmel AT42QT2160 Touch
140 Sensor chip as a keyboard input.
141
142 This driver can also be built as a module. If so, the module
143 will be called qt2160.
144
145 config KEYBOARD_BFIN
146 tristate "Blackfin BF54x keypad support"
147 depends on (BF54x && !BF544)
148 help
149 Say Y here if you want to use the BF54x keypad.
150
151 To compile this driver as a module, choose M here: the
152 module will be called bf54x-keys.
153
154 config KEYBOARD_LKKBD
155 tristate "DECstation/VAXstation LK201/LK401 keyboard"
156 select SERIO
157 help
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.
162
163 To compile this driver as a module, choose M here: the
164 module will be called lkkbd.
165
166 config KEYBOARD_EP93XX
167 tristate "EP93xx Matrix Keypad support"
168 depends on ARCH_EP93XX
169 select INPUT_MATRIXKMAP
170 help
171 Say Y here to enable the matrix keypad on the Cirrus EP93XX.
172
173 To compile this driver as a module, choose M here: the
174 module will be called ep93xx_keypad.
175
176 config KEYBOARD_GPIO
177 tristate "GPIO Buttons"
178 depends on GENERIC_GPIO
179 help
180 This driver implements support for buttons connected
181 to GPIO pins of various CPUs (and some other chips).
182
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.
187
188 To compile this driver as a module, choose M here: the
189 module will be called gpio_keys.
190
191 config KEYBOARD_GPIO_POLLED
192 tristate "Polled GPIO buttons"
193 depends on GENERIC_GPIO
194 select INPUT_POLLDEV
195 help
196 This driver implements support for buttons connected
197 to GPIO pins that are not capable of generating interrupts.
198
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.
203
204 To compile this driver as a module, choose M here: the
205 module will be called gpio_keys_polled.
206
207 config KEYBOARD_TCA6416
208 tristate "TCA6416/TCA6408A Keypad Support"
209 depends on I2C
210 help
211 This driver implements basic keypad functionality
212 for keys connected through TCA6416/TCA6408A IO expanders.
213
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).
218
219 If enabled the entire TCA6416 device will be managed through
220 this driver.
221
222 To compile this driver as a module, choose M here: the
223 module will be called tca6416_keypad.
224
225 config KEYBOARD_TCA8418
226 tristate "TCA8418 Keypad Support"
227 depends on I2C
228 select INPUT_MATRIXKMAP
229 help
230 This driver implements basic keypad functionality
231 for keys connected through TCA8418 keypad decoder.
232
233 Say Y here if your device has keys connected to
234 TCA8418 keypad decoder.
235
236 If enabled the complete TCA8418 device will be managed through
237 this driver.
238
239 To compile this driver as a module, choose M here: the
240 module will be called tca8418_keypad.
241
242 config KEYBOARD_MATRIX
243 tristate "GPIO driven matrix keypad support"
244 depends on GENERIC_GPIO
245 select INPUT_MATRIXKMAP
246 help
247 Enable support for GPIO driven matrix keypad.
248
249 To compile this driver as a module, choose M here: the
250 module will be called matrix_keypad.
251
252 config KEYBOARD_HIL_OLD
253 tristate "HP HIL keyboard support (simple driver)"
254 depends on GSC || HP300
255 default y
256 help
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.
263
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
267 submenu.
268
269 config KEYBOARD_HIL
270 tristate "HP HIL keyboard/pointer support"
271 depends on GSC || HP300
272 default y
273 select HP_SDC
274 select HIL_MLC
275 select SERIO
276 help
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.
282
283 config KEYBOARD_HP6XX
284 tristate "HP Jornada 6xx keyboard"
285 depends on SH_HP6XX
286 select INPUT_POLLDEV
287 help
288 Say Y here if you have a HP Jornada 620/660/680/690 and want to
289 support the built-in keyboard.
290
291 To compile this driver as a module, choose M here: the
292 module will be called jornada680_kbd.
293
294 config KEYBOARD_HP7XX
295 tristate "HP Jornada 7xx keyboard"
296 depends on SA1100_JORNADA720_SSP && SA1100_SSP
297 help
298 Say Y here if you have a HP Jornada 710/720/728 and want to
299 support the built-in keyboard.
300
301 To compile this driver as a module, choose M here: the
302 module will be called jornada720_kbd.
303
304 config KEYBOARD_LM8323
305 tristate "LM8323 keypad chip"
306 depends on I2C
307 depends on LEDS_CLASS
308 help
309 If you say yes here you get support for the National Semiconductor
310 LM8323 keypad controller.
311
312 To compile this driver as a module, choose M here: the
313 module will be called lm8323.
314
315 config KEYBOARD_LM8333
316 tristate "LM8333 keypad chip"
317 depends on I2C
318 select INPUT_MATRIXKMAP
319 help
320 If you say yes here you get support for the National Semiconductor
321 LM8333 keypad controller.
322
323 To compile this driver as a module, choose M here: the
324 module will be called lm8333.
325
326 config KEYBOARD_LOCOMO
327 tristate "LoCoMo Keyboard Support"
328 depends on SHARP_LOCOMO
329 help
330 Say Y here if you are running Linux on a Sharp Zaurus Collie or Poodle based PDA
331
332 To compile this driver as a module, choose M here: the
333 module will be called locomokbd.
334
335 config KEYBOARD_LPC32XX
336 tristate "LPC32XX matrix key scanner support"
337 depends on ARCH_LPC32XX && OF
338 help
339 Say Y here if you want to use NXP LPC32XX SoC key scanner interface,
340 connected to a key matrix.
341
342 To compile this driver as a module, choose M here: the
343 module will be called lpc32xx-keys.
344
345 config KEYBOARD_MAPLE
346 tristate "Maple bus keyboard"
347 depends on SH_DREAMCAST && MAPLE
348 help
349 Say Y here if you have a Dreamcast console running Linux and have
350 a keyboard attached to its Maple bus.
351
352 To compile this driver as a module, choose M here: the
353 module will be called maple_keyb.
354
355 config KEYBOARD_MAX7359
356 tristate "Maxim MAX7359 Key Switch Controller"
357 depends on I2C
358 help
359 If you say yes here you get support for the Maxim MAX7359 Key
360 Switch Controller chip. This providers microprocessors with
361 management of up to 64 key switches
362
363 To compile this driver as a module, choose M here: the
364 module will be called max7359_keypad.
365
366 config KEYBOARD_MCS
367 tristate "MELFAS MCS Touchkey"
368 depends on I2C
369 help
370 Say Y here if you have the MELFAS MCS5000/5080 touchkey controller
371 chip in your system.
372
373 If unsure, say N.
374
375 To compile this driver as a module, choose M here: the
376 module will be called mcs_touchkey.
377
378 config KEYBOARD_MPR121
379 tristate "Freescale MPR121 Touchkey"
380 depends on I2C
381 help
382 Say Y here if you have Freescale MPR121 touchkey controller
383 chip in your system.
384
385 If unsure, say N.
386
387 To compile this driver as a module, choose M here: the
388 module will be called mpr121_touchkey.
389
390 config KEYBOARD_IMX
391 tristate "IMX keypad support"
392 depends on ARCH_MXC
393 select INPUT_MATRIXKMAP
394 help
395 Enable support for IMX keypad port.
396
397 To compile this driver as a module, choose M here: the
398 module will be called imx_keypad.
399
400 config KEYBOARD_NEWTON
401 tristate "Newton keyboard"
402 select SERIO
403 help
404 Say Y here if you have a Newton keyboard on a serial port.
405
406 To compile this driver as a module, choose M here: the
407 module will be called newtonkbd.
408
409 config KEYBOARD_NOMADIK
410 tristate "ST-Ericsson Nomadik SKE keyboard"
411 depends on (ARCH_NOMADIK || ARCH_U8500)
412 select INPUT_MATRIXKMAP
413 help
414 Say Y here if you want to use a keypad provided on the SKE controller
415 used on the Ux500 and Nomadik platforms
416
417 To compile this driver as a module, choose M here: the
418 module will be called nmk-ske-keypad.
419
420 config KEYBOARD_TEGRA
421 tristate "NVIDIA Tegra internal matrix keyboard controller support"
422 depends on ARCH_TEGRA
423 select INPUT_MATRIXKMAP
424 help
425 Say Y here if you want to use a matrix keyboard connected directly
426 to the internal keyboard controller on Tegra SoCs.
427
428 To compile this driver as a module, choose M here: the
429 module will be called tegra-kbc.
430
431 config KEYBOARD_OPENCORES
432 tristate "OpenCores Keyboard Controller"
433 help
434 Say Y here if you want to use the OpenCores Keyboard Controller
435 http://www.opencores.org/project,keyboardcontroller
436
437 To compile this driver as a module, choose M here; the
438 module will be called opencores-kbd.
439
440 config KEYBOARD_PXA27x
441 tristate "PXA27x/PXA3xx keypad support"
442 depends on PXA27x || PXA3xx || ARCH_MMP
443 help
444 Enable support for PXA27x/PXA3xx keypad controller.
445
446 To compile this driver as a module, choose M here: the
447 module will be called pxa27x_keypad.
448
449 config KEYBOARD_PXA930_ROTARY
450 tristate "PXA930/PXA935 Enhanced Rotary Controller Support"
451 depends on CPU_PXA930 || CPU_PXA935
452 help
453 Enable support for PXA930/PXA935 Enhanced Rotary Controller.
454
455 To compile this driver as a module, choose M here: the
456 module will be called pxa930_rotary.
457
458 config KEYBOARD_PMIC8XXX
459 tristate "Qualcomm PMIC8XXX keypad support"
460 depends on MFD_PM8XXX
461 select INPUT_MATRIXKMAP
462 help
463 Say Y here if you want to enable the driver for the PMIC8XXX
464 keypad provided as a reference design from Qualcomm. This is intended
465 to support upto 18x8 matrix based keypad design.
466
467 To compile this driver as a module, choose M here: the module will
468 be called pmic8xxx-keypad.
469
470 config KEYBOARD_SAMSUNG
471 tristate "Samsung keypad support"
472 depends on HAVE_CLK
473 select INPUT_MATRIXKMAP
474 help
475 Say Y here if you want to use the keypad on your Samsung mobile
476 device.
477
478 To compile this driver as a module, choose M here: the
479 module will be called samsung-keypad.
480
481 config KEYBOARD_STOWAWAY
482 tristate "Stowaway keyboard"
483 select SERIO
484 help
485 Say Y here if you have a Stowaway keyboard on a serial port.
486 Stowaway compatible keyboards like Dicota Input-PDA keyboard
487 are also supported by this driver.
488
489 To compile this driver as a module, choose M here: the
490 module will be called stowaway.
491
492 config KEYBOARD_SUNKBD
493 tristate "Sun Type 4 and Type 5 keyboard"
494 select SERIO
495 help
496 Say Y here if you want to use a Sun Type 4 or Type 5 keyboard,
497 connected either to the Sun keyboard connector or to an serial
498 (RS-232) port via a simple adapter.
499
500 To compile this driver as a module, choose M here: the
501 module will be called sunkbd.
502
503 config KEYBOARD_SH_KEYSC
504 tristate "SuperH KEYSC keypad support"
505 depends on SUPERH || ARCH_SHMOBILE
506 help
507 Say Y here if you want to use a keypad attached to the KEYSC block
508 on SuperH processors such as sh7722 and sh7343.
509
510 To compile this driver as a module, choose M here: the
511 module will be called sh_keysc.
512
513 config KEYBOARD_STMPE
514 tristate "STMPE keypad support"
515 depends on MFD_STMPE
516 select INPUT_MATRIXKMAP
517 help
518 Say Y here if you want to use the keypad controller on STMPE I/O
519 expanders.
520
521 To compile this driver as a module, choose M here: the module will be
522 called stmpe-keypad.
523
524 config KEYBOARD_DAVINCI
525 tristate "TI DaVinci Key Scan"
526 depends on ARCH_DAVINCI_DM365
527 help
528 Say Y to enable keypad module support for the TI DaVinci
529 platforms (DM365).
530
531 To compile this driver as a module, choose M here: the
532 module will be called davinci_keyscan.
533
534 config KEYBOARD_OMAP
535 tristate "TI OMAP keypad support"
536 depends on ARCH_OMAP1
537 select INPUT_MATRIXKMAP
538 help
539 Say Y here if you want to use the OMAP keypad.
540
541 To compile this driver as a module, choose M here: the
542 module will be called omap-keypad.
543
544 config KEYBOARD_OMAP4
545 tristate "TI OMAP4+ keypad support"
546 select INPUT_MATRIXKMAP
547 help
548 Say Y here if you want to use the OMAP4+ keypad.
549
550 To compile this driver as a module, choose M here: the
551 module will be called omap4-keypad.
552
553 config KEYBOARD_SPEAR
554 tristate "ST SPEAR keyboard support"
555 depends on PLAT_SPEAR
556 select INPUT_MATRIXKMAP
557 help
558 Say Y here if you want to use the SPEAR keyboard.
559
560 To compile this driver as a module, choose M here: the
561 module will be called spear-keboard.
562
563 config KEYBOARD_TC3589X
564 tristate "TC3589X Keypad support"
565 depends on MFD_TC3589X
566 select INPUT_MATRIXKMAP
567 help
568 Say Y here if you want to use the keypad controller on
569 TC35892/3 I/O expander.
570
571 To compile this driver as a module, choose M here: the
572 module will be called tc3589x-keypad.
573
574 config KEYBOARD_TNETV107X
575 tristate "TI TNETV107X keypad support"
576 depends on ARCH_DAVINCI_TNETV107X
577 select INPUT_MATRIXKMAP
578 help
579 Say Y here if you want to use the TNETV107X keypad.
580
581 To compile this driver as a module, choose M here: the
582 module will be called tnetv107x-keypad.
583
584 config KEYBOARD_TWL4030
585 tristate "TI TWL4030/TWL5030/TPS659x0 keypad support"
586 depends on TWL4030_CORE
587 select INPUT_MATRIXKMAP
588 help
589 Say Y here if your board use the keypad controller on
590 TWL4030 family chips. It's safe to say enable this
591 even on boards that don't use the keypad controller.
592
593 To compile this driver as a module, choose M here: the
594 module will be called twl4030_keypad.
595
596 config KEYBOARD_XTKBD
597 tristate "XT keyboard"
598 select SERIO
599 help
600 Say Y here if you want to use the old IBM PC/XT keyboard (or
601 compatible) on your system. This is only possible with a
602 parallel port keyboard adapter, you cannot connect it to the
603 keyboard port on a PC that runs Linux.
604
605 To compile this driver as a module, choose M here: the
606 module will be called xtkbd.
607
608 config KEYBOARD_W90P910
609 tristate "W90P910 Matrix Keypad support"
610 depends on ARCH_W90X900
611 select INPUT_MATRIXKMAP
612 help
613 Say Y here to enable the matrix keypad on evaluation board
614 based on W90P910.
615
616 To compile this driver as a module, choose M here: the
617 module will be called w90p910_keypad.
618
619 endif
This page took 0.055014 seconds and 5 git commands to generate.