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