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