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