drivers/input/misc/Kconfig

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