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