xref: /openbmc/linux/drivers/input/keyboard/Kconfig (revision e77ff779)
1# SPDX-License-Identifier: GPL-2.0-only
2#
3# Input core configuration
4#
5menuconfig INPUT_KEYBOARD
6	bool "Keyboards"
7	default y
8	help
9	  Say Y here, and a list of supported keyboards will be displayed.
10	  This option doesn't affect the kernel.
11
12	  If unsure, say Y.
13
14if INPUT_KEYBOARD
15
16config KEYBOARD_ADC
17	tristate "ADC Ladder Buttons"
18	depends on IIO
19	select INPUT_POLLDEV
20	help
21	  This driver implements support for buttons connected
22	  to an ADC using a resistor ladder.
23
24	  Say Y here if your device has such buttons connected to an ADC.  Your
25	  board-specific setup logic must also provide a configuration data
26	  for mapping voltages to buttons.
27
28	  To compile this driver as a module, choose M here: the
29	  module will be called adc_keys.
30
31config KEYBOARD_ADP5520
32	tristate "Keypad Support for ADP5520 PMIC"
33	depends on PMIC_ADP5520
34	help
35	  This option enables support for the keypad scan matrix
36	  on Analog Devices ADP5520 PMICs.
37
38	  To compile this driver as a module, choose M here: the module will
39	  be called adp5520-keys.
40
41config KEYBOARD_ADP5588
42	tristate "ADP5588/87 I2C QWERTY Keypad and IO Expander"
43	depends on I2C
44	help
45	  Say Y here if you want to use a ADP5588/87 attached to your
46	  system I2C bus.
47
48	  To compile this driver as a module, choose M here: the
49	  module will be called adp5588-keys.
50
51config KEYBOARD_ADP5589
52	tristate "ADP5585/ADP5589 I2C QWERTY Keypad and IO Expander"
53	depends on I2C
54	help
55	  Say Y here if you want to use a ADP5585/ADP5589 attached to your
56	  system I2C bus.
57
58	  To compile this driver as a module, choose M here: the
59	  module will be called adp5589-keys.
60
61config KEYBOARD_AMIGA
62	tristate "Amiga keyboard"
63	depends on AMIGA
64	help
65	  Say Y here if you are running Linux on any AMIGA and have a keyboard
66	  attached.
67
68	  To compile this driver as a module, choose M here: the
69	  module will be called amikbd.
70
71config ATARI_KBD_CORE
72	bool
73
74config KEYBOARD_APPLESPI
75	tristate "Apple SPI keyboard and trackpad"
76	depends on ACPI && EFI
77	depends on SPI
78	depends on X86 || COMPILE_TEST
79	depends on LEDS_CLASS
80	select CRC16
81	help
82	  Say Y here if you are running Linux on any Apple MacBook8,1 or later,
83	  or any MacBookPro13,* or MacBookPro14,*.
84
85	  You will also need to enable appropriate SPI master controllers:
86	  spi_pxa2xx_platform and spi_pxa2xx_pci for MacBook8,1, and
87	  spi_pxa2xx_platform and intel_lpss_pci for the rest.
88
89	  To compile this driver as a module, choose M here: the
90	  module will be called applespi.
91
92config KEYBOARD_ATARI
93	tristate "Atari keyboard"
94	depends on ATARI
95	select ATARI_KBD_CORE
96	help
97	  Say Y here if you are running Linux on any Atari and have a keyboard
98	  attached.
99
100	  To compile this driver as a module, choose M here: the
101	  module will be called atakbd.
102
103config KEYBOARD_ATKBD
104	tristate "AT keyboard"
105	default y
106	select SERIO
107	select SERIO_LIBPS2
108	select SERIO_I8042 if ARCH_MIGHT_HAVE_PC_SERIO
109	select SERIO_GSCPS2 if GSC
110	help
111	  Say Y here if you want to use a standard AT or PS/2 keyboard. Usually
112	  you'll need this, unless you have a different type keyboard (USB, ADB
113	  or other). This also works for AT and PS/2 keyboards connected over a
114	  PS/2 to serial converter.
115
116	  If unsure, say Y.
117
118	  To compile this driver as a module, choose M here: the
119	  module will be called atkbd.
120
121config KEYBOARD_ATKBD_HP_KEYCODES
122	bool "Use HP keyboard scancodes"
123	depends on PARISC && KEYBOARD_ATKBD
124	default y
125	help
126	  Say Y here if you have a PA-RISC machine and want to use an AT or
127	  PS/2 keyboard, and your keyboard uses keycodes that are specific to
128	  PA-RISC keyboards.
129
130	  Say N if you use a standard keyboard.
131
132config KEYBOARD_ATKBD_RDI_KEYCODES
133	bool "Use PrecisionBook keyboard scancodes"
134	depends on KEYBOARD_ATKBD_HP_KEYCODES
135	default n
136	help
137	  If you have an RDI PrecisionBook, say Y here if you want to use its
138	  built-in keyboard (as opposed to an external keyboard).
139
140	  The PrecisionBook has five keys that conflict with those used by most
141	  AT and PS/2 keyboards. These are as follows:
142
143	    PrecisionBook    Standard AT or PS/2
144
145	    F1               F12
146	    Left Ctrl        Left Alt
147	    Caps Lock        Left Ctrl
148	    Right Ctrl       Caps Lock
149	    Left             102nd key (the key to the right of Left Shift)
150
151	  If you say N here, and use the PrecisionBook keyboard, then each key
152	  in the left-hand column will be interpreted as the corresponding key
153	  in the right-hand column.
154
155	  If you say Y here, and use an external keyboard, then each key in the
156	  right-hand column will be interpreted as the key shown in the
157	  left-hand column.
158
159config KEYBOARD_QT1050
160	tristate "Microchip AT42QT1050 Touch Sensor Chip"
161	depends on I2C
162	select REGMAP_I2C
163	help
164	  Say Y here if you want to use Microchip AT42QT1050 QTouch
165	  Sensor chip as input device.
166
167	  To compile this driver as a module, choose M here:
168	  the module will be called qt1050
169
170config KEYBOARD_QT1070
171       tristate "Atmel AT42QT1070 Touch Sensor Chip"
172       depends on I2C
173       help
174         Say Y here if you want to use Atmel AT42QT1070 QTouch
175         Sensor chip as input device.
176
177         To compile this driver as a module, choose M here:
178         the module will be called qt1070
179
180config KEYBOARD_QT2160
181	tristate "Atmel AT42QT2160 Touch Sensor Chip"
182	depends on I2C
183	help
184	  If you say yes here you get support for Atmel AT42QT2160 Touch
185	  Sensor chip as a keyboard input.
186
187	  This driver can also be built as a module. If so, the module
188	  will be called qt2160.
189
190config KEYBOARD_CLPS711X
191	tristate "CLPS711X Keypad support"
192	depends on OF_GPIO && (ARCH_CLPS711X || COMPILE_TEST)
193	select INPUT_MATRIXKMAP
194	select INPUT_POLLDEV
195	help
196	  Say Y here to enable the matrix keypad on the Cirrus Logic
197	  CLPS711X CPUs.
198
199	  To compile this driver as a module, choose M here: the
200	  module will be called clps711x-keypad.
201
202config KEYBOARD_DLINK_DIR685
203	tristate "D-Link DIR-685 touchkeys support"
204	depends on I2C
205	default ARCH_GEMINI
206	help
207	  If you say yes here you get support for the D-Link DIR-685
208	  touchkeys.
209
210	  To compile this driver as a module, choose M here: the
211	  module will be called dlink-dir685-touchkeys.
212
213config KEYBOARD_LKKBD
214	tristate "DECstation/VAXstation LK201/LK401 keyboard"
215	select SERIO
216	help
217	  Say Y here if you want to use a LK201 or LK401 style serial
218	  keyboard. This keyboard is also useable on PCs if you attach
219	  it with the inputattach program. The connector pinout is
220	  described within lkkbd.c.
221
222	  To compile this driver as a module, choose M here: the
223	  module will be called lkkbd.
224
225config KEYBOARD_EP93XX
226	tristate "EP93xx Matrix Keypad support"
227	depends on ARCH_EP93XX || COMPILE_TEST
228	select INPUT_MATRIXKMAP
229	help
230	  Say Y here to enable the matrix keypad on the Cirrus EP93XX.
231
232	  To compile this driver as a module, choose M here: the
233	  module will be called ep93xx_keypad.
234
235config KEYBOARD_GPIO
236	tristate "GPIO Buttons"
237	depends on GPIOLIB || COMPILE_TEST
238	help
239	  This driver implements support for buttons connected
240	  to GPIO pins of various CPUs (and some other chips).
241
242	  Say Y here if your device has buttons connected
243	  directly to such GPIO pins.  Your board-specific
244	  setup logic must also provide a platform device,
245	  with configuration data saying which GPIOs are used.
246
247	  To compile this driver as a module, choose M here: the
248	  module will be called gpio_keys.
249
250config KEYBOARD_GPIO_POLLED
251	tristate "Polled GPIO buttons"
252	depends on GPIOLIB
253	select INPUT_POLLDEV
254	help
255	  This driver implements support for buttons connected
256	  to GPIO pins that are not capable of generating interrupts.
257
258	  Say Y here if your device has buttons connected
259	  directly to such GPIO pins.  Your board-specific
260	  setup logic must also provide a platform device,
261	  with configuration data saying which GPIOs are used.
262
263	  To compile this driver as a module, choose M here: the
264	  module will be called gpio_keys_polled.
265
266config KEYBOARD_TCA6416
267	tristate "TCA6416/TCA6408A Keypad Support"
268	depends on I2C
269	help
270	  This driver implements basic keypad functionality
271	  for keys connected through TCA6416/TCA6408A IO expanders.
272
273	  Say Y here if your device has keys connected to
274	  TCA6416/TCA6408A IO expander. Your board-specific setup logic
275	  must also provide pin-mask details(of which TCA6416 pins
276	  are used for keypad).
277
278	  If enabled the entire TCA6416 device will be managed through
279	  this driver.
280
281	  To compile this driver as a module, choose M here: the
282	  module will be called tca6416_keypad.
283
284config KEYBOARD_TCA8418
285	tristate "TCA8418 Keypad Support"
286	depends on I2C
287	select INPUT_MATRIXKMAP
288	help
289	  This driver implements basic keypad functionality
290	  for keys connected through TCA8418 keypad decoder.
291
292	  Say Y here if your device has keys connected to
293	  TCA8418 keypad decoder.
294
295	  If enabled the complete TCA8418 device will be managed through
296	  this driver.
297
298	  To compile this driver as a module, choose M here: the
299	  module will be called tca8418_keypad.
300
301config KEYBOARD_MATRIX
302	tristate "GPIO driven matrix keypad support"
303	depends on GPIOLIB || COMPILE_TEST
304	select INPUT_MATRIXKMAP
305	help
306	  Enable support for GPIO driven matrix keypad.
307
308	  To compile this driver as a module, choose M here: the
309	  module will be called matrix_keypad.
310
311config KEYBOARD_HIL_OLD
312	tristate "HP HIL keyboard support (simple driver)"
313	depends on GSC || HP300
314	default y
315	help
316	  The "Human Interface Loop" is a older, 8-channel USB-like
317	  controller used in several Hewlett Packard models. This driver
318	  was adapted from the one written for m68k/hp300, and implements
319	  support for a keyboard attached to the HIL port, but not for
320	  any other types of HIL input devices like mice or tablets.
321	  However, it has been thoroughly tested and is stable.
322
323	  If you want full HIL support including support for multiple
324	  keyboards, mice, and tablets, you have to enable the
325	  "HP System Device Controller i8042 Support" in the input/serio
326	  submenu.
327
328config KEYBOARD_HIL
329	tristate "HP HIL keyboard/pointer support"
330	depends on GSC || HP300
331	default y
332	select HP_SDC
333	select HIL_MLC
334	select SERIO
335	help
336	  The "Human Interface Loop" is a older, 8-channel USB-like
337	  controller used in several Hewlett Packard models.
338	  This driver implements support for HIL-keyboards and pointing
339	  devices (mice, tablets, touchscreens) attached
340	  to your machine, so normally you should say Y here.
341
342config KEYBOARD_HP6XX
343	tristate "HP Jornada 6xx keyboard"
344	depends on SH_HP6XX
345	select INPUT_POLLDEV
346	help
347	  Say Y here if you have a HP Jornada 620/660/680/690 and want to
348	  support the built-in keyboard.
349
350	  To compile this driver as a module, choose M here: the
351	  module will be called jornada680_kbd.
352
353config KEYBOARD_HP7XX
354	tristate "HP Jornada 7xx keyboard"
355	depends on SA1100_JORNADA720_SSP && SA1100_SSP
356	help
357	  Say Y here if you have a HP Jornada 710/720/728 and want to
358	  support the built-in keyboard.
359
360	  To compile this driver as a module, choose M here: the
361	  module will be called jornada720_kbd.
362
363config KEYBOARD_LM8323
364	tristate "LM8323 keypad chip"
365	depends on I2C
366	depends on LEDS_CLASS
367	help
368	  If you say yes here you get support for the National Semiconductor
369	  LM8323 keypad controller.
370
371	  To compile this driver as a module, choose M here: the
372	  module will be called lm8323.
373
374config KEYBOARD_LM8333
375	tristate "LM8333 keypad chip"
376	depends on I2C
377	select INPUT_MATRIXKMAP
378	help
379	  If you say yes here you get support for the National Semiconductor
380	  LM8333 keypad controller.
381
382	  To compile this driver as a module, choose M here: the
383	  module will be called lm8333.
384
385config KEYBOARD_LOCOMO
386	tristate "LoCoMo Keyboard Support"
387	depends on SHARP_LOCOMO
388	help
389	  Say Y here if you are running Linux on a Sharp Zaurus Collie or Poodle based PDA
390
391	  To compile this driver as a module, choose M here: the
392	  module will be called locomokbd.
393
394config KEYBOARD_LPC32XX
395	tristate "LPC32XX matrix key scanner support"
396	depends on ARCH_LPC32XX && OF
397	select INPUT_MATRIXKMAP
398	help
399	  Say Y here if you want to use NXP LPC32XX SoC key scanner interface,
400	  connected to a key matrix.
401
402	  To compile this driver as a module, choose M here: the
403	  module will be called lpc32xx-keys.
404
405config KEYBOARD_MAPLE
406	tristate "Maple bus keyboard"
407	depends on SH_DREAMCAST && MAPLE
408	help
409	  Say Y here if you have a Dreamcast console running Linux and have
410	  a keyboard attached to its Maple bus.
411
412	  To compile this driver as a module, choose M here: the
413	  module will be called maple_keyb.
414
415config KEYBOARD_MAX7359
416	tristate "Maxim MAX7359 Key Switch Controller"
417	select INPUT_MATRIXKMAP
418	depends on I2C
419	help
420	  If you say yes here you get support for the Maxim MAX7359 Key
421	  Switch Controller chip. This providers microprocessors with
422	  management of up to 64 key switches
423
424	  To compile this driver as a module, choose M here: the
425	  module will be called max7359_keypad.
426
427config KEYBOARD_MCS
428	tristate "MELFAS MCS Touchkey"
429	depends on I2C
430	help
431	  Say Y here if you have the MELFAS MCS5000/5080 touchkey controller
432	  chip in your system.
433
434	  If unsure, say N.
435
436	  To compile this driver as a module, choose M here: the
437	  module will be called mcs_touchkey.
438
439config KEYBOARD_MPR121
440	tristate "Freescale MPR121 Touchkey"
441	depends on I2C
442	help
443	  Say Y here if you have Freescale MPR121 touchkey controller
444	  chip in your system.
445
446	  If unsure, say N.
447
448	  To compile this driver as a module, choose M here: the
449	  module will be called mpr121_touchkey.
450
451config KEYBOARD_SNVS_PWRKEY
452	tristate "IMX SNVS Power Key Driver"
453	depends on ARCH_MXC || COMPILE_TEST
454	depends on OF
455	help
456	  This is the snvs powerkey driver for the Freescale i.MX application
457	  processors that are newer than i.MX6 SX.
458
459	  To compile this driver as a module, choose M here; the
460	  module will be called snvs_pwrkey.
461
462config KEYBOARD_IMX
463	tristate "IMX keypad support"
464	depends on ARCH_MXC
465	select INPUT_MATRIXKMAP
466	help
467	  Enable support for IMX keypad port.
468
469	  To compile this driver as a module, choose M here: the
470	  module will be called imx_keypad.
471
472config KEYBOARD_NEWTON
473	tristate "Newton keyboard"
474	select SERIO
475	help
476	  Say Y here if you have a Newton keyboard on a serial port.
477
478	  To compile this driver as a module, choose M here: the
479	  module will be called newtonkbd.
480
481config KEYBOARD_NOMADIK
482	tristate "ST-Ericsson Nomadik SKE keyboard"
483	depends on (ARCH_NOMADIK || ARCH_U8500)
484	select INPUT_MATRIXKMAP
485	help
486	  Say Y here if you want to use a keypad provided on the SKE controller
487	  used on the Ux500 and Nomadik platforms
488
489	  To compile this driver as a module, choose M here: the
490	  module will be called nmk-ske-keypad.
491
492config KEYBOARD_NSPIRE
493	tristate "TI-NSPIRE built-in keyboard"
494	depends on ARCH_NSPIRE && OF
495	select INPUT_MATRIXKMAP
496	help
497	  Say Y here if you want to use the built-in keypad on TI-NSPIRE.
498
499	  To compile this driver as a module, choose M here: the
500	  module will be called nspire-keypad.
501
502config KEYBOARD_TEGRA
503	tristate "NVIDIA Tegra internal matrix keyboard controller support"
504	depends on ARCH_TEGRA && OF
505	select INPUT_MATRIXKMAP
506	help
507	  Say Y here if you want to use a matrix keyboard connected directly
508	  to the internal keyboard controller on Tegra SoCs.
509
510	  To compile this driver as a module, choose M here: the
511	  module will be called tegra-kbc.
512
513config KEYBOARD_OPENCORES
514	tristate "OpenCores Keyboard Controller"
515	depends on HAS_IOMEM
516	help
517	  Say Y here if you want to use the OpenCores Keyboard Controller
518	  http://www.opencores.org/project,keyboardcontroller
519
520	  To compile this driver as a module, choose M here; the
521	  module will be called opencores-kbd.
522
523config KEYBOARD_PXA27x
524	tristate "PXA27x/PXA3xx keypad support"
525	depends on PXA27x || PXA3xx || ARCH_MMP
526	select INPUT_MATRIXKMAP
527	help
528	  Enable support for PXA27x/PXA3xx keypad controller.
529
530	  To compile this driver as a module, choose M here: the
531	  module will be called pxa27x_keypad.
532
533config KEYBOARD_PXA930_ROTARY
534	tristate "PXA930/PXA935 Enhanced Rotary Controller Support"
535	depends on CPU_PXA930 || CPU_PXA935
536	help
537	  Enable support for PXA930/PXA935 Enhanced Rotary Controller.
538
539	  To compile this driver as a module, choose M here: the
540	  module will be called pxa930_rotary.
541
542config KEYBOARD_PMIC8XXX
543	tristate "Qualcomm PMIC8XXX keypad support"
544	depends on MFD_PM8XXX
545	select INPUT_MATRIXKMAP
546	help
547	  Say Y here if you want to enable the driver for the PMIC8XXX
548	  keypad provided as a reference design from Qualcomm. This is intended
549	  to support upto 18x8 matrix based keypad design.
550
551	  To compile this driver as a module, choose M here: the module will
552	  be called pmic8xxx-keypad.
553
554config KEYBOARD_SAMSUNG
555	tristate "Samsung keypad support"
556	depends on HAVE_CLK
557	select INPUT_MATRIXKMAP
558	help
559	  Say Y here if you want to use the keypad on your Samsung mobile
560	  device.
561
562	  To compile this driver as a module, choose M here: the
563	  module will be called samsung-keypad.
564
565config KEYBOARD_GOLDFISH_EVENTS
566	depends on GOLDFISH || COMPILE_TEST
567	tristate "Generic Input Event device for Goldfish"
568	help
569	  Say Y here to get an input event device for the Goldfish virtual
570	  device emulator.
571
572	  To compile this driver as a module, choose M here: the
573	  module will be called goldfish-events.
574
575config KEYBOARD_STOWAWAY
576	tristate "Stowaway keyboard"
577	select SERIO
578	help
579	  Say Y here if you have a Stowaway keyboard on a serial port.
580	  Stowaway compatible keyboards like Dicota Input-PDA keyboard
581	  are also supported by this driver.
582
583	  To compile this driver as a module, choose M here: the
584	  module will be called stowaway.
585
586config KEYBOARD_ST_KEYSCAN
587	tristate "STMicroelectronics keyscan support"
588	depends on ARCH_STI || COMPILE_TEST
589	select INPUT_MATRIXKMAP
590	help
591	  Say Y here if you want to use a keypad attached to the keyscan block
592	  on some STMicroelectronics SoC devices.
593
594	  To compile this driver as a module, choose M here: the
595	  module will be called st-keyscan.
596
597config KEYBOARD_SUNKBD
598	tristate "Sun Type 4 and Type 5 keyboard"
599	select SERIO
600	help
601	  Say Y here if you want to use a Sun Type 4 or Type 5 keyboard,
602	  connected either to the Sun keyboard connector or to an serial
603	  (RS-232) port via a simple adapter.
604
605	  To compile this driver as a module, choose M here: the
606	  module will be called sunkbd.
607
608config KEYBOARD_SH_KEYSC
609	tristate "SuperH KEYSC keypad support"
610	depends on ARCH_SHMOBILE || COMPILE_TEST
611	help
612	  Say Y here if you want to use a keypad attached to the KEYSC block
613	  on SuperH processors such as sh7722 and sh7343.
614
615	  To compile this driver as a module, choose M here: the
616	  module will be called sh_keysc.
617
618config KEYBOARD_STMPE
619	tristate "STMPE keypad support"
620	depends on MFD_STMPE
621	depends on OF
622	select INPUT_MATRIXKMAP
623	help
624	  Say Y here if you want to use the keypad controller on STMPE I/O
625	  expanders.
626
627	  To compile this driver as a module, choose M here: the module will be
628	  called stmpe-keypad.
629
630config KEYBOARD_SUN4I_LRADC
631	tristate "Allwinner sun4i low res adc attached tablet keys support"
632	depends on ARCH_SUNXI
633	help
634	  This selects support for the Allwinner low res adc attached tablet
635	  keys found on Allwinner sunxi SoCs.
636
637	  To compile this driver as a module, choose M here: the
638	  module will be called sun4i-lradc-keys.
639
640config KEYBOARD_DAVINCI
641	tristate "TI DaVinci Key Scan"
642	depends on ARCH_DAVINCI_DM365
643	help
644	  Say Y to enable keypad module support for the TI DaVinci
645	  platforms (DM365).
646
647	  To compile this driver as a module, choose M here: the
648	  module will be called davinci_keyscan.
649
650config KEYBOARD_IPAQ_MICRO
651	tristate "Buttons on Micro SoC (iPaq h3100,h3600,h3700)"
652	depends on MFD_IPAQ_MICRO
653	help
654	  Say Y to enable support for the buttons attached to
655	  Micro peripheral controller on iPAQ h3100/h3600/h3700
656
657	  To compile this driver as a module, choose M here: the
658	  module will be called ipaq-micro-keys.
659
660config KEYBOARD_OMAP
661	tristate "TI OMAP keypad support"
662	depends on ARCH_OMAP1
663	select INPUT_MATRIXKMAP
664	help
665	  Say Y here if you want to use the OMAP keypad.
666
667	  To compile this driver as a module, choose M here: the
668	  module will be called omap-keypad.
669
670config KEYBOARD_OMAP4
671	tristate "TI OMAP4+ keypad support"
672	depends on OF || ARCH_OMAP2PLUS
673	select INPUT_MATRIXKMAP
674	help
675	  Say Y here if you want to use the OMAP4+ keypad.
676
677	  To compile this driver as a module, choose M here: the
678	  module will be called omap4-keypad.
679
680config KEYBOARD_SPEAR
681	tristate "ST SPEAR keyboard support"
682	depends on PLAT_SPEAR
683	select INPUT_MATRIXKMAP
684	help
685	  Say Y here if you want to use the SPEAR keyboard.
686
687	  To compile this driver as a module, choose M here: the
688	  module will be called spear-keboard.
689
690config KEYBOARD_TC3589X
691	tristate "TC3589X Keypad support"
692	depends on MFD_TC3589X
693	select INPUT_MATRIXKMAP
694	help
695	  Say Y here if you want to use the keypad controller on
696	  TC35892/3 I/O expander.
697
698	  To compile this driver as a module, choose M here: the
699	  module will be called tc3589x-keypad.
700
701config KEYBOARD_TM2_TOUCHKEY
702	tristate "TM2 touchkey support"
703	depends on I2C
704	depends on LEDS_CLASS
705	help
706	  Say Y here to enable device driver for tm2-touchkey with
707	  LED control for the Exynos5433 TM2 board.
708
709	  To compile this driver as a module, choose M here.
710	  module will be called tm2-touchkey.
711
712config KEYBOARD_TWL4030
713	tristate "TI TWL4030/TWL5030/TPS659x0 keypad support"
714	depends on TWL4030_CORE
715	select INPUT_MATRIXKMAP
716	help
717	  Say Y here if your board use the keypad controller on
718	  TWL4030 family chips.  It's safe to say enable this
719	  even on boards that don't use the keypad controller.
720
721	  To compile this driver as a module, choose M here: the
722	  module will be called twl4030_keypad.
723
724config KEYBOARD_XTKBD
725	tristate "XT keyboard"
726	select SERIO
727	help
728	  Say Y here if you want to use the old IBM PC/XT keyboard (or
729	  compatible) on your system. This is only possible with a
730	  parallel port keyboard adapter, you cannot connect it to the
731	  keyboard port on a PC that runs Linux.
732
733	  To compile this driver as a module, choose M here: the
734	  module will be called xtkbd.
735
736config KEYBOARD_W90P910
737	tristate "W90P910 Matrix Keypad support"
738	depends on ARCH_W90X900
739	select INPUT_MATRIXKMAP
740	help
741	  Say Y here to enable the matrix keypad on evaluation board
742	  based on W90P910.
743
744	  To compile this driver as a module, choose M here: the
745	  module will be called w90p910_keypad.
746
747config KEYBOARD_CROS_EC
748	tristate "ChromeOS EC keyboard"
749	select INPUT_MATRIXKMAP
750	depends on MFD_CROS_EC
751	help
752	  Say Y here to enable the matrix keyboard used by ChromeOS devices
753	  and implemented on the ChromeOS EC. You must enable one bus option
754	  (CROS_EC_I2C or CROS_EC_SPI) to use this.
755
756	  To compile this driver as a module, choose M here: the
757	  module will be called cros_ec_keyb.
758
759config KEYBOARD_CAP11XX
760	tristate "Microchip CAP11XX based touch sensors"
761	depends on OF && I2C
762	select REGMAP_I2C
763	help
764	  Say Y here to enable the CAP11XX touch sensor driver.
765
766	  To compile this driver as a module, choose M here: the
767	  module will be called cap11xx.
768
769config KEYBOARD_BCM
770	tristate "Broadcom keypad driver"
771	depends on OF && HAVE_CLK
772	select INPUT_MATRIXKMAP
773	default ARCH_BCM_CYGNUS
774	help
775	  Say Y here if you want to use Broadcom keypad.
776
777	  To compile this driver as a module, choose M here: the
778	  module will be called bcm-keypad.
779
780config KEYBOARD_MTK_PMIC
781	tristate "MediaTek PMIC keys support"
782	depends on MFD_MT6397
783	help
784	  Say Y here if you want to use the pmic keys (powerkey/homekey).
785
786	  To compile this driver as a module, choose M here: the
787	  module will be called pmic-keys.
788
789endif
790