Version:  2.0.40 2.2.26 2.4.37 3.13 3.14 3.15 3.16 3.17 3.18 3.19 4.0 4.1 4.2 4.3 4.4 4.5 4.6 4.7 4.8 4.9 4.10

Linux/drivers/input/misc/Kconfig

  1 #
  2 # Input misc drivers configuration
  3 #
  4 menuconfig 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 
 13 if INPUT_MISC
 14 
 15 config 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 
 25 config 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 
 35 config 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 
 45 config 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 
 55 config 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 
 65 config 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 
 75 config 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 
 85 config 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 
 99 config 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 
110 config 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 
120 config 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 
132 config 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 
144 config INPUT_PM8XXX_VIBRATOR
145         tristate "Qualcomm PM8XXX vibrator support"
146         depends on MFD_PM8XXX
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 
156 config 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 
167 config 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 
179 config INPUT_M68K_BEEP
180         tristate "M68k Beeper support"
181         depends on M68K
182 
183 config 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 
194 config 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 
204 config 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 
216 config 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 
226 config 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 
237 config INPUT_MPU3050
238         tristate "MPU3050 Triaxial gyroscope sensor"
239         depends on I2C
240         help
241           Say Y here if you want to support InvenSense MPU3050
242           connected via an I2C bus.
243 
244           To compile this driver as a module, choose M here: the
245           module will be called mpu3050.
246 
247 config INPUT_APANEL
248         tristate "Fujitsu Lifebook Application Panel buttons"
249         depends on X86 && I2C && LEDS_CLASS
250         select INPUT_POLLDEV
251         select CHECK_SIGNATURE
252         help
253          Say Y here for support of the Application Panel buttons, used on
254          Fujitsu Lifebook. These are attached to the mainboard through
255          an SMBus interface managed by the I2C Intel ICH (i801) driver,
256          which you should also build for this kernel.
257 
258          To compile this driver as a module, choose M here: the module will
259          be called apanel.
260 
261 config INPUT_GP2A
262         tristate "Sharp GP2AP002A00F I2C Proximity/Opto sensor driver"
263         depends on I2C
264         depends on GPIOLIB || COMPILE_TEST
265         help
266           Say Y here if you have a Sharp GP2AP002A00F proximity/als combo-chip
267           hooked to an I2C bus.
268 
269           To compile this driver as a module, choose M here: the
270           module will be called gp2ap002a00f.
271 
272 config INPUT_GPIO_BEEPER
273         tristate "Generic GPIO Beeper support"
274         depends on GPIOLIB || COMPILE_TEST
275         help
276           Say Y here if you have a beeper connected to a GPIO pin.
277 
278           To compile this driver as a module, choose M here: the
279           module will be called gpio-beeper.
280 
281 config INPUT_GPIO_TILT_POLLED
282         tristate "Polled GPIO tilt switch"
283         depends on GPIOLIB || COMPILE_TEST
284         select INPUT_POLLDEV
285         help
286           This driver implements support for tilt switches connected
287           to GPIO pins that are not capable of generating interrupts.
288 
289           The list of gpios to use and the mapping of their states
290           to specific angles is done via platform data.
291 
292           To compile this driver as a module, choose M here: the
293           module will be called gpio_tilt_polled.
294 
295 config INPUT_GPIO_DECODER
296         tristate "Polled GPIO Decoder Input driver"
297         depends on GPIOLIB || COMPILE_TEST
298         select INPUT_POLLDEV
299         help
300          Say Y here if you want driver to read status of multiple GPIO
301          lines and report the encoded value as an absolute integer to
302          input subsystem.
303 
304          To compile this driver as a module, choose M here: the module
305          will be called gpio_decoder.
306 
307 config INPUT_IXP4XX_BEEPER
308         tristate "IXP4XX Beeper support"
309         depends on ARCH_IXP4XX
310         help
311           If you say yes here, you can connect a beeper to the
312           ixp4xx gpio pins. This is used by the LinkSys NSLU2.
313 
314           If unsure, say Y.
315 
316           To compile this driver as a module, choose M here: the
317           module will be called ixp4xx-beeper.
318 
319 config INPUT_COBALT_BTNS
320         tristate "Cobalt button interface"
321         depends on MIPS_COBALT
322         select INPUT_POLLDEV
323         help
324           Say Y here if you want to support MIPS Cobalt button interface.
325 
326           To compile this driver as a module, choose M here: the
327           module will be called cobalt_btns.
328 
329 config INPUT_WISTRON_BTNS
330         tristate "x86 Wistron laptop button interface"
331         depends on X86_32
332         select INPUT_POLLDEV
333         select INPUT_SPARSEKMAP
334         select NEW_LEDS
335         select LEDS_CLASS
336         select CHECK_SIGNATURE
337         help
338           Say Y here for support of Wistron laptop button interfaces, used on
339           laptops of various brands, including Acer and Fujitsu-Siemens. If
340           available, mail and wifi LEDs will be controllable via /sys/class/leds.
341 
342           To compile this driver as a module, choose M here: the module will
343           be called wistron_btns.
344 
345 config INPUT_ATLAS_BTNS
346         tristate "x86 Atlas button interface"
347         depends on X86 && ACPI
348         help
349           Say Y here for support of Atlas wallmount touchscreen buttons.
350           The events will show up as scancodes F1 through F9 via evdev.
351 
352           To compile this driver as a module, choose M here: the module will
353           be called atlas_btns.
354 
355 config INPUT_ATI_REMOTE2
356         tristate "ATI / Philips USB RF remote control"
357         depends on USB_ARCH_HAS_HCD
358         select USB
359         help
360           Say Y here if you want to use an ATI or Philips USB RF remote control.
361           These are RF remotes with USB receivers.
362           ATI Remote Wonder II comes with some ATI's All-In-Wonder video cards
363           and is also available as a separate product.
364           This driver provides mouse pointer, left and right mouse buttons,
365           and maps all the other remote buttons to keypress events.
366 
367           To compile this driver as a module, choose M here: the module will be
368           called ati_remote2.
369 
370 config INPUT_KEYSPAN_REMOTE
371         tristate "Keyspan DMR USB remote control"
372         depends on USB_ARCH_HAS_HCD
373         select USB
374         help
375           Say Y here if you want to use a Keyspan DMR USB remote control.
376           Currently only the UIA-11 type of receiver has been tested.  The tag
377           on the receiver that connects to the USB port should have a P/N that
378           will tell you what type of DMR you have.  The UIA-10 type is not
379           supported at this time.  This driver maps all buttons to keypress
380           events.
381 
382           To compile this driver as a module, choose M here: the module will
383           be called keyspan_remote.
384 
385 config INPUT_KXTJ9
386         tristate "Kionix KXTJ9 tri-axis digital accelerometer"
387         depends on I2C
388         help
389           Say Y here to enable support for the Kionix KXTJ9 digital tri-axis
390           accelerometer.
391 
392           To compile this driver as a module, choose M here: the module will
393           be called kxtj9.
394 
395 config INPUT_KXTJ9_POLLED_MODE
396         bool "Enable polling mode support"
397         depends on INPUT_KXTJ9
398         select INPUT_POLLDEV
399         help
400           Say Y here if you need accelerometer to work in polling mode.
401 
402 config INPUT_POWERMATE
403         tristate "Griffin PowerMate and Contour Jog support"
404         depends on USB_ARCH_HAS_HCD
405         select USB
406         help
407           Say Y here if you want to use Griffin PowerMate or Contour Jog devices.
408           These are aluminum dials which can measure clockwise and anticlockwise
409           rotation.  The dial also acts as a pushbutton.  The base contains an LED
410           which can be instructed to pulse or to switch to a particular intensity.
411 
412           You can download userspace tools from
413           <http://sowerbutts.com/powermate/>.
414 
415           To compile this driver as a module, choose M here: the
416           module will be called powermate.
417 
418 config INPUT_YEALINK
419         tristate "Yealink usb-p1k voip phone"
420         depends on USB_ARCH_HAS_HCD
421         select USB
422         help
423           Say Y here if you want to enable keyboard and LCD functions of the
424           Yealink usb-p1k usb phones. The audio part is enabled by the generic
425           usb sound driver, so you might want to enable that as well.
426 
427           For information about how to use these additional functions, see
428           <file:Documentation/input/yealink.txt>.
429 
430           To compile this driver as a module, choose M here: the module will be
431           called yealink.
432 
433 config INPUT_CM109
434         tristate "C-Media CM109 USB I/O Controller"
435         depends on USB_ARCH_HAS_HCD
436         select USB
437         help
438           Say Y here if you want to enable keyboard and buzzer functions of the
439           C-Media CM109 usb phones. The audio part is enabled by the generic
440           usb sound driver, so you might want to enable that as well.
441 
442           To compile this driver as a module, choose M here: the module will be
443           called cm109.
444 
445 config INPUT_REGULATOR_HAPTIC
446         tristate "Regulator haptics support"
447         depends on REGULATOR
448         select INPUT_FF_MEMLESS
449         help
450           This option enables device driver support for the haptic controlled
451           by a regulator. This driver supports ff-memless interface
452           from input framework.
453 
454           To compile this driver as a module, choose M here: the
455           module will be called regulator-haptic.
456 
457 config INPUT_RETU_PWRBUTTON
458         tristate "Retu Power button Driver"
459         depends on MFD_RETU
460         help
461           Say Y here if you want to enable power key reporting via the
462           Retu chips found in Nokia Internet Tablets (770, N800, N810).
463 
464           To compile this driver as a module, choose M here. The module will
465           be called retu-pwrbutton.
466 
467 config INPUT_TPS65218_PWRBUTTON
468         tristate "TPS65218 Power button driver"
469         depends on (MFD_TPS65217 || MFD_TPS65218)
470         help
471           Say Y here if you want to enable power buttong reporting for
472           TPS65217 and TPS65218 Power Management IC devices.
473 
474           To compile this driver as a module, choose M here. The module will
475           be called tps65218-pwrbutton.
476 
477 config INPUT_AXP20X_PEK
478         tristate "X-Powers AXP20X power button driver"
479         depends on MFD_AXP20X
480         help
481           Say Y here if you want to enable power key reporting via the
482           AXP20X PMIC.
483 
484           To compile this driver as a module, choose M here. The module will
485           be called axp20x-pek.
486 
487 
488 config INPUT_TWL4030_PWRBUTTON
489         tristate "TWL4030 Power button Driver"
490         depends on TWL4030_CORE
491         help
492           Say Y here if you want to enable power key reporting via the
493           TWL4030 family of chips.
494 
495           To compile this driver as a module, choose M here. The module will
496           be called twl4030_pwrbutton.
497 
498 config INPUT_TWL4030_VIBRA
499         tristate "Support for TWL4030 Vibrator"
500         depends on TWL4030_CORE
501         select MFD_TWL4030_AUDIO
502         select INPUT_FF_MEMLESS
503         help
504           This option enables support for TWL4030 Vibrator Driver.
505 
506           To compile this driver as a module, choose M here. The module will
507           be called twl4030_vibra.
508 
509 config INPUT_TWL6040_VIBRA
510         tristate "Support for TWL6040 Vibrator"
511         depends on TWL6040_CORE
512         select INPUT_FF_MEMLESS
513         help
514           This option enables support for TWL6040 Vibrator Driver.
515 
516           To compile this driver as a module, choose M here. The module will
517           be called twl6040_vibra.
518 
519 config INPUT_UINPUT
520         tristate "User level driver support"
521         help
522           Say Y here if you want to support user level drivers for input
523           subsystem accessible under char device 10:223 - /dev/input/uinput.
524 
525           To compile this driver as a module, choose M here: the
526           module will be called uinput.
527 
528 config INPUT_SGI_BTNS
529         tristate "SGI Indy/O2 volume button interface"
530         depends on SGI_IP22 || SGI_IP32
531         select INPUT_POLLDEV
532         help
533           Say Y here if you want to support SGI Indy/O2 volume button interface.
534 
535           To compile this driver as a module, choose M here: the
536           module will be called sgi_btns.
537 
538 config HP_SDC_RTC
539         tristate "HP SDC Real Time Clock"
540         depends on (GSC || HP300) && SERIO
541         select HP_SDC
542         help
543           Say Y here if you want to support the built-in real time clock
544           of the HP SDC controller.
545 
546 config INPUT_PALMAS_PWRBUTTON
547         tristate "Palmas Power button Driver"
548         depends on MFD_PALMAS
549         help
550           Say Y here if you want to enable power key reporting via the
551           Palmas family of PMICs.
552 
553           To compile this driver as a module, choose M here. The module will
554           be called palmas_pwrbutton.
555 
556 config INPUT_PCF50633_PMU
557         tristate "PCF50633 PMU events"
558         depends on MFD_PCF50633
559         help
560          Say Y to include support for delivering  PMU events via  input
561          layer on NXP PCF50633.
562 
563 config INPUT_PCF8574
564         tristate "PCF8574 Keypad input device"
565         depends on I2C
566         help
567           Say Y here if you want to support a keypad connected via I2C
568           with a PCF8574.
569 
570           To compile this driver as a module, choose M here: the
571           module will be called pcf8574_keypad.
572 
573 config INPUT_PWM_BEEPER
574         tristate "PWM beeper support"
575         depends on PWM
576         help
577           Say Y here to get support for PWM based beeper devices.
578 
579           If unsure, say N.
580 
581           To compile this driver as a module, choose M here: the module will be
582           called pwm-beeper.
583 
584 config INPUT_GPIO_ROTARY_ENCODER
585         tristate "Rotary encoders connected to GPIO pins"
586         depends on GPIOLIB || COMPILE_TEST
587         help
588           Say Y here to add support for rotary encoders connected to GPIO lines.
589           Check file:Documentation/input/rotary-encoder.txt for more
590           information.
591 
592           To compile this driver as a module, choose M here: the
593           module will be called rotary_encoder.
594 
595 config INPUT_RB532_BUTTON
596         tristate "Mikrotik Routerboard 532 button interface"
597         depends on MIKROTIK_RB532
598         depends on GPIOLIB
599         select INPUT_POLLDEV
600         help
601           Say Y here if you want support for the S1 button built into
602           Mikrotik's Routerboard 532.
603 
604           To compile this driver as a module, choose M here: the
605           module will be called rb532_button.
606 
607 config INPUT_DA9052_ONKEY
608         tristate "Dialog DA9052/DA9053 Onkey"
609         depends on PMIC_DA9052
610         help
611           Support the ONKEY of Dialog DA9052 PMICs as an input device
612           reporting power button status.
613 
614           To compile this driver as a module, choose M here: the
615           module will be called da9052_onkey.
616 
617 config INPUT_DA9055_ONKEY
618         tristate "Dialog Semiconductor DA9055 ONKEY"
619         depends on MFD_DA9055
620         help
621           Support the ONKEY of DA9055 PMICs as an input device
622           reporting power button status.
623 
624           To compile this driver as a module, choose M here: the module
625           will be called da9055_onkey.
626 
627 config INPUT_DA9063_ONKEY
628         tristate "Dialog DA9063/62/61 OnKey"
629         depends on MFD_DA9063 || MFD_DA9062
630         help
631           Support the ONKEY of Dialog DA9063, DA9062 and DA9061 Power
632           Management ICs as an input device capable of reporting the
633           power button status.
634 
635           To compile this driver as a module, choose M here: the module
636           will be called da9063_onkey.
637 
638 config INPUT_DM355EVM
639         tristate "TI DaVinci DM355 EVM Keypad and IR Remote"
640         depends on MFD_DM355EVM_MSP
641         select INPUT_SPARSEKMAP
642         help
643           Supports the pushbuttons and IR remote used with
644           the DM355 EVM board.
645 
646           To compile this driver as a module, choose M here: the
647           module will be called dm355evm_keys.
648 
649 config INPUT_BFIN_ROTARY
650         tristate "Blackfin Rotary support"
651         depends on BF54x || BF52x
652         help
653           Say Y here if you want to use the Blackfin Rotary.
654 
655           To compile this driver as a module, choose M here: the
656           module will be called bfin-rotary.
657 
658 config 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 
668 config 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 
678 config 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 
695 config 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 
705 config 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 
715 config 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 
725 config 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 
739 config 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 
749 config 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 
762 config 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 
772 config 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 
782 config 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 
792 config 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 
804 config 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 
815 config 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 
826 config 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 
835 endif

This page was automatically generated by LXR 0.3.1 (source).  •  Linux is a registered trademark of Linus Torvalds  •  Contact us