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