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