xref: /openbmc/linux/drivers/input/keyboard/Kconfig (revision cd5d5810)
1#
2# Input core configuration
3#
4menuconfig 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
13if INPUT_KEYBOARD
14
15config 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
25config 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
35config 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
45config 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
55config ATARI_KBD_CORE
56	bool
57
58config 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
69config 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
87config 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
98config 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
125config 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
135config KEYBOARD_QT2160
136	tristate "Atmel AT42QT2160 Touch Sensor Chip"
137	depends on I2C
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
145config 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
154config 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
166config 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
176config KEYBOARD_GPIO
177	tristate "GPIO Buttons"
178	depends on GPIOLIB
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
191config KEYBOARD_GPIO_POLLED
192	tristate "Polled GPIO buttons"
193	depends on GPIOLIB
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
207config 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
225config 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
242config KEYBOARD_MATRIX
243	tristate "GPIO driven matrix keypad support"
244	depends on GPIOLIB
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
252config 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
269config 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
283config 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
294config 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
304config 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
315config 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
326config 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
335config KEYBOARD_LPC32XX
336	tristate "LPC32XX matrix key scanner support"
337	depends on ARCH_LPC32XX && OF
338	select INPUT_MATRIXKMAP
339	help
340	  Say Y here if you want to use NXP LPC32XX SoC key scanner interface,
341	  connected to a key matrix.
342
343	  To compile this driver as a module, choose M here: the
344	  module will be called lpc32xx-keys.
345
346config KEYBOARD_MAPLE
347	tristate "Maple bus keyboard"
348	depends on SH_DREAMCAST && MAPLE
349	help
350	  Say Y here if you have a Dreamcast console running Linux and have
351	  a keyboard attached to its Maple bus.
352
353	  To compile this driver as a module, choose M here: the
354	  module will be called maple_keyb.
355
356config KEYBOARD_MAX7359
357	tristate "Maxim MAX7359 Key Switch Controller"
358	depends on I2C
359	help
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
363
364	  To compile this driver as a module, choose M here: the
365	  module will be called max7359_keypad.
366
367config KEYBOARD_MCS
368	tristate "MELFAS MCS Touchkey"
369	depends on I2C
370	help
371	  Say Y here if you have the MELFAS MCS5000/5080 touchkey controller
372	  chip in your system.
373
374	  If unsure, say N.
375
376	  To compile this driver as a module, choose M here: the
377	  module will be called mcs_touchkey.
378
379config KEYBOARD_MPR121
380	tristate "Freescale MPR121 Touchkey"
381	depends on I2C
382	help
383	  Say Y here if you have Freescale MPR121 touchkey controller
384	  chip in your system.
385
386	  If unsure, say N.
387
388	  To compile this driver as a module, choose M here: the
389	  module will be called mpr121_touchkey.
390
391config KEYBOARD_IMX
392	tristate "IMX keypad support"
393	depends on ARCH_MXC
394	select INPUT_MATRIXKMAP
395	help
396	  Enable support for IMX keypad port.
397
398	  To compile this driver as a module, choose M here: the
399	  module will be called imx_keypad.
400
401config KEYBOARD_NEWTON
402	tristate "Newton keyboard"
403	select SERIO
404	help
405	  Say Y here if you have a Newton keyboard on a serial port.
406
407	  To compile this driver as a module, choose M here: the
408	  module will be called newtonkbd.
409
410config KEYBOARD_NOMADIK
411	tristate "ST-Ericsson Nomadik SKE keyboard"
412	depends on (ARCH_NOMADIK || ARCH_U8500)
413	select INPUT_MATRIXKMAP
414	help
415	  Say Y here if you want to use a keypad provided on the SKE controller
416	  used on the Ux500 and Nomadik platforms
417
418	  To compile this driver as a module, choose M here: the
419	  module will be called nmk-ske-keypad.
420
421config KEYBOARD_NSPIRE
422	tristate "TI-NSPIRE built-in keyboard"
423	depends on ARCH_NSPIRE && OF
424	select INPUT_MATRIXKMAP
425	help
426	  Say Y here if you want to use the built-in keypad on TI-NSPIRE.
427
428	  To compile this driver as a module, choose M here: the
429	  module will be called nspire-keypad.
430
431config KEYBOARD_TEGRA
432	tristate "NVIDIA Tegra internal matrix keyboard controller support"
433	depends on ARCH_TEGRA && OF
434	select INPUT_MATRIXKMAP
435	help
436	  Say Y here if you want to use a matrix keyboard connected directly
437	  to the internal keyboard controller on Tegra SoCs.
438
439	  To compile this driver as a module, choose M here: the
440	  module will be called tegra-kbc.
441
442config KEYBOARD_OPENCORES
443	tristate "OpenCores Keyboard Controller"
444	depends on HAS_IOMEM
445	help
446	  Say Y here if you want to use the OpenCores Keyboard Controller
447	  http://www.opencores.org/project,keyboardcontroller
448
449	  To compile this driver as a module, choose M here; the
450	  module will be called opencores-kbd.
451
452config KEYBOARD_PXA27x
453	tristate "PXA27x/PXA3xx keypad support"
454	depends on PXA27x || PXA3xx || ARCH_MMP
455	select INPUT_MATRIXKMAP
456	help
457	  Enable support for PXA27x/PXA3xx keypad controller.
458
459	  To compile this driver as a module, choose M here: the
460	  module will be called pxa27x_keypad.
461
462config KEYBOARD_PXA930_ROTARY
463	tristate "PXA930/PXA935 Enhanced Rotary Controller Support"
464	depends on CPU_PXA930 || CPU_PXA935
465	help
466	  Enable support for PXA930/PXA935 Enhanced Rotary Controller.
467
468	  To compile this driver as a module, choose M here: the
469	  module will be called pxa930_rotary.
470
471config KEYBOARD_PMIC8XXX
472	tristate "Qualcomm PMIC8XXX keypad support"
473	depends on MFD_PM8XXX
474	select INPUT_MATRIXKMAP
475	help
476	  Say Y here if you want to enable the driver for the PMIC8XXX
477	  keypad provided as a reference design from Qualcomm. This is intended
478	  to support upto 18x8 matrix based keypad design.
479
480	  To compile this driver as a module, choose M here: the module will
481	  be called pmic8xxx-keypad.
482
483config KEYBOARD_SAMSUNG
484	tristate "Samsung keypad support"
485	depends on HAVE_CLK
486	select INPUT_MATRIXKMAP
487	help
488	  Say Y here if you want to use the keypad on your Samsung mobile
489	  device.
490
491	  To compile this driver as a module, choose M here: the
492	  module will be called samsung-keypad.
493
494config KEYBOARD_GOLDFISH_EVENTS
495	depends on GOLDFISH
496	tristate "Generic Input Event device for Goldfish"
497	help
498	  Say Y here to get an input event device for the Goldfish virtual
499	  device emulator.
500
501	  To compile this driver as a module, choose M here: the
502	  module will be called goldfish-events.
503
504config KEYBOARD_STOWAWAY
505	tristate "Stowaway keyboard"
506	select SERIO
507	help
508	  Say Y here if you have a Stowaway keyboard on a serial port.
509	  Stowaway compatible keyboards like Dicota Input-PDA keyboard
510	  are also supported by this driver.
511
512	  To compile this driver as a module, choose M here: the
513	  module will be called stowaway.
514
515config KEYBOARD_SUNKBD
516	tristate "Sun Type 4 and Type 5 keyboard"
517	select SERIO
518	help
519	  Say Y here if you want to use a Sun Type 4 or Type 5 keyboard,
520	  connected either to the Sun keyboard connector or to an serial
521	  (RS-232) port via a simple adapter.
522
523	  To compile this driver as a module, choose M here: the
524	  module will be called sunkbd.
525
526config KEYBOARD_SH_KEYSC
527	tristate "SuperH KEYSC keypad support"
528	depends on SUPERH || ARCH_SHMOBILE
529	help
530	  Say Y here if you want to use a keypad attached to the KEYSC block
531	  on SuperH processors such as sh7722 and sh7343.
532
533	  To compile this driver as a module, choose M here: the
534	  module will be called sh_keysc.
535
536config KEYBOARD_STMPE
537	tristate "STMPE keypad support"
538	depends on MFD_STMPE
539	select INPUT_MATRIXKMAP
540	help
541	  Say Y here if you want to use the keypad controller on STMPE I/O
542	  expanders.
543
544	  To compile this driver as a module, choose M here: the module will be
545	  called stmpe-keypad.
546
547config KEYBOARD_DAVINCI
548	tristate "TI DaVinci Key Scan"
549	depends on ARCH_DAVINCI_DM365
550	help
551	  Say Y to enable keypad module support for the TI DaVinci
552	  platforms (DM365).
553
554	  To compile this driver as a module, choose M here: the
555	  module will be called davinci_keyscan.
556
557config KEYBOARD_OMAP
558	tristate "TI OMAP keypad support"
559	depends on ARCH_OMAP1
560	select INPUT_MATRIXKMAP
561	help
562	  Say Y here if you want to use the OMAP keypad.
563
564	  To compile this driver as a module, choose M here: the
565	  module will be called omap-keypad.
566
567config KEYBOARD_OMAP4
568	tristate "TI OMAP4+ keypad support"
569	depends on ARCH_OMAP2PLUS
570	select INPUT_MATRIXKMAP
571	help
572	  Say Y here if you want to use the OMAP4+ keypad.
573
574	  To compile this driver as a module, choose M here: the
575	  module will be called omap4-keypad.
576
577config KEYBOARD_SPEAR
578	tristate "ST SPEAR keyboard support"
579	depends on PLAT_SPEAR
580	select INPUT_MATRIXKMAP
581	help
582	  Say Y here if you want to use the SPEAR keyboard.
583
584	  To compile this driver as a module, choose M here: the
585	  module will be called spear-keboard.
586
587config KEYBOARD_TC3589X
588	tristate "TC3589X Keypad support"
589	depends on MFD_TC3589X
590	select INPUT_MATRIXKMAP
591	help
592	  Say Y here if you want to use the keypad controller on
593	  TC35892/3 I/O expander.
594
595	  To compile this driver as a module, choose M here: the
596	  module will be called tc3589x-keypad.
597
598config KEYBOARD_TNETV107X
599	tristate "TI TNETV107X keypad support"
600	depends on ARCH_DAVINCI_TNETV107X
601	select INPUT_MATRIXKMAP
602	help
603	  Say Y here if you want to use the TNETV107X keypad.
604
605	  To compile this driver as a module, choose M here: the
606	  module will be called tnetv107x-keypad.
607
608config KEYBOARD_TWL4030
609	tristate "TI TWL4030/TWL5030/TPS659x0 keypad support"
610	depends on TWL4030_CORE
611	select INPUT_MATRIXKMAP
612	help
613	  Say Y here if your board use the keypad controller on
614	  TWL4030 family chips.  It's safe to say enable this
615	  even on boards that don't use the keypad controller.
616
617	  To compile this driver as a module, choose M here: the
618	  module will be called twl4030_keypad.
619
620config KEYBOARD_XTKBD
621	tristate "XT keyboard"
622	select SERIO
623	help
624	  Say Y here if you want to use the old IBM PC/XT keyboard (or
625	  compatible) on your system. This is only possible with a
626	  parallel port keyboard adapter, you cannot connect it to the
627	  keyboard port on a PC that runs Linux.
628
629	  To compile this driver as a module, choose M here: the
630	  module will be called xtkbd.
631
632config KEYBOARD_W90P910
633	tristate "W90P910 Matrix Keypad support"
634	depends on ARCH_W90X900
635	select INPUT_MATRIXKMAP
636	help
637	  Say Y here to enable the matrix keypad on evaluation board
638	  based on W90P910.
639
640	  To compile this driver as a module, choose M here: the
641	  module will be called w90p910_keypad.
642
643config KEYBOARD_CROS_EC
644	tristate "ChromeOS EC keyboard"
645	select INPUT_MATRIXKMAP
646	depends on MFD_CROS_EC
647	help
648	  Say Y here to enable the matrix keyboard used by ChromeOS devices
649	  and implemented on the ChromeOS EC. You must enable one bus option
650	  (MFD_CROS_EC_I2C or MFD_CROS_EC_SPI) to use this.
651
652	  To compile this driver as a module, choose M here: the
653	  module will be called cros_ec_keyb.
654
655endif
656