xref: /linux/drivers/input/keyboard/Kconfig (revision 7a5f1cd22d47f8ca4b760b6334378ae42c1bd24b)
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	help
20	  This driver implements support for buttons connected
21	  to an ADC using a resistor ladder.
22
23	  Say Y here if your device has such buttons connected to an ADC.  Your
24	  board-specific setup logic must also provide a configuration data
25	  for mapping voltages to buttons.
26
27	  To compile this driver as a module, choose M here: the
28	  module will be called adc_keys.
29
30config KEYBOARD_ADP5520
31	tristate "Keypad Support for ADP5520 PMIC"
32	depends on PMIC_ADP5520
33	help
34	  This option enables support for the keypad scan matrix
35	  on Analog Devices ADP5520 PMICs.
36
37	  To compile this driver as a module, choose M here: the module will
38	  be called adp5520-keys.
39
40config KEYBOARD_ADP5585
41	tristate "ADP558x keypad support"
42	depends on MFD_ADP5585
43	select INPUT_MATRIXKMAP
44	help
45	  This option enables support for the KEYPAD function found in the Analog
46	  Devices ADP5585 and similar devices.
47
48	  To compile this driver as a module, choose M here: the
49	  module will be called adp5585-keys.
50
51config KEYBOARD_ADP5588
52	tristate "ADP5588/87 I2C QWERTY Keypad and IO Expander"
53	depends on I2C
54	select GPIOLIB
55	select GPIOLIB_IRQCHIP
56	select INPUT_MATRIXKMAP
57	help
58	  Say Y here if you want to use a ADP5588/87 attached to your
59	  system I2C bus.
60
61	  To compile this driver as a module, choose M here: the
62	  module will be called adp5588-keys.
63
64config KEYBOARD_AMIGA
65	tristate "Amiga keyboard"
66	depends on AMIGA
67	help
68	  Say Y here if you are running Linux on any AMIGA and have a keyboard
69	  attached.
70
71	  To compile this driver as a module, choose M here: the
72	  module will be called amikbd.
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	select INPUT_VIVALDIFMAP
111	help
112	  Say Y here if you want to use a standard AT or PS/2 keyboard. Usually
113	  you'll need this, unless you have a different type keyboard (USB, ADB
114	  or other). This also works for AT and PS/2 keyboards connected over a
115	  PS/2 to serial converter.
116
117	  If unsure, say Y.
118
119	  To compile this driver as a module, choose M here: the
120	  module will be called atkbd.
121
122config KEYBOARD_ATKBD_HP_KEYCODES
123	bool "Use HP keyboard scancodes"
124	depends on PARISC && KEYBOARD_ATKBD
125	default y
126	help
127	  Say Y here if you have a PA-RISC machine and want to use an AT or
128	  PS/2 keyboard, and your keyboard uses keycodes that are specific to
129	  PA-RISC keyboards.
130
131	  Say N if you use a standard keyboard.
132
133config KEYBOARD_ATKBD_RDI_KEYCODES
134	bool "Use PrecisionBook keyboard scancodes"
135	depends on KEYBOARD_ATKBD_HP_KEYCODES
136	default n
137	help
138	  If you have an RDI PrecisionBook, say Y here if you want to use its
139	  built-in keyboard (as opposed to an external keyboard).
140
141	  The PrecisionBook has five keys that conflict with those used by most
142	  AT and PS/2 keyboards. These are as follows:
143
144	    PrecisionBook    Standard AT or PS/2
145
146	    F1               F12
147	    Left Ctrl        Left Alt
148	    Caps Lock        Left Ctrl
149	    Right Ctrl       Caps Lock
150	    Left             102nd key (the key to the right of Left Shift)
151
152	  If you say N here, and use the PrecisionBook keyboard, then each key
153	  in the left-hand column will be interpreted as the corresponding key
154	  in the right-hand column.
155
156	  If you say Y here, and use an external keyboard, then each key in the
157	  right-hand column will be interpreted as the key shown in the
158	  left-hand column.
159
160config KEYBOARD_QT1050
161	tristate "Microchip AT42QT1050 Touch Sensor Chip"
162	depends on I2C
163	select REGMAP_I2C
164	help
165	  Say Y here if you want to use Microchip AT42QT1050 QTouch
166	  Sensor chip as input device.
167
168	  To compile this driver as a module, choose M here:
169	  the module will be called qt1050
170
171config KEYBOARD_QT1070
172	tristate "Atmel AT42QT1070 Touch Sensor Chip"
173	depends on I2C
174	help
175	  Say Y here if you want to use Atmel AT42QT1070 QTouch
176	  Sensor chip as input device.
177
178	  To compile this driver as a module, choose M here:
179	  the module will be called qt1070
180
181config KEYBOARD_QT2160
182	tristate "Atmel AT42QT2160 Touch Sensor Chip"
183	depends on I2C
184	help
185	  If you say yes here you get support for Atmel AT42QT2160 Touch
186	  Sensor chip as a keyboard input.
187
188	  This driver can also be built as a module. If so, the module
189	  will be called qt2160.
190
191config KEYBOARD_CLPS711X
192	tristate "CLPS711X Keypad support"
193	depends on ARCH_CLPS711X || COMPILE_TEST
194	select INPUT_MATRIXKMAP
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 usable 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	help
254	  This driver implements support for buttons connected
255	  to GPIO pins that are not capable of generating interrupts.
256
257	  Say Y here if your device has buttons connected
258	  directly to such GPIO pins.  Your board-specific
259	  setup logic must also provide a platform device,
260	  with configuration data saying which GPIOs are used.
261
262	  To compile this driver as a module, choose M here: the
263	  module will be called gpio_keys_polled.
264
265config KEYBOARD_TCA8418
266	tristate "TCA8418 Keypad Support"
267	depends on I2C
268	select INPUT_MATRIXKMAP
269	help
270	  This driver implements basic keypad functionality
271	  for keys connected through TCA8418 keypad decoder.
272
273	  Say Y here if your device has keys connected to
274	  TCA8418 keypad decoder.
275
276	  If enabled the complete TCA8418 device will be managed through
277	  this driver.
278
279	  To compile this driver as a module, choose M here: the
280	  module will be called tca8418_keypad.
281
282config KEYBOARD_MATRIX
283	tristate "GPIO driven matrix keypad support"
284	depends on GPIOLIB || COMPILE_TEST
285	select INPUT_MATRIXKMAP
286	help
287	  Enable support for GPIO driven matrix keypad.
288
289	  To compile this driver as a module, choose M here: the
290	  module will be called matrix_keypad.
291
292config KEYBOARD_CHARLIEPLEX
293	tristate "GPIO driven charlieplex keypad support"
294	depends on GPIOLIB || COMPILE_TEST
295	select INPUT_MATRIXKMAP
296	help
297	  Enable support for GPIO driven charlieplex keypad. A charlieplex
298	  keypad allows to use fewer GPIO lines to interface to key switches.
299	  For example, an N lines charlieplex keypad can be used to interface
300	  to N^2-N different key switches. However, this type of keypad
301	  cannot detect more than one key press at a time.
302
303	  To compile this driver as a module, choose M here: the
304	  module will be called charlieplex_keypad.
305
306config KEYBOARD_HIL_OLD
307	tristate "HP HIL keyboard support (simple driver)"
308	depends on GSC || HP300
309	default y
310	help
311	  The "Human Interface Loop" is a older, 8-channel USB-like
312	  controller used in several Hewlett Packard models. This driver
313	  was adapted from the one written for m68k/hp300, and implements
314	  support for a keyboard attached to the HIL port, but not for
315	  any other types of HIL input devices like mice or tablets.
316	  However, it has been thoroughly tested and is stable.
317
318	  If you want full HIL support including support for multiple
319	  keyboards, mice, and tablets, you have to enable the
320	  "HP System Device Controller i8042 Support" in the input/serio
321	  submenu.
322
323config KEYBOARD_HIL
324	tristate "HP HIL keyboard/pointer support"
325	depends on GSC || HP300
326	default y
327	select HP_SDC
328	select HIL_MLC
329	select SERIO
330	help
331	  The "Human Interface Loop" is a older, 8-channel USB-like
332	  controller used in several Hewlett Packard models.
333	  This driver implements support for HIL-keyboards and pointing
334	  devices (mice, tablets, touchscreens) attached
335	  to your machine, so normally you should say Y here.
336
337config KEYBOARD_HP6XX
338	tristate "HP Jornada 6xx keyboard"
339	depends on SH_HP6XX
340	help
341	  Say Y here if you have a HP Jornada 620/660/680/690 and want to
342	  support the built-in keyboard.
343
344	  To compile this driver as a module, choose M here: the
345	  module will be called jornada680_kbd.
346
347config KEYBOARD_HP7XX
348	tristate "HP Jornada 7xx keyboard"
349	depends on SA1100_JORNADA720_SSP && SA1100_SSP
350	help
351	  Say Y here if you have a HP Jornada 710/720/728 and want to
352	  support the built-in keyboard.
353
354	  To compile this driver as a module, choose M here: the
355	  module will be called jornada720_kbd.
356
357config KEYBOARD_LM8323
358	tristate "LM8323 keypad chip"
359	depends on I2C
360	depends on LEDS_CLASS
361	help
362	  If you say yes here you get support for the National Semiconductor
363	  LM8323 keypad controller.
364
365	  To compile this driver as a module, choose M here: the
366	  module will be called lm8323.
367
368config KEYBOARD_LM8333
369	tristate "LM8333 keypad chip"
370	depends on I2C
371	select INPUT_MATRIXKMAP
372	help
373	  If you say yes here you get support for the National Semiconductor
374	  LM8333 keypad controller.
375
376	  To compile this driver as a module, choose M here: the
377	  module will be called lm8333.
378
379config KEYBOARD_LOCOMO
380	tristate "LoCoMo Keyboard Support"
381	depends on SHARP_LOCOMO
382	help
383	  Say Y here if you are running Linux on a Sharp Zaurus Collie or Poodle based PDA
384
385	  To compile this driver as a module, choose M here: the
386	  module will be called locomokbd.
387
388config KEYBOARD_LPC32XX
389	tristate "LPC32XX matrix key scanner support"
390	depends on (ARCH_LPC32XX && OF) || COMPILE_TEST
391	select INPUT_MATRIXKMAP
392	help
393	  Say Y here if you want to use NXP LPC32XX SoC key scanner interface,
394	  connected to a key matrix.
395
396	  To compile this driver as a module, choose M here: the
397	  module will be called lpc32xx-keys.
398
399config KEYBOARD_MAPLE
400	tristate "Maple bus keyboard"
401	depends on SH_DREAMCAST && MAPLE
402	help
403	  Say Y here if you have a Dreamcast console running Linux and have
404	  a keyboard attached to its Maple bus.
405
406	  To compile this driver as a module, choose M here: the
407	  module will be called maple_keyb.
408
409config KEYBOARD_MAX7359
410	tristate "Maxim MAX7359 Key Switch Controller"
411	select INPUT_MATRIXKMAP
412	depends on I2C
413	help
414	  If you say yes here you get support for the Maxim MAX7359 Key
415	  Switch Controller chip. This providers microprocessors with
416	  management of up to 64 key switches
417
418	  To compile this driver as a module, choose M here: the
419	  module will be called max7359_keypad.
420
421config KEYBOARD_MAX7360
422	tristate "Maxim MAX7360 Key Switch Controller"
423	select INPUT_MATRIXKMAP
424	depends on I2C
425	depends on MFD_MAX7360
426	help
427	  If you say yes here you get support for the keypad controller on the
428	  Maxim MAX7360 I/O Expander.
429
430	  To compile this driver as a module, choose M here: the module will be
431	  called max7360_keypad.
432
433config KEYBOARD_MPR121
434	tristate "Freescale MPR121 Touchkey"
435	depends on I2C
436	help
437	  Say Y here if you have Freescale MPR121 touchkey controller
438	  chip in your system.
439
440	  If unsure, say N.
441
442	  To compile this driver as a module, choose M here: the
443	  module will be called mpr121_touchkey.
444
445config KEYBOARD_SNVS_PWRKEY
446	tristate "IMX SNVS Power Key Driver"
447	depends on ARCH_MXC || (COMPILE_TEST && HAS_IOMEM)
448	depends on OF
449	help
450	  This is the snvs powerkey driver for the Freescale i.MX application
451	  processors.
452
453	  To compile this driver as a module, choose M here; the
454	  module will be called snvs_pwrkey.
455
456config KEYBOARD_IMX
457	tristate "IMX keypad support"
458	depends on ARCH_MXC || COMPILE_TEST
459	select INPUT_MATRIXKMAP
460	help
461	  Enable support for IMX keypad port.
462
463	  To compile this driver as a module, choose M here: the
464	  module will be called imx_keypad.
465
466config KEYBOARD_IMX_BBM_SCMI
467	tristate "IMX BBM SCMI Key Driver"
468	depends on IMX_SCMI_BBM_EXT || COMPILE_TEST
469	default y if ARCH_MXC
470	help
471	  This is the BBM key driver for NXP i.MX SoCs managed through
472	  SCMI protocol.
473
474	  To compile this driver as a module, choose M here: the
475	  module will be called scmi-imx-bbm-key.
476
477config KEYBOARD_IMX_SC_KEY
478	tristate "IMX SCU Key Driver"
479	depends on IMX_SCU
480	help
481	  This is the system controller key driver for NXP i.MX SoCs with
482	  system controller inside.
483
484	  To compile this driver as a module, choose M here: the
485	  module will be called imx_sc_key.
486
487config KEYBOARD_NEWTON
488	tristate "Newton keyboard"
489	select SERIO
490	help
491	  Say Y here if you have a Newton keyboard on a serial port.
492
493	  To compile this driver as a module, choose M here: the
494	  module will be called newtonkbd.
495
496config KEYBOARD_NSPIRE
497	tristate "TI-NSPIRE built-in keyboard"
498	depends on ARCH_NSPIRE && OF
499	select INPUT_MATRIXKMAP
500	help
501	  Say Y here if you want to use the built-in keypad on TI-NSPIRE.
502
503	  To compile this driver as a module, choose M here: the
504	  module will be called nspire-keypad.
505
506config KEYBOARD_TEGRA
507	tristate "NVIDIA Tegra internal matrix keyboard controller support"
508	depends on (ARCH_TEGRA && OF) || COMPILE_TEST
509	select INPUT_MATRIXKMAP
510	help
511	  Say Y here if you want to use a matrix keyboard connected directly
512	  to the internal keyboard controller on Tegra SoCs.
513
514	  To compile this driver as a module, choose M here: the
515	  module will be called tegra-kbc.
516
517config KEYBOARD_OPENCORES
518	tristate "OpenCores Keyboard Controller"
519	depends on HAS_IOMEM
520	help
521	  Say Y here if you want to use the OpenCores Keyboard Controller
522	  http://www.opencores.org/project,keyboardcontroller
523
524	  To compile this driver as a module, choose M here; the
525	  module will be called opencores-kbd.
526
527config KEYBOARD_PINEPHONE
528	tristate "Pine64 PinePhone Keyboard"
529	depends on I2C && REGULATOR
530	select CRC8
531	select INPUT_MATRIXKMAP
532	help
533	  Say Y here to enable support for the keyboard in the Pine64 PinePhone
534	  keyboard case. This driver supports the FLOSS firmware available at
535	  https://megous.com/git/pinephone-keyboard/
536
537	  To compile this driver as a module, choose M here; the
538	  module will be called pinephone-keyboard.
539
540config KEYBOARD_PXA27x
541	tristate "PXA27x/PXA3xx keypad support"
542	depends on PXA27x || PXA3xx || ARCH_MMP || COMPILE_TEST
543	select INPUT_MATRIXKMAP
544	help
545	  Enable support for PXA27x/PXA3xx keypad controller.
546
547	  To compile this driver as a module, choose M here: the
548	  module will be called pxa27x_keypad.
549
550config KEYBOARD_PMIC8XXX
551	tristate "Qualcomm PMIC8XXX keypad support"
552	depends on MFD_PM8XXX
553	select INPUT_MATRIXKMAP
554	help
555	  Say Y here if you want to enable the driver for the PMIC8XXX
556	  keypad provided as a reference design from Qualcomm. This is intended
557	  to support up to 18x8 matrix-based keypad design.
558
559	  To compile this driver as a module, choose M here: the module will
560	  be called pmic8xxx-keypad.
561
562config KEYBOARD_SAMSUNG
563	tristate "Samsung keypad support"
564	depends on HAS_IOMEM && HAVE_CLK
565	select INPUT_MATRIXKMAP
566	help
567	  Say Y here if you want to use the keypad on your Samsung mobile
568	  device.
569
570	  To compile this driver as a module, choose M here: the
571	  module will be called samsung-keypad.
572
573config KEYBOARD_GOLDFISH_EVENTS
574	depends on GOLDFISH || COMPILE_TEST
575	tristate "Generic Input Event device for Goldfish"
576	help
577	  Say Y here to get an input event device for the Goldfish virtual
578	  device emulator.
579
580	  To compile this driver as a module, choose M here: the
581	  module will be called goldfish-events.
582
583config KEYBOARD_STOWAWAY
584	tristate "Stowaway keyboard"
585	select SERIO
586	help
587	  Say Y here if you have a Stowaway keyboard on a serial port.
588	  Stowaway compatible keyboards like Dicota Input-PDA keyboard
589	  are also supported by this driver.
590
591	  To compile this driver as a module, choose M here: the
592	  module will be called stowaway.
593
594config KEYBOARD_ST_KEYSCAN
595	tristate "STMicroelectronics keyscan support"
596	depends on ARCH_STI || COMPILE_TEST
597	select INPUT_MATRIXKMAP
598	help
599	  Say Y here if you want to use a keypad attached to the keyscan block
600	  on some STMicroelectronics SoC devices.
601
602	  To compile this driver as a module, choose M here: the
603	  module will be called st-keyscan.
604
605config KEYBOARD_SUNKBD
606	tristate "Sun Type 4 and Type 5 keyboard"
607	select SERIO
608	help
609	  Say Y here if you want to use a Sun Type 4 or Type 5 keyboard,
610	  connected either to the Sun keyboard connector or to an serial
611	  (RS-232) port via a simple adapter.
612
613	  To compile this driver as a module, choose M here: the
614	  module will be called sunkbd.
615
616config KEYBOARD_SH_KEYSC
617	tristate "SuperH KEYSC keypad support"
618	depends on ARCH_SHMOBILE || COMPILE_TEST
619	help
620	  Say Y here if you want to use a keypad attached to the KEYSC block
621	  on SuperH processors such as sh7722 and sh7343.
622
623	  To compile this driver as a module, choose M here: the
624	  module will be called sh_keysc.
625
626config KEYBOARD_STMPE
627	tristate "STMPE keypad support"
628	depends on MFD_STMPE
629	depends on OF
630	select INPUT_MATRIXKMAP
631	help
632	  Say Y here if you want to use the keypad controller on STMPE I/O
633	  expanders.
634
635	  To compile this driver as a module, choose M here: the module will be
636	  called stmpe-keypad.
637
638config KEYBOARD_SUN4I_LRADC
639	tristate "Allwinner sun4i low res adc attached tablet keys support"
640	depends on ARCH_SUNXI
641	help
642	  This selects support for the Allwinner low res adc attached tablet
643	  keys found on Allwinner sunxi SoCs.
644
645	  To compile this driver as a module, choose M here: the
646	  module will be called sun4i-lradc-keys.
647
648config KEYBOARD_IPAQ_MICRO
649	tristate "Buttons on Micro SoC (iPaq h3100,h3600,h3700)"
650	depends on MFD_IPAQ_MICRO
651	help
652	  Say Y to enable support for the buttons attached to
653	  Micro peripheral controller on iPAQ h3100/h3600/h3700
654
655	  To compile this driver as a module, choose M here: the
656	  module will be called ipaq-micro-keys.
657
658config KEYBOARD_IQS62X
659	tristate "Azoteq IQS620A/621/622/624/625 keys and switches"
660	depends on MFD_IQS62X
661	help
662	  Say Y here to enable key and switch support for the Azoteq IQS620A,
663	  IQS621, IQS622, IQS624 and IQS625 multi-function sensors.
664
665	  To compile this driver as a module, choose M here: the module will
666	  be called iqs62x-keys.
667
668config KEYBOARD_OMAP
669	tristate "TI OMAP keypad support"
670	depends on ARCH_OMAP1
671	select INPUT_MATRIXKMAP
672	help
673	  Say Y here if you want to use the OMAP keypad.
674
675	  To compile this driver as a module, choose M here: the
676	  module will be called omap-keypad.
677
678config KEYBOARD_OMAP4
679	tristate "TI OMAP4+ keypad support"
680	depends on (OF && HAS_IOMEM) || ARCH_OMAP2PLUS
681	select INPUT_MATRIXKMAP
682	help
683	  Say Y here if you want to use the OMAP4+ keypad.
684
685	  To compile this driver as a module, choose M here: the
686	  module will be called omap4-keypad.
687
688config KEYBOARD_SPEAR
689	tristate "ST SPEAR keyboard support"
690	depends on PLAT_SPEAR || COMPILE_TEST
691	select INPUT_MATRIXKMAP
692	help
693	  Say Y here if you want to use the SPEAR keyboard.
694
695	  To compile this driver as a module, choose M here: the
696	  module will be called spear-keyboard.
697
698config KEYBOARD_TC3589X
699	tristate "TC3589X Keypad support"
700	depends on MFD_TC3589X
701	select INPUT_MATRIXKMAP
702	help
703	  Say Y here if you want to use the keypad controller on
704	  TC35892/3 I/O expander.
705
706	  To compile this driver as a module, choose M here: the
707	  module will be called tc3589x-keypad.
708
709config KEYBOARD_TM2_TOUCHKEY
710	tristate "TM2 touchkey support"
711	depends on I2C
712	depends on LEDS_CLASS
713	help
714	  Say Y here to enable device driver for tm2-touchkey with
715	  LED control for the Exynos5433 TM2 board.
716
717	  To compile this driver as a module, choose M here.
718	  module will be called tm2-touchkey.
719
720config KEYBOARD_TWL4030
721	tristate "TI TWL4030/TWL5030/TPS659x0 keypad support"
722	depends on TWL4030_CORE
723	select INPUT_MATRIXKMAP
724	help
725	  Say Y here if your board use the keypad controller on
726	  TWL4030 family chips.  It's safe to say enable this
727	  even on boards that don't use the keypad controller.
728
729	  To compile this driver as a module, choose M here: the
730	  module will be called twl4030_keypad.
731
732config KEYBOARD_XTKBD
733	tristate "XT keyboard"
734	select SERIO
735	help
736	  Say Y here if you want to use the old IBM PC/XT keyboard (or
737	  compatible) on your system. This is only possible with a
738	  parallel port keyboard adapter, you cannot connect it to the
739	  keyboard port on a PC that runs Linux.
740
741	  To compile this driver as a module, choose M here: the
742	  module will be called xtkbd.
743
744config KEYBOARD_CROS_EC
745	tristate "ChromeOS EC keyboard"
746	select INPUT_MATRIXKMAP
747	select INPUT_VIVALDIFMAP
748	depends on CROS_EC
749	help
750	  Say Y here to enable the matrix keyboard used by ChromeOS devices
751	  and implemented on the ChromeOS EC. You must enable one bus option
752	  (CROS_EC_I2C or CROS_EC_SPI) to use this.
753
754	  To compile this driver as a module, choose M here: the
755	  module will be called cros_ec_keyb.
756
757config KEYBOARD_CAP11XX
758	tristate "Microchip CAP11XX based touch sensors"
759	depends on OF && I2C
760	select REGMAP_I2C
761	help
762	  Say Y here to enable the CAP11XX touch sensor driver.
763
764	  To compile this driver as a module, choose M here: the
765	  module will be called cap11xx.
766
767config KEYBOARD_BCM
768	tristate "Broadcom keypad driver"
769	depends on OF && HAVE_CLK && HAS_IOMEM
770	select INPUT_MATRIXKMAP
771	default ARCH_BCM_CYGNUS
772	help
773	  Say Y here if you want to use Broadcom keypad.
774
775	  To compile this driver as a module, choose M here: the
776	  module will be called bcm-keypad.
777
778config KEYBOARD_MT6779
779	tristate "MediaTek Keypad Support"
780	depends on ARCH_MEDIATEK || COMPILE_TEST
781	select REGMAP_MMIO
782	select INPUT_MATRIXKMAP
783	help
784	  Say Y here if you want to use the keypad on MediaTek SoCs.
785	  If unsure, say N.
786
787	  To compile this driver as a module, choose M here: the
788	  module will be called mt6779-keypad.
789
790config KEYBOARD_MTK_PMIC
791	tristate "MediaTek PMIC keys support"
792	depends on MFD_MT6397 || COMPILE_TEST
793	help
794	  Say Y here if you want to use the pmic keys (powerkey/homekey).
795
796	  To compile this driver as a module, choose M here: the
797	  module will be called pmic-keys.
798
799config KEYBOARD_CYPRESS_SF
800	tristate "Cypress StreetFighter touchkey support"
801	depends on I2C
802	help
803	  Say Y here if you want to enable support for Cypress StreetFighter
804	  touchkeys.
805
806	  To compile this driver as a module, choose M here: the
807	  module will be called cypress-sf.
808
809endif
810