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