xref: /openbmc/linux/drivers/input/misc/Kconfig (revision ba61bb17)
1#
2# Input misc drivers configuration
3#
4menuconfig INPUT_MISC
5	bool "Miscellaneous devices"
6	help
7	  Say Y here, and a list of miscellaneous input drivers will be displayed.
8	  Everything that didn't fit into the other categories is here. This option
9	  doesn't affect the kernel.
10
11	  If unsure, say Y.
12
13if INPUT_MISC
14
15config INPUT_88PM860X_ONKEY
16	tristate "88PM860x ONKEY support"
17	depends on MFD_88PM860X
18	help
19	  Support the ONKEY of Marvell 88PM860x PMICs as an input device
20	  reporting power button status.
21
22	  To compile this driver as a module, choose M here: the module
23	  will be called 88pm860x_onkey.
24
25config INPUT_88PM80X_ONKEY
26	tristate "88PM80x ONKEY support"
27	depends on MFD_88PM800
28	help
29	  Support the ONKEY of Marvell 88PM80x PMICs as an input device
30	  reporting power button status.
31
32	  To compile this driver as a module, choose M here: the module
33	  will be called 88pm80x_onkey.
34
35config INPUT_AB8500_PONKEY
36	tristate "AB8500 Pon (PowerOn) Key"
37	depends on AB8500_CORE
38	help
39	  Say Y here to use the PowerOn Key for ST-Ericsson's AB8500
40	  Mix-Sig PMIC.
41
42	  To compile this driver as a module, choose M here: the module
43	  will be called ab8500-ponkey.
44
45config INPUT_AD714X
46	tristate "Analog Devices AD714x Capacitance Touch Sensor"
47	help
48	  Say Y here if you want to support an AD7142/3/7/8/7A touch sensor.
49
50	  You should select a bus connection too.
51
52	  To compile this driver as a module, choose M here: the
53	  module will be called ad714x.
54
55config INPUT_AD714X_I2C
56	tristate "support I2C bus connection"
57	depends on INPUT_AD714X && I2C
58	default y
59	help
60	  Say Y here if you have AD7142/AD7147 hooked to an I2C bus.
61
62	  To compile this driver as a module, choose M here: the
63	  module will be called ad714x-i2c.
64
65config INPUT_AD714X_SPI
66	tristate "support SPI bus connection"
67	depends on INPUT_AD714X && SPI
68	default y
69	help
70	  Say Y here if you have AD7142/AD7147 hooked to a SPI bus.
71
72	  To compile this driver as a module, choose M here: the
73	  module will be called ad714x-spi.
74
75config INPUT_ARIZONA_HAPTICS
76	tristate "Arizona haptics support"
77	depends on MFD_ARIZONA && SND_SOC
78	select INPUT_FF_MEMLESS
79	help
80	  Say Y to enable support for the haptics module in Arizona CODECs.
81
82	  To compile this driver as a module, choose M here: the
83	  module will be called arizona-haptics.
84
85config INPUT_ATMEL_CAPTOUCH
86	tristate "Atmel Capacitive Touch Button Driver"
87	depends on OF || COMPILE_TEST
88	depends on I2C
89	help
90	  Say Y here if an Atmel Capacitive Touch Button device which
91	  implements "captouch" protocol is connected to I2C bus. Typically
92	  this device consists of Atmel Touch sensor controlled by AtMegaXX
93	  MCU running firmware based on Qtouch library.
94	  One should find "atmel,captouch" node in the board specific DTS.
95
96	  To compile this driver as a module, choose M here: the
97	  module will be called atmel_captouch.
98
99config INPUT_BMA150
100	tristate "BMA150/SMB380 acceleration sensor support"
101	depends on I2C
102	select INPUT_POLLDEV
103	help
104	  Say Y here if you have Bosch Sensortec's BMA150 or SMB380
105	  acceleration sensor hooked to an I2C bus.
106
107	  To compile this driver as a module, choose M here: the
108	  module will be called bma150.
109
110config INPUT_E3X0_BUTTON
111	tristate "NI Ettus Research USRP E3xx Button support."
112	default n
113	help
114	  Say Y here to enable support for the NI Ettus Research
115	  USRP E3xx Button.
116
117	  To compile this driver as a module, choose M here: the
118	  module will be called e3x0_button.
119
120config INPUT_PCSPKR
121	tristate "PC Speaker support"
122	depends on PCSPKR_PLATFORM
123	help
124	  Say Y here if you want the standard PC Speaker to be used for
125	  bells and whistles.
126
127	  If unsure, say Y.
128
129	  To compile this driver as a module, choose M here: the
130	  module will be called pcspkr.
131
132config INPUT_PM8941_PWRKEY
133	tristate "Qualcomm PM8941 power key support"
134	depends on MFD_SPMI_PMIC
135	help
136	  Say Y here if you want support for the power key usually found
137	  on boards using a Qualcomm PM8941 compatible PMIC.
138
139	  If unsure, say Y.
140
141	  To compile this driver as a module, choose M here: the module
142	  will be called pm8941-pwrkey.
143
144config INPUT_PM8XXX_VIBRATOR
145	tristate "Qualcomm PM8XXX vibrator support"
146	depends on MFD_PM8XXX || MFD_SPMI_PMIC
147	select INPUT_FF_MEMLESS
148	help
149	  This option enables device driver support for the vibrator
150	  on Qualcomm PM8xxx chip. This driver supports ff-memless interface
151	  from input framework.
152
153	  To compile this driver as module, choose M here: the
154	  module will be called pm8xxx-vibrator.
155
156config INPUT_PMIC8XXX_PWRKEY
157	tristate "PMIC8XXX power key support"
158	depends on MFD_PM8XXX
159	help
160	  Say Y here if you want support for the PMIC8XXX power key.
161
162	  If unsure, say N.
163
164	  To compile this driver as a module, choose M here: the
165	  module will be called pmic8xxx-pwrkey.
166
167config INPUT_SPARCSPKR
168	tristate "SPARC Speaker support"
169	depends on PCI && SPARC64
170	help
171	  Say Y here if you want the standard Speaker on Sparc PCI systems
172	  to be used for bells and whistles.
173
174	  If unsure, say Y.
175
176	  To compile this driver as a module, choose M here: the
177	  module will be called sparcspkr.
178
179config INPUT_M68K_BEEP
180	tristate "M68k Beeper support"
181	depends on M68K
182
183config INPUT_MAX77693_HAPTIC
184	tristate "MAXIM MAX77693/MAX77843 haptic controller support"
185	depends on (MFD_MAX77693 || MFD_MAX77843) && PWM
186	select INPUT_FF_MEMLESS
187	help
188	  This option enables support for the haptic controller on
189	  MAXIM MAX77693 and MAX77843 chips.
190
191	  To compile this driver as module, choose M here: the
192	  module will be called max77693-haptic.
193
194config INPUT_MAX8925_ONKEY
195	tristate "MAX8925 ONKEY support"
196	depends on MFD_MAX8925
197	help
198	  Support the ONKEY of MAX8925 PMICs as an input device
199	  reporting power button status.
200
201	  To compile this driver as a module, choose M here: the module
202	  will be called max8925_onkey.
203
204config INPUT_MAX8997_HAPTIC
205	tristate "MAXIM MAX8997 haptic controller support"
206	depends on PWM && MFD_MAX8997
207	select INPUT_FF_MEMLESS
208	help
209	  This option enables device driver support for the haptic controller
210	  on MAXIM MAX8997 chip. This driver supports ff-memless interface
211	  from input framework.
212
213	  To compile this driver as module, choose M here: the
214	  module will be called max8997-haptic.
215
216config INPUT_MC13783_PWRBUTTON
217	tristate "MC13783 ON buttons"
218	depends on MFD_MC13XXX
219	help
220	  Support the ON buttons of MC13783 PMIC as an input device
221	  reporting power button status.
222
223	  To compile this driver as a module, choose M here: the module
224	  will be called mc13783-pwrbutton.
225
226config INPUT_MMA8450
227	tristate "MMA8450 - Freescale's 3-Axis, 8/12-bit Digital Accelerometer"
228	depends on I2C
229	select INPUT_POLLDEV
230	help
231	  Say Y here if you want to support Freescale's MMA8450 Accelerometer
232	  through I2C interface.
233
234	  To compile this driver as a module, choose M here: the
235	  module will be called mma8450.
236
237config INPUT_APANEL
238	tristate "Fujitsu Lifebook Application Panel buttons"
239	depends on X86 && I2C && LEDS_CLASS
240	select INPUT_POLLDEV
241	select CHECK_SIGNATURE
242	help
243	 Say Y here for support of the Application Panel buttons, used on
244	 Fujitsu Lifebook. These are attached to the mainboard through
245	 an SMBus interface managed by the I2C Intel ICH (i801) driver,
246	 which you should also build for this kernel.
247
248	 To compile this driver as a module, choose M here: the module will
249	 be called apanel.
250
251config INPUT_GP2A
252	tristate "Sharp GP2AP002A00F I2C Proximity/Opto sensor driver"
253	depends on I2C
254	depends on GPIOLIB || COMPILE_TEST
255	help
256	  Say Y here if you have a Sharp GP2AP002A00F proximity/als combo-chip
257	  hooked to an I2C bus.
258
259	  To compile this driver as a module, choose M here: the
260	  module will be called gp2ap002a00f.
261
262config INPUT_GPIO_BEEPER
263	tristate "Generic GPIO Beeper support"
264	depends on GPIOLIB || COMPILE_TEST
265	help
266	  Say Y here if you have a beeper connected to a GPIO pin.
267
268	  To compile this driver as a module, choose M here: the
269	  module will be called gpio-beeper.
270
271config INPUT_GPIO_DECODER
272	tristate "Polled GPIO Decoder Input driver"
273	depends on GPIOLIB || COMPILE_TEST
274	select INPUT_POLLDEV
275	help
276	 Say Y here if you want driver to read status of multiple GPIO
277	 lines and report the encoded value as an absolute integer to
278	 input subsystem.
279
280	 To compile this driver as a module, choose M here: the module
281	 will be called gpio_decoder.
282
283config INPUT_IXP4XX_BEEPER
284	tristate "IXP4XX Beeper support"
285	depends on ARCH_IXP4XX
286	help
287	  If you say yes here, you can connect a beeper to the
288	  ixp4xx gpio pins. This is used by the LinkSys NSLU2.
289
290	  If unsure, say Y.
291
292	  To compile this driver as a module, choose M here: the
293	  module will be called ixp4xx-beeper.
294
295config INPUT_COBALT_BTNS
296	tristate "Cobalt button interface"
297	depends on MIPS_COBALT
298	select INPUT_POLLDEV
299	help
300	  Say Y here if you want to support MIPS Cobalt button interface.
301
302	  To compile this driver as a module, choose M here: the
303	  module will be called cobalt_btns.
304
305config INPUT_CPCAP_PWRBUTTON
306	tristate "CPCAP OnKey"
307	depends on MFD_CPCAP
308	help
309	  Say Y here if you want to enable power key reporting via the
310	  Motorola CPCAP chip.
311
312	  To compile this driver as a module, choose M here. The module will
313	  be called cpcap-pwrbutton.
314
315config INPUT_WISTRON_BTNS
316	tristate "x86 Wistron laptop button interface"
317	depends on X86_32
318	select INPUT_POLLDEV
319	select INPUT_SPARSEKMAP
320	select NEW_LEDS
321	select LEDS_CLASS
322	select CHECK_SIGNATURE
323	help
324	  Say Y here for support of Wistron laptop button interfaces, used on
325	  laptops of various brands, including Acer and Fujitsu-Siemens. If
326	  available, mail and wifi LEDs will be controllable via /sys/class/leds.
327
328	  To compile this driver as a module, choose M here: the module will
329	  be called wistron_btns.
330
331config INPUT_ATLAS_BTNS
332	tristate "x86 Atlas button interface"
333	depends on X86 && ACPI
334	help
335	  Say Y here for support of Atlas wallmount touchscreen buttons.
336	  The events will show up as scancodes F1 through F9 via evdev.
337
338	  To compile this driver as a module, choose M here: the module will
339	  be called atlas_btns.
340
341config INPUT_ATI_REMOTE2
342	tristate "ATI / Philips USB RF remote control"
343	depends on USB_ARCH_HAS_HCD
344	select USB
345	help
346	  Say Y here if you want to use an ATI or Philips USB RF remote control.
347	  These are RF remotes with USB receivers.
348	  ATI Remote Wonder II comes with some ATI's All-In-Wonder video cards
349	  and is also available as a separate product.
350	  This driver provides mouse pointer, left and right mouse buttons,
351	  and maps all the other remote buttons to keypress events.
352
353	  To compile this driver as a module, choose M here: the module will be
354	  called ati_remote2.
355
356config INPUT_KEYSPAN_REMOTE
357	tristate "Keyspan DMR USB remote control"
358	depends on USB_ARCH_HAS_HCD
359	select USB
360	help
361	  Say Y here if you want to use a Keyspan DMR USB remote control.
362	  Currently only the UIA-11 type of receiver has been tested.  The tag
363	  on the receiver that connects to the USB port should have a P/N that
364	  will tell you what type of DMR you have.  The UIA-10 type is not
365	  supported at this time.  This driver maps all buttons to keypress
366	  events.
367
368	  To compile this driver as a module, choose M here: the module will
369	  be called keyspan_remote.
370
371config INPUT_KXTJ9
372	tristate "Kionix KXTJ9 tri-axis digital accelerometer"
373	depends on I2C
374	help
375	  Say Y here to enable support for the Kionix KXTJ9 digital tri-axis
376	  accelerometer.
377
378	  To compile this driver as a module, choose M here: the module will
379	  be called kxtj9.
380
381config INPUT_KXTJ9_POLLED_MODE
382	bool "Enable polling mode support"
383	depends on INPUT_KXTJ9
384	select INPUT_POLLDEV
385	help
386	  Say Y here if you need accelerometer to work in polling mode.
387
388config INPUT_POWERMATE
389	tristate "Griffin PowerMate and Contour Jog support"
390	depends on USB_ARCH_HAS_HCD
391	select USB
392	help
393	  Say Y here if you want to use Griffin PowerMate or Contour Jog devices.
394	  These are aluminum dials which can measure clockwise and anticlockwise
395	  rotation.  The dial also acts as a pushbutton.  The base contains an LED
396	  which can be instructed to pulse or to switch to a particular intensity.
397
398	  You can download userspace tools from
399	  <http://sowerbutts.com/powermate/>.
400
401	  To compile this driver as a module, choose M here: the
402	  module will be called powermate.
403
404config INPUT_YEALINK
405	tristate "Yealink usb-p1k voip phone"
406	depends on USB_ARCH_HAS_HCD
407	select USB
408	help
409	  Say Y here if you want to enable keyboard and LCD functions of the
410	  Yealink usb-p1k usb phones. The audio part is enabled by the generic
411	  usb sound driver, so you might want to enable that as well.
412
413	  For information about how to use these additional functions, see
414	  <file:Documentation/input/devices/yealink.rst>.
415
416	  To compile this driver as a module, choose M here: the module will be
417	  called yealink.
418
419config INPUT_CM109
420	tristate "C-Media CM109 USB I/O Controller"
421	depends on USB_ARCH_HAS_HCD
422	select USB
423	help
424	  Say Y here if you want to enable keyboard and buzzer functions of the
425	  C-Media CM109 usb phones. The audio part is enabled by the generic
426	  usb sound driver, so you might want to enable that as well.
427
428	  To compile this driver as a module, choose M here: the module will be
429	  called cm109.
430
431config INPUT_REGULATOR_HAPTIC
432	tristate "Regulator haptics support"
433	depends on REGULATOR
434	select INPUT_FF_MEMLESS
435	help
436	  This option enables device driver support for the haptic controlled
437	  by a regulator. This driver supports ff-memless interface
438	  from input framework.
439
440	  To compile this driver as a module, choose M here: the
441	  module will be called regulator-haptic.
442
443config INPUT_RETU_PWRBUTTON
444	tristate "Retu Power button Driver"
445	depends on MFD_RETU
446	help
447	  Say Y here if you want to enable power key reporting via the
448	  Retu chips found in Nokia Internet Tablets (770, N800, N810).
449
450	  To compile this driver as a module, choose M here. The module will
451	  be called retu-pwrbutton.
452
453config INPUT_TPS65218_PWRBUTTON
454	tristate "TPS65218 Power button driver"
455	depends on (MFD_TPS65217 || MFD_TPS65218)
456	help
457	  Say Y here if you want to enable power button reporting for
458	  TPS65217 and TPS65218 Power Management IC devices.
459
460	  To compile this driver as a module, choose M here. The module will
461	  be called tps65218-pwrbutton.
462
463config INPUT_AXP20X_PEK
464	tristate "X-Powers AXP20X power button driver"
465	depends on MFD_AXP20X
466	help
467	  Say Y here if you want to enable power key reporting via the
468	  AXP20X PMIC.
469
470	  To compile this driver as a module, choose M here. The module will
471	  be called axp20x-pek.
472
473
474config INPUT_TWL4030_PWRBUTTON
475	tristate "TWL4030 Power button Driver"
476	depends on TWL4030_CORE
477	help
478	  Say Y here if you want to enable power key reporting via the
479	  TWL4030 family of chips.
480
481	  To compile this driver as a module, choose M here. The module will
482	  be called twl4030_pwrbutton.
483
484config INPUT_TWL4030_VIBRA
485	tristate "Support for TWL4030 Vibrator"
486	depends on TWL4030_CORE
487	select MFD_TWL4030_AUDIO
488	select INPUT_FF_MEMLESS
489	help
490	  This option enables support for TWL4030 Vibrator Driver.
491
492	  To compile this driver as a module, choose M here. The module will
493	  be called twl4030_vibra.
494
495config INPUT_TWL6040_VIBRA
496	tristate "Support for TWL6040 Vibrator"
497	depends on TWL6040_CORE
498	select INPUT_FF_MEMLESS
499	help
500	  This option enables support for TWL6040 Vibrator Driver.
501
502	  To compile this driver as a module, choose M here. The module will
503	  be called twl6040_vibra.
504
505config INPUT_UINPUT
506	tristate "User level driver support"
507	help
508	  Say Y here if you want to support user level drivers for input
509	  subsystem accessible under char device 10:223 - /dev/input/uinput.
510
511	  To compile this driver as a module, choose M here: the
512	  module will be called uinput.
513
514config INPUT_SGI_BTNS
515	tristate "SGI Indy/O2 volume button interface"
516	depends on SGI_IP22 || SGI_IP32
517	select INPUT_POLLDEV
518	help
519	  Say Y here if you want to support SGI Indy/O2 volume button interface.
520
521	  To compile this driver as a module, choose M here: the
522	  module will be called sgi_btns.
523
524config HP_SDC_RTC
525	tristate "HP SDC Real Time Clock"
526	depends on (GSC || HP300) && SERIO
527	select HP_SDC
528	help
529	  Say Y here if you want to support the built-in real time clock
530	  of the HP SDC controller.
531
532config INPUT_PALMAS_PWRBUTTON
533	tristate "Palmas Power button Driver"
534	depends on MFD_PALMAS
535	help
536	  Say Y here if you want to enable power key reporting via the
537	  Palmas family of PMICs.
538
539	  To compile this driver as a module, choose M here. The module will
540	  be called palmas_pwrbutton.
541
542config INPUT_PCF50633_PMU
543	tristate "PCF50633 PMU events"
544	depends on MFD_PCF50633
545	help
546	 Say Y to include support for delivering  PMU events via  input
547	 layer on NXP PCF50633.
548
549config INPUT_PCF8574
550	tristate "PCF8574 Keypad input device"
551	depends on I2C
552	help
553	  Say Y here if you want to support a keypad connected via I2C
554	  with a PCF8574.
555
556	  To compile this driver as a module, choose M here: the
557	  module will be called pcf8574_keypad.
558
559config INPUT_PWM_BEEPER
560	tristate "PWM beeper support"
561	depends on PWM
562	help
563	  Say Y here to get support for PWM based beeper devices.
564
565	  If unsure, say N.
566
567	  To compile this driver as a module, choose M here: the module will be
568	  called pwm-beeper.
569
570config INPUT_PWM_VIBRA
571	tristate "PWM vibrator support"
572	depends on PWM
573	select INPUT_FF_MEMLESS
574	help
575	  Say Y here to get support for PWM based vibrator devices.
576
577	  If unsure, say N.
578
579	  To compile this driver as a module, choose M here: the module will be
580	  called pwm-vibra.
581
582config INPUT_RK805_PWRKEY
583	tristate "Rockchip RK805 PMIC power key support"
584	depends on MFD_RK808
585	help
586	  Select this option to enable power key driver for RK805.
587
588	  If unsure, say N.
589
590	  To compile this driver as a module, choose M here: the module will be
591	  called rk805_pwrkey.
592
593config INPUT_GPIO_ROTARY_ENCODER
594	tristate "Rotary encoders connected to GPIO pins"
595	depends on GPIOLIB || COMPILE_TEST
596	help
597	  Say Y here to add support for rotary encoders connected to GPIO lines.
598	  Check file:Documentation/input/devices/rotary-encoder.rst for more
599	  information.
600
601	  To compile this driver as a module, choose M here: the
602	  module will be called rotary_encoder.
603
604config INPUT_RB532_BUTTON
605	tristate "Mikrotik Routerboard 532 button interface"
606	depends on MIKROTIK_RB532
607	depends on GPIOLIB
608	select INPUT_POLLDEV
609	help
610	  Say Y here if you want support for the S1 button built into
611	  Mikrotik's Routerboard 532.
612
613	  To compile this driver as a module, choose M here: the
614	  module will be called rb532_button.
615
616config INPUT_DA9052_ONKEY
617	tristate "Dialog DA9052/DA9053 Onkey"
618	depends on PMIC_DA9052
619	help
620	  Support the ONKEY of Dialog DA9052 PMICs as an input device
621	  reporting power button status.
622
623	  To compile this driver as a module, choose M here: the
624	  module will be called da9052_onkey.
625
626config INPUT_DA9055_ONKEY
627	tristate "Dialog Semiconductor DA9055 ONKEY"
628	depends on MFD_DA9055
629	help
630	  Support the ONKEY of DA9055 PMICs as an input device
631	  reporting power button status.
632
633	  To compile this driver as a module, choose M here: the module
634	  will be called da9055_onkey.
635
636config INPUT_DA9063_ONKEY
637	tristate "Dialog DA9063/62/61 OnKey"
638	depends on MFD_DA9063 || MFD_DA9062
639	help
640	  Support the ONKEY of Dialog DA9063, DA9062 and DA9061 Power
641	  Management ICs as an input device capable of reporting the
642	  power button status.
643
644	  To compile this driver as a module, choose M here: the module
645	  will be called da9063_onkey.
646
647config INPUT_DM355EVM
648	tristate "TI DaVinci DM355 EVM Keypad and IR Remote"
649	depends on MFD_DM355EVM_MSP
650	select INPUT_SPARSEKMAP
651	help
652	  Supports the pushbuttons and IR remote used with
653	  the DM355 EVM board.
654
655	  To compile this driver as a module, choose M here: the
656	  module will be called dm355evm_keys.
657
658config INPUT_WM831X_ON
659	tristate "WM831X ON pin"
660	depends on MFD_WM831X
661	help
662	  Support the ON pin of WM831X PMICs as an input device
663	  reporting power button status.
664
665	  To compile this driver as a module, choose M here: the module
666	  will be called wm831x_on.
667
668config INPUT_PCAP
669	tristate "Motorola EZX PCAP misc input events"
670	depends on EZX_PCAP
671	help
672	  Say Y here if you want to use Power key and Headphone button
673	  on Motorola EZX phones.
674
675	  To compile this driver as a module, choose M here: the
676	  module will be called pcap_keys.
677
678config INPUT_ADXL34X
679	tristate "Analog Devices ADXL34x Three-Axis Digital Accelerometer"
680	default n
681	help
682	  Say Y here if you have a Accelerometer interface using the
683	  ADXL345/6 controller, and your board-specific initialization
684	  code includes that in its table of devices.
685
686	  This driver can use either I2C or SPI communication to the
687	  ADXL345/6 controller.  Select the appropriate method for
688	  your system.
689
690	  If unsure, say N (but it's safe to say "Y").
691
692	  To compile this driver as a module, choose M here: the
693	  module will be called adxl34x.
694
695config INPUT_ADXL34X_I2C
696	tristate "support I2C bus connection"
697	depends on INPUT_ADXL34X && I2C
698	default y
699	help
700	  Say Y here if you have ADXL345/6 hooked to an I2C bus.
701
702	  To compile this driver as a module, choose M here: the
703	  module will be called adxl34x-i2c.
704
705config INPUT_ADXL34X_SPI
706	tristate "support SPI bus connection"
707	depends on INPUT_ADXL34X && SPI
708	default y
709	help
710	  Say Y here if you have ADXL345/6 hooked to a SPI bus.
711
712	  To compile this driver as a module, choose M here: the
713	  module will be called adxl34x-spi.
714
715config INPUT_IMS_PCU
716	tristate "IMS Passenger Control Unit driver"
717	depends on USB
718	depends on LEDS_CLASS
719	help
720	  Say Y here if you have system with IMS Rave Passenger Control Unit.
721
722	  To compile this driver as a module, choose M here: the module will be
723	  called ims_pcu.
724
725config INPUT_CMA3000
726	tristate "VTI CMA3000 Tri-axis accelerometer"
727	help
728	  Say Y here if you want to use VTI CMA3000_D0x Accelerometer
729	  driver
730
731	  This driver currently only supports I2C interface to the
732	  controller. Also select the I2C method.
733
734	  If unsure, say N
735
736	  To compile this driver as a module, choose M here: the
737	  module will be called cma3000_d0x.
738
739config INPUT_CMA3000_I2C
740	tristate "Support I2C bus connection"
741	depends on INPUT_CMA3000 && I2C
742	help
743	  Say Y here if you want to use VTI CMA3000_D0x Accelerometer
744	  through I2C interface.
745
746	  To compile this driver as a module, choose M here: the
747	  module will be called cma3000_d0x_i2c.
748
749config INPUT_XEN_KBDDEV_FRONTEND
750	tristate "Xen virtual keyboard and mouse support"
751	depends on XEN
752	default y
753	select XEN_XENBUS_FRONTEND
754	help
755	  This driver implements the front-end of the Xen virtual
756	  keyboard and mouse device driver.  It communicates with a back-end
757	  in another domain.
758
759	  To compile this driver as a module, choose M here: the
760	  module will be called xen-kbdfront.
761
762config INPUT_SIRFSOC_ONKEY
763	tristate "CSR SiRFSoC power on/off/suspend key support"
764	depends on ARCH_SIRF && OF
765	default y
766	help
767	  Say Y here if you want to support for the SiRFSoC power on/off/suspend key
768	  in Linux, after you press the onkey, system will suspend.
769
770	  If unsure, say N.
771
772config INPUT_IDEAPAD_SLIDEBAR
773	tristate "IdeaPad Laptop Slidebar"
774	depends on INPUT
775	depends on SERIO_I8042
776	help
777	  Say Y here if you have an IdeaPad laptop with a slidebar.
778
779	  To compile this driver as a module, choose M here: the
780	  module will be called ideapad_slidebar.
781
782config INPUT_SOC_BUTTON_ARRAY
783	tristate "Windows-compatible SoC Button Array"
784	depends on KEYBOARD_GPIO
785	help
786	  Say Y here if you have a SoC-based tablet that originally
787	  runs Windows 8.
788
789	  To compile this driver as a module, choose M here: the
790	  module will be called soc_button_array.
791
792config INPUT_DRV260X_HAPTICS
793	tristate "TI DRV260X haptics support"
794	depends on INPUT && I2C
795	depends on GPIOLIB || COMPILE_TEST
796	select INPUT_FF_MEMLESS
797	select REGMAP_I2C
798	help
799	  Say Y to enable support for the TI DRV260X haptics driver.
800
801	  To compile this driver as a module, choose M here: the
802	  module will be called drv260x-haptics.
803
804config INPUT_DRV2665_HAPTICS
805	tristate "TI DRV2665 haptics support"
806	depends on INPUT && I2C
807	select INPUT_FF_MEMLESS
808	select REGMAP_I2C
809	help
810	  Say Y to enable support for the TI DRV2665 haptics driver.
811
812	  To compile this driver as a module, choose M here: the
813	  module will be called drv2665-haptics.
814
815config INPUT_DRV2667_HAPTICS
816	tristate "TI DRV2667 haptics support"
817	depends on INPUT && I2C
818	select INPUT_FF_MEMLESS
819	select REGMAP_I2C
820	help
821	  Say Y to enable support for the TI DRV2667 haptics driver.
822
823	  To compile this driver as a module, choose M here: the
824	  module will be called drv2667-haptics.
825
826config INPUT_HISI_POWERKEY
827	tristate "Hisilicon PMIC ONKEY support"
828	depends on ARCH_HISI || COMPILE_TEST
829	help
830	  Say Y to enable support for PMIC ONKEY.
831
832	  To compile this driver as a module, choose M here: the
833	  module will be called hisi_powerkey.
834
835config INPUT_RAVE_SP_PWRBUTTON
836	tristate "RAVE SP Power button Driver"
837	depends on RAVE_SP_CORE
838	help
839	  Say Y here if you want to enable power key reporting from RAVE SP
840
841	  To compile this driver as a module, choose M here: the
842	  module will be called rave-sp-pwrbutton.
843
844config INPUT_SC27XX_VIBRA
845	tristate "Spreadtrum sc27xx vibrator support"
846	depends on MFD_SC27XX_PMIC || COMPILE_TEST
847	select INPUT_FF_MEMLESS
848	help
849	  This option enables support for Spreadtrum sc27xx vibrator driver.
850
851	  To compile this driver as a module, choose M here. The module will
852	  be called sc27xx_vibra.
853
854endif
855