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_IXP4XX_BEEPER
 296         tristate "IXP4XX Beeper support"
 297         depends on ARCH_IXP4XX
 298         help
 299           If you say yes here, you can connect a beeper to the
 300           ixp4xx gpio pins. This is used by the LinkSys NSLU2.
 301
 302           If unsure, say Y.
 303
 304           To compile this driver as a module, choose M here: the
 305           module will be called ixp4xx-beeper.
 306
 307 config INPUT_COBALT_BTNS
 308         tristate "Cobalt button interface"
 309         depends on MIPS_COBALT
 310         select INPUT_POLLDEV
 311         help
 312           Say Y here if you want to support MIPS Cobalt button interface.
 313
 314           To compile this driver as a module, choose M here: the
 315           module will be called cobalt_btns.
 316
 317 config INPUT_WISTRON_BTNS
 318         tristate "x86 Wistron laptop button interface"
 319         depends on X86_32
 320         select INPUT_POLLDEV
 321         select INPUT_SPARSEKMAP
 322         select NEW_LEDS
 323         select LEDS_CLASS
 324         select CHECK_SIGNATURE
 325         help
 326           Say Y here for support of Wistron laptop button interfaces, used on
 327           laptops of various brands, including Acer and Fujitsu-Siemens. If
 328           available, mail and wifi LEDs will be controllable via /sys/class/leds.
 329
 330           To compile this driver as a module, choose M here: the module will
 331           be called wistron_btns.
 332
 333 config INPUT_ATLAS_BTNS
 334         tristate "x86 Atlas button interface"
 335         depends on X86 && ACPI
 336         help
 337           Say Y here for support of Atlas wallmount touchscreen buttons.
 338           The events will show up as scancodes F1 through F9 via evdev.
 339
 340           To compile this driver as a module, choose M here: the module will
 341           be called atlas_btns.
 342
 343 config INPUT_ATI_REMOTE2
 344         tristate "ATI / Philips USB RF remote control"
 345         depends on USB_ARCH_HAS_HCD
 346         select USB
 347         help
 348           Say Y here if you want to use an ATI or Philips USB RF remote control.
 349           These are RF remotes with USB receivers.
 350           ATI Remote Wonder II comes with some ATI's All-In-Wonder video cards
 351           and is also available as a separate product.
 352           This driver provides mouse pointer, left and right mouse buttons,
 353           and maps all the other remote buttons to keypress events.
 354
 355           To compile this driver as a module, choose M here: the module will be
 356           called ati_remote2.
 357
 358 config INPUT_KEYSPAN_REMOTE
 359         tristate "Keyspan DMR USB remote control"
 360         depends on USB_ARCH_HAS_HCD
 361         select USB
 362         help
 363           Say Y here if you want to use a Keyspan DMR USB remote control.
 364           Currently only the UIA-11 type of receiver has been tested.  The tag
 365           on the receiver that connects to the USB port should have a P/N that
 366           will tell you what type of DMR you have.  The UIA-10 type is not
 367           supported at this time.  This driver maps all buttons to keypress
 368           events.
 369
 370           To compile this driver as a module, choose M here: the module will
 371           be called keyspan_remote.
 372
 373 config INPUT_KXTJ9
 374         tristate "Kionix KXTJ9 tri-axis digital accelerometer"
 375         depends on I2C
 376         help
 377           Say Y here to enable support for the Kionix KXTJ9 digital tri-axis
 378           accelerometer.
 379
 380           To compile this driver as a module, choose M here: the module will
 381           be called kxtj9.
 382
 383 config INPUT_KXTJ9_POLLED_MODE
 384         bool "Enable polling mode support"
 385         depends on INPUT_KXTJ9
 386         select INPUT_POLLDEV
 387         help
 388           Say Y here if you need accelerometer to work in polling mode.
 389
 390 config INPUT_POWERMATE
 391         tristate "Griffin PowerMate and Contour Jog support"
 392         depends on USB_ARCH_HAS_HCD
 393         select USB
 394         help
 395           Say Y here if you want to use Griffin PowerMate or Contour Jog devices.
 396           These are aluminum dials which can measure clockwise and anticlockwise
 397           rotation.  The dial also acts as a pushbutton.  The base contains an LED
 398           which can be instructed to pulse or to switch to a particular intensity.
 399
 400           You can download userspace tools from
 401           <http://sowerbutts.com/powermate/>.
 402
 403           To compile this driver as a module, choose M here: the
 404           module will be called powermate.
 405
 406 config INPUT_YEALINK
 407         tristate "Yealink usb-p1k voip phone"
 408         depends on USB_ARCH_HAS_HCD
 409         select USB
 410         help
 411           Say Y here if you want to enable keyboard and LCD functions of the
 412           Yealink usb-p1k usb phones. The audio part is enabled by the generic
 413           usb sound driver, so you might want to enable that as well.
 414
 415           For information about how to use these additional functions, see
 416           <file:Documentation/input/yealink.txt>.
 417
 418           To compile this driver as a module, choose M here: the module will be
 419           called yealink.
 420
 421 config INPUT_CM109
 422         tristate "C-Media CM109 USB I/O Controller"
 423         depends on USB_ARCH_HAS_HCD
 424         select USB
 425         help
 426           Say Y here if you want to enable keyboard and buzzer functions of the
 427           C-Media CM109 usb phones. The audio part is enabled by the generic
 428           usb sound driver, so you might want to enable that as well.
 429
 430           To compile this driver as a module, choose M here: the module will be
 431           called cm109.
 432
 433 config INPUT_REGULATOR_HAPTIC
 434         tristate "Regulator haptics support"
 435         depends on REGULATOR
 436         select INPUT_FF_MEMLESS
 437         help
 438           This option enables device driver support for the haptic controlled
 439           by a regulator. This driver supports ff-memless interface
 440           from input framework.
 441
 442           To compile this driver as a module, choose M here: the
 443           module will be called regulator-haptic.
 444
 445 config INPUT_RETU_PWRBUTTON
 446         tristate "Retu Power button Driver"
 447         depends on MFD_RETU
 448         help
 449           Say Y here if you want to enable power key reporting via the
 450           Retu chips found in Nokia Internet Tablets (770, N800, N810).
 451
 452           To compile this driver as a module, choose M here. The module will
 453           be called retu-pwrbutton.
 454
 455 config INPUT_TPS65218_PWRBUTTON
 456         tristate "TPS65218 Power button driver"
 457         depends on MFD_TPS65218
 458         help
 459           Say Y here if you want to enable power buttong reporting for
 460           the TPS65218 Power Management IC device.
 461
 462           To compile this driver as a module, choose M here. The module will
 463           be called tps65218-pwrbutton.
 464
 465 config INPUT_AXP20X_PEK
 466         tristate "X-Powers AXP20X power button driver"
 467         depends on MFD_AXP20X
 468         help
 469           Say Y here if you want to enable power key reporting via the
 470           AXP20X PMIC.
 471
 472           To compile this driver as a module, choose M here. The module will
 473           be called axp20x-pek.
 474
 475
 476 config INPUT_TWL4030_PWRBUTTON
 477         tristate "TWL4030 Power button Driver"
 478         depends on TWL4030_CORE
 479         help
 480           Say Y here if you want to enable power key reporting via the
 481           TWL4030 family of chips.
 482
 483           To compile this driver as a module, choose M here. The module will
 484           be called twl4030_pwrbutton.
 485
 486 config INPUT_TWL4030_VIBRA
 487         tristate "Support for TWL4030 Vibrator"
 488         depends on TWL4030_CORE
 489         select MFD_TWL4030_AUDIO
 490         select INPUT_FF_MEMLESS
 491         help
 492           This option enables support for TWL4030 Vibrator Driver.
 493
 494           To compile this driver as a module, choose M here. The module will
 495           be called twl4030_vibra.
 496
 497 config INPUT_TWL6040_VIBRA
 498         tristate "Support for TWL6040 Vibrator"
 499         depends on TWL6040_CORE
 500         select INPUT_FF_MEMLESS
 501         help
 502           This option enables support for TWL6040 Vibrator Driver.
 503
 504           To compile this driver as a module, choose M here. The module will
 505           be called twl6040_vibra.
 506
 507 config INPUT_UINPUT
 508         tristate "User level driver support"
 509         help
 510           Say Y here if you want to support user level drivers for input
 511           subsystem accessible under char device 10:223 - /dev/input/uinput.
 512
 513           To compile this driver as a module, choose M here: the
 514           module will be called uinput.
 515
 516 config INPUT_SGI_BTNS
 517         tristate "SGI Indy/O2 volume button interface"
 518         depends on SGI_IP22 || SGI_IP32
 519         select INPUT_POLLDEV
 520         help
 521           Say Y here if you want to support SGI Indy/O2 volume button interface.
 522
 523           To compile this driver as a module, choose M here: the
 524           module will be called sgi_btns.
 525
 526 config HP_SDC_RTC
 527         tristate "HP SDC Real Time Clock"
 528         depends on (GSC || HP300) && SERIO
 529         select HP_SDC
 530         help
 531           Say Y here if you want to support the built-in real time clock
 532           of the HP SDC controller.
 533
 534 config INPUT_PALMAS_PWRBUTTON
 535         tristate "Palmas Power button Driver"
 536         depends on MFD_PALMAS
 537         help
 538           Say Y here if you want to enable power key reporting via the
 539           Palmas family of PMICs.
 540
 541           To compile this driver as a module, choose M here. The module will
 542           be called palmas_pwrbutton.
 543
 544 config INPUT_PCF50633_PMU
 545         tristate "PCF50633 PMU events"
 546         depends on MFD_PCF50633
 547         help
 548          Say Y to include support for delivering  PMU events via  input
 549          layer on NXP PCF50633.
 550
 551 config INPUT_PCF8574
 552         tristate "PCF8574 Keypad input device"
 553         depends on I2C
 554         help
 555           Say Y here if you want to support a keypad connected via I2C
 556           with a PCF8574.
 557
 558           To compile this driver as a module, choose M here: the
 559           module will be called pcf8574_keypad.
 560
 561 config INPUT_PWM_BEEPER
 562         tristate "PWM beeper support"
 563         depends on PWM
 564         help
 565           Say Y here to get support for PWM based beeper devices.
 566
 567           If unsure, say N.
 568
 569           To compile this driver as a module, choose M here: the module will be
 570           called pwm-beeper.
 571
 572 config INPUT_GPIO_ROTARY_ENCODER
 573         tristate "Rotary encoders connected to GPIO pins"
 574         depends on GPIOLIB || COMPILE_TEST
 575         help
 576           Say Y here to add support for rotary encoders connected to GPIO lines.
 577           Check file:Documentation/input/rotary-encoder.txt for more
 578           information.
 579
 580           To compile this driver as a module, choose M here: the
 581           module will be called rotary_encoder.
 582
 583 config INPUT_RB532_BUTTON
 584         tristate "Mikrotik Routerboard 532 button interface"
 585         depends on MIKROTIK_RB532
 586         depends on GPIOLIB
 587         select INPUT_POLLDEV
 588         help
 589           Say Y here if you want support for the S1 button built into
 590           Mikrotik's Routerboard 532.
 591
 592           To compile this driver as a module, choose M here: the
 593           module will be called rb532_button.
 594
 595 config INPUT_DA9052_ONKEY
 596         tristate "Dialog DA9052/DA9053 Onkey"
 597         depends on PMIC_DA9052
 598         help
 599           Support the ONKEY of Dialog DA9052 PMICs as an input device
 600           reporting power button status.
 601
 602           To compile this driver as a module, choose M here: the
 603           module will be called da9052_onkey.
 604
 605 config INPUT_DA9055_ONKEY
 606         tristate "Dialog Semiconductor DA9055 ONKEY"
 607         depends on MFD_DA9055
 608         help
 609           Support the ONKEY of DA9055 PMICs as an input device
 610           reporting power button status.
 611
 612           To compile this driver as a module, choose M here: the module
 613           will be called da9055_onkey.
 614
 615 config INPUT_DA9063_ONKEY
 616         tristate "Dialog DA9062/63 OnKey"
 617         depends on MFD_DA9063 || MFD_DA9062
 618         help
 619           Support the ONKEY of Dialog DA9063 and DA9062 Power Management ICs
 620           as an input device capable of reporting the power button status.
 621
 622           To compile this driver as a module, choose M here: the module
 623           will be called da9063_onkey.
 624
 625 config INPUT_DM355EVM
 626         tristate "TI DaVinci DM355 EVM Keypad and IR Remote"
 627         depends on MFD_DM355EVM_MSP
 628         select INPUT_SPARSEKMAP
 629         help
 630           Supports the pushbuttons and IR remote used with
 631           the DM355 EVM board.
 632
 633           To compile this driver as a module, choose M here: the
 634           module will be called dm355evm_keys.
 635
 636 config INPUT_BFIN_ROTARY
 637         tristate "Blackfin Rotary support"
 638         depends on BF54x || BF52x
 639         help
 640           Say Y here if you want to use the Blackfin Rotary.
 641
 642           To compile this driver as a module, choose M here: the
 643           module will be called bfin-rotary.
 644
 645 config INPUT_WM831X_ON
 646         tristate "WM831X ON pin"
 647         depends on MFD_WM831X
 648         help
 649           Support the ON pin of WM831X PMICs as an input device
 650           reporting power button status.
 651
 652           To compile this driver as a module, choose M here: the module
 653           will be called wm831x_on.
 654
 655 config INPUT_PCAP
 656         tristate "Motorola EZX PCAP misc input events"
 657         depends on EZX_PCAP
 658         help
 659           Say Y here if you want to use Power key and Headphone button
 660           on Motorola EZX phones.
 661
 662           To compile this driver as a module, choose M here: the
 663           module will be called pcap_keys.
 664
 665 config INPUT_ADXL34X
 666         tristate "Analog Devices ADXL34x Three-Axis Digital Accelerometer"
 667         default n
 668         help
 669           Say Y here if you have a Accelerometer interface using the
 670           ADXL345/6 controller, and your board-specific initialization
 671           code includes that in its table of devices.
 672
 673           This driver can use either I2C or SPI communication to the
 674           ADXL345/6 controller.  Select the appropriate method for
 675           your system.
 676
 677           If unsure, say N (but it's safe to say "Y").
 678
 679           To compile this driver as a module, choose M here: the
 680           module will be called adxl34x.
 681
 682 config INPUT_ADXL34X_I2C
 683         tristate "support I2C bus connection"
 684         depends on INPUT_ADXL34X && I2C
 685         default y
 686         help
 687           Say Y here if you have ADXL345/6 hooked to an I2C bus.
 688
 689           To compile this driver as a module, choose M here: the
 690           module will be called adxl34x-i2c.
 691
 692 config INPUT_ADXL34X_SPI
 693         tristate "support SPI bus connection"
 694         depends on INPUT_ADXL34X && SPI
 695         default y
 696         help
 697           Say Y here if you have ADXL345/6 hooked to a SPI bus.
 698
 699           To compile this driver as a module, choose M here: the
 700           module will be called adxl34x-spi.
 701
 702 config INPUT_IMS_PCU
 703         tristate "IMS Passenger Control Unit driver"
 704         depends on USB
 705         depends on LEDS_CLASS
 706         help
 707           Say Y here if you have system with IMS Rave Passenger Control Unit.
 708
 709           To compile this driver as a module, choose M here: the module will be
 710           called ims_pcu.
 711
 712 config INPUT_CMA3000
 713         tristate "VTI CMA3000 Tri-axis accelerometer"
 714         help
 715           Say Y here if you want to use VTI CMA3000_D0x Accelerometer
 716           driver
 717
 718           This driver currently only supports I2C interface to the
 719           controller. Also select the I2C method.
 720
 721           If unsure, say N
 722
 723           To compile this driver as a module, choose M here: the
 724           module will be called cma3000_d0x.
 725
 726 config INPUT_CMA3000_I2C
 727         tristate "Support I2C bus connection"
 728         depends on INPUT_CMA3000 && I2C
 729         help
 730           Say Y here if you want to use VTI CMA3000_D0x Accelerometer
 731           through I2C interface.
 732
 733           To compile this driver as a module, choose M here: the
 734           module will be called cma3000_d0x_i2c.
 735
 736 config INPUT_XEN_KBDDEV_FRONTEND
 737         tristate "Xen virtual keyboard and mouse support"
 738         depends on XEN
 739         default y
 740         select XEN_XENBUS_FRONTEND
 741         help
 742           This driver implements the front-end of the Xen virtual
 743           keyboard and mouse device driver.  It communicates with a back-end
 744           in another domain.
 745
 746           To compile this driver as a module, choose M here: the
 747           module will be called xen-kbdfront.
 748
 749 config INPUT_SIRFSOC_ONKEY
 750         tristate "CSR SiRFSoC power on/off/suspend key support"
 751         depends on ARCH_SIRF && OF
 752         default y
 753         help
 754           Say Y here if you want to support for the SiRFSoC power on/off/suspend key
 755           in Linux, after you press the onkey, system will suspend.
 756
 757           If unsure, say N.
 758
 759 config INPUT_IDEAPAD_SLIDEBAR
 760         tristate "IdeaPad Laptop Slidebar"
 761         depends on INPUT
 762         depends on SERIO_I8042
 763         help
 764           Say Y here if you have an IdeaPad laptop with a slidebar.
 765
 766           To compile this driver as a module, choose M here: the
 767           module will be called ideapad_slidebar.
 768
 769 config INPUT_SOC_BUTTON_ARRAY
 770         tristate "Windows-compatible SoC Button Array"
 771         depends on KEYBOARD_GPIO
 772         help
 773           Say Y here if you have a SoC-based tablet that originally
 774           runs Windows 8.
 775
 776           To compile this driver as a module, choose M here: the
 777           module will be called soc_button_array.
 778
 779 config INPUT_DRV260X_HAPTICS
 780         tristate "TI DRV260X haptics support"
 781         depends on INPUT && I2C
 782         depends on GPIOLIB || COMPILE_TEST
 783         select INPUT_FF_MEMLESS
 784         select REGMAP_I2C
 785         help
 786           Say Y to enable support for the TI DRV260X haptics driver.
 787
 788           To compile this driver as a module, choose M here: the
 789           module will be called drv260x-haptics.
 790
 791 config INPUT_DRV2665_HAPTICS
 792         tristate "TI DRV2665 haptics support"
 793         depends on INPUT && I2C
 794         select INPUT_FF_MEMLESS
 795         select REGMAP_I2C
 796         help
 797           Say Y to enable support for the TI DRV2665 haptics driver.
 798
 799           To compile this driver as a module, choose M here: the
 800           module will be called drv2665-haptics.
 801
 802 config INPUT_DRV2667_HAPTICS
 803         tristate "TI DRV2667 haptics support"
 804         depends on INPUT && I2C
 805         select INPUT_FF_MEMLESS
 806         select REGMAP_I2C
 807         help
 808           Say Y to enable support for the TI DRV2667 haptics driver.
 809
 810           To compile this driver as a module, choose M here: the
 811           module will be called drv2667-haptics.
 812
 813 config INPUT_HISI_POWERKEY
 814         tristate "Hisilicon PMIC ONKEY support"
 815         depends on ARCH_HISI || COMPILE_TEST
 816         help
 817           Say Y to enable support for PMIC ONKEY.
 818
 819           To compile this driver as a module, choose M here: the
 820           module will be called hisi_powerkey.
 821
 822 endif