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_BMA150
  86         tristate "BMA150/SMB380 acceleration sensor support"
  87         depends on I2C
  88         select INPUT_POLLDEV
  89         help
  90           Say Y here if you have Bosch Sensortec's BMA150 or SMB380
  91           acceleration sensor hooked to an I2C bus.
  92
  93           To compile this driver as a module, choose M here: the
  94           module will be called bma150.
  95
  96 config INPUT_PCSPKR
  97         tristate "PC Speaker support"
  98         depends on PCSPKR_PLATFORM
  99         help
 100           Say Y here if you want the standard PC Speaker to be used for
 101           bells and whistles.
 102
 103           If unsure, say Y.
 104
 105           To compile this driver as a module, choose M here: the
 106           module will be called pcspkr.
 107
 108 config INPUT_PM8XXX_VIBRATOR
 109         tristate "Qualcomm PM8XXX vibrator support"
 110         depends on MFD_PM8XXX
 111         select INPUT_FF_MEMLESS
 112         help
 113           This option enables device driver support for the vibrator
 114           on Qualcomm PM8xxx chip. This driver supports ff-memless interface
 115           from input framework.
 116
 117           To compile this driver as module, choose M here: the
 118           module will be called pm8xxx-vibrator.
 119
 120 config INPUT_PMIC8XXX_PWRKEY
 121         tristate "PMIC8XXX power key support"
 122         depends on MFD_PM8XXX
 123         help
 124           Say Y here if you want support for the PMIC8XXX power key.
 125
 126           If unsure, say N.
 127
 128           To compile this driver as a module, choose M here: the
 129           module will be called pmic8xxx-pwrkey.
 130
 131 config INPUT_SPARCSPKR
 132         tristate "SPARC Speaker support"
 133         depends on PCI && SPARC64
 134         help
 135           Say Y here if you want the standard Speaker on Sparc PCI systems
 136           to be used for 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 sparcspkr.
 142
 143 config INPUT_M68K_BEEP
 144         tristate "M68k Beeper support"
 145         depends on M68K
 146
 147 config INPUT_MAX8925_ONKEY
 148         tristate "MAX8925 ONKEY support"
 149         depends on MFD_MAX8925
 150         help
 151           Support the ONKEY of MAX8925 PMICs as an input device
 152           reporting power button status.
 153
 154           To compile this driver as a module, choose M here: the module
 155           will be called max8925_onkey.
 156
 157 config INPUT_MAX8997_HAPTIC
 158         tristate "MAXIM MAX8997 haptic controller support"
 159         depends on HAVE_PWM && MFD_MAX8997
 160         select INPUT_FF_MEMLESS
 161         help
 162           This option enables device driver support for the haptic controller
 163           on MAXIM MAX8997 chip. This driver supports ff-memless interface
 164           from input framework.
 165
 166           To compile this driver as module, choose M here: the
 167           module will be called max8997-haptic.
 168
 169 config INPUT_MC13783_PWRBUTTON
 170         tristate "MC13783 ON buttons"
 171         depends on MFD_MC13783
 172         help
 173           Support the ON buttons of MC13783 PMIC as an input device
 174           reporting power button status.
 175
 176           To compile this driver as a module, choose M here: the module
 177           will be called mc13783-pwrbutton.
 178
 179 config INPUT_MMA8450
 180         tristate "MMA8450 - Freescale's 3-Axis, 8/12-bit Digital Accelerometer"
 181         depends on I2C
 182         select INPUT_POLLDEV
 183         help
 184           Say Y here if you want to support Freescale's MMA8450 Accelerometer
 185           through I2C interface.
 186
 187           To compile this driver as a module, choose M here: the
 188           module will be called mma8450.
 189
 190 config INPUT_MPU3050
 191         tristate "MPU3050 Triaxial gyroscope sensor"
 192         depends on I2C
 193         help
 194           Say Y here if you want to support InvenSense MPU3050
 195           connected via an I2C bus.
 196
 197           To compile this driver as a module, choose M here: the
 198           module will be called mpu3050.
 199
 200 config INPUT_APANEL
 201         tristate "Fujitsu Lifebook Application Panel buttons"
 202         depends on X86 && I2C && LEDS_CLASS
 203         select INPUT_POLLDEV
 204         select CHECK_SIGNATURE
 205         help
 206          Say Y here for support of the Application Panel buttons, used on
 207          Fujitsu Lifebook. These are attached to the mainboard through
 208          an SMBus interface managed by the I2C Intel ICH (i801) driver,
 209          which you should also build for this kernel.
 210
 211          To compile this driver as a module, choose M here: the module will
 212          be called apanel.
 213
 214 config INPUT_GP2A
 215         tristate "Sharp GP2AP002A00F I2C Proximity/Opto sensor driver"
 216         depends on I2C
 217         depends on GPIOLIB
 218         help
 219           Say Y here if you have a Sharp GP2AP002A00F proximity/als combo-chip
 220           hooked to an I2C bus.
 221
 222           To compile this driver as a module, choose M here: the
 223           module will be called gp2ap002a00f.
 224
 225 config INPUT_GPIO_TILT_POLLED
 226         tristate "Polled GPIO tilt switch"
 227         depends on GPIOLIB
 228         select INPUT_POLLDEV
 229         help
 230           This driver implements support for tilt switches connected
 231           to GPIO pins that are not capable of generating interrupts.
 232
 233           The list of gpios to use and the mapping of their states
 234           to specific angles is done via platform data.
 235
 236           To compile this driver as a module, choose M here: the
 237           module will be called gpio_tilt_polled.
 238
 239 config INPUT_IXP4XX_BEEPER
 240         tristate "IXP4XX Beeper support"
 241         depends on ARCH_IXP4XX
 242         help
 243           If you say yes here, you can connect a beeper to the
 244           ixp4xx gpio pins. This is used by the LinkSys NSLU2.
 245
 246           If unsure, say Y.
 247
 248           To compile this driver as a module, choose M here: the
 249           module will be called ixp4xx-beeper.
 250
 251 config INPUT_COBALT_BTNS
 252         tristate "Cobalt button interface"
 253         depends on MIPS_COBALT
 254         select INPUT_POLLDEV
 255         help
 256           Say Y here if you want to support MIPS Cobalt button interface.
 257
 258           To compile this driver as a module, choose M here: the
 259           module will be called cobalt_btns.
 260
 261 config INPUT_WISTRON_BTNS
 262         tristate "x86 Wistron laptop button interface"
 263         depends on X86 && !X86_64
 264         select INPUT_POLLDEV
 265         select INPUT_SPARSEKMAP
 266         select NEW_LEDS
 267         select LEDS_CLASS
 268         select CHECK_SIGNATURE
 269         help
 270           Say Y here for support of Wistron laptop button interfaces, used on
 271           laptops of various brands, including Acer and Fujitsu-Siemens. If
 272           available, mail and wifi LEDs will be controllable via /sys/class/leds.
 273
 274           To compile this driver as a module, choose M here: the module will
 275           be called wistron_btns.
 276
 277 config INPUT_ATLAS_BTNS
 278         tristate "x86 Atlas button interface"
 279         depends on X86 && ACPI
 280         help
 281           Say Y here for support of Atlas wallmount touchscreen buttons.
 282           The events will show up as scancodes F1 through F9 via evdev.
 283
 284           To compile this driver as a module, choose M here: the module will
 285           be called atlas_btns.
 286
 287 config INPUT_ATI_REMOTE2
 288         tristate "ATI / Philips USB RF remote control"
 289         depends on USB_ARCH_HAS_HCD
 290         select USB
 291         help
 292           Say Y here if you want to use an ATI or Philips USB RF remote control.
 293           These are RF remotes with USB receivers.
 294           ATI Remote Wonder II comes with some ATI's All-In-Wonder video cards
 295           and is also available as a separate product.
 296           This driver provides mouse pointer, left and right mouse buttons,
 297           and maps all the other remote buttons to keypress events.
 298
 299           To compile this driver as a module, choose M here: the module will be
 300           called ati_remote2.
 301
 302 config INPUT_KEYSPAN_REMOTE
 303         tristate "Keyspan DMR USB remote control"
 304         depends on USB_ARCH_HAS_HCD
 305         select USB
 306         help
 307           Say Y here if you want to use a Keyspan DMR USB remote control.
 308           Currently only the UIA-11 type of receiver has been tested.  The tag
 309           on the receiver that connects to the USB port should have a P/N that
 310           will tell you what type of DMR you have.  The UIA-10 type is not
 311           supported at this time.  This driver maps all buttons to keypress
 312           events.
 313
 314           To compile this driver as a module, choose M here: the module will
 315           be called keyspan_remote.
 316
 317 config INPUT_KXTJ9
 318         tristate "Kionix KXTJ9 tri-axis digital accelerometer"
 319         depends on I2C
 320         help
 321           Say Y here to enable support for the Kionix KXTJ9 digital tri-axis
 322           accelerometer.
 323
 324           To compile this driver as a module, choose M here: the module will
 325           be called kxtj9.
 326
 327 config INPUT_KXTJ9_POLLED_MODE
 328         bool "Enable polling mode support"
 329         depends on INPUT_KXTJ9
 330         select INPUT_POLLDEV
 331         help
 332           Say Y here if you need accelerometer to work in polling mode.
 333
 334 config INPUT_POWERMATE
 335         tristate "Griffin PowerMate and Contour Jog support"
 336         depends on USB_ARCH_HAS_HCD
 337         select USB
 338         help
 339           Say Y here if you want to use Griffin PowerMate or Contour Jog devices.
 340           These are aluminum dials which can measure clockwise and anticlockwise
 341           rotation.  The dial also acts as a pushbutton.  The base contains an LED
 342           which can be instructed to pulse or to switch to a particular intensity.
 343
 344           You can download userspace tools from
 345           <http://sowerbutts.com/powermate/>.
 346
 347           To compile this driver as a module, choose M here: the
 348           module will be called powermate.
 349
 350 config INPUT_YEALINK
 351         tristate "Yealink usb-p1k voip phone"
 352         depends on USB_ARCH_HAS_HCD
 353         select USB
 354         help
 355           Say Y here if you want to enable keyboard and LCD functions of the
 356           Yealink usb-p1k usb phones. The audio part is enabled by the generic
 357           usb sound driver, so you might want to enable that as well.
 358
 359           For information about how to use these additional functions, see
 360           <file:Documentation/input/yealink.txt>.
 361
 362           To compile this driver as a module, choose M here: the module will be
 363           called yealink.
 364
 365 config INPUT_CM109
 366         tristate "C-Media CM109 USB I/O Controller"
 367         depends on USB_ARCH_HAS_HCD
 368         select USB
 369         help
 370           Say Y here if you want to enable keyboard and buzzer functions of the
 371           C-Media CM109 usb phones. The audio part is enabled by the generic
 372           usb sound driver, so you might want to enable that as well.
 373
 374           To compile this driver as a module, choose M here: the module will be
 375           called cm109.
 376
 377 config INPUT_RETU_PWRBUTTON
 378         tristate "Retu Power button Driver"
 379         depends on MFD_RETU
 380         help
 381           Say Y here if you want to enable power key reporting via the
 382           Retu chips found in Nokia Internet Tablets (770, N800, N810).
 383
 384           To compile this driver as a module, choose M here. The module will
 385           be called retu-pwrbutton.
 386
 387 config INPUT_TWL4030_PWRBUTTON
 388         tristate "TWL4030 Power button Driver"
 389         depends on TWL4030_CORE
 390         help
 391           Say Y here if you want to enable power key reporting via the
 392           TWL4030 family of chips.
 393
 394           To compile this driver as a module, choose M here. The module will
 395           be called twl4030_pwrbutton.
 396
 397 config INPUT_TWL4030_VIBRA
 398         tristate "Support for TWL4030 Vibrator"
 399         depends on TWL4030_CORE
 400         select MFD_TWL4030_AUDIO
 401         select INPUT_FF_MEMLESS
 402         help
 403           This option enables support for TWL4030 Vibrator Driver.
 404
 405           To compile this driver as a module, choose M here. The module will
 406           be called twl4030_vibra.
 407
 408 config INPUT_TWL6040_VIBRA
 409         tristate "Support for TWL6040 Vibrator"
 410         depends on TWL6040_CORE
 411         select INPUT_FF_MEMLESS
 412         help
 413           This option enables support for TWL6040 Vibrator Driver.
 414
 415           To compile this driver as a module, choose M here. The module will
 416           be called twl6040_vibra.
 417
 418 config INPUT_UINPUT
 419         tristate "User level driver support"
 420         help
 421           Say Y here if you want to support user level drivers for input
 422           subsystem accessible under char device 10:223 - /dev/input/uinput.
 423
 424           To compile this driver as a module, choose M here: the
 425           module will be called uinput.
 426
 427 config INPUT_SGI_BTNS
 428         tristate "SGI Indy/O2 volume button interface"
 429         depends on SGI_IP22 || SGI_IP32
 430         select INPUT_POLLDEV
 431         help
 432           Say Y here if you want to support SGI Indy/O2 volume button interface.
 433
 434           To compile this driver as a module, choose M here: the
 435           module will be called sgi_btns.
 436
 437 config HP_SDC_RTC
 438         tristate "HP SDC Real Time Clock"
 439         depends on (GSC || HP300) && SERIO
 440         select HP_SDC
 441         help
 442           Say Y here if you want to support the built-in real time clock
 443           of the HP SDC controller.
 444
 445 config INPUT_PCF50633_PMU
 446         tristate "PCF50633 PMU events"
 447         depends on MFD_PCF50633
 448         help
 449          Say Y to include support for delivering  PMU events via  input
 450          layer on NXP PCF50633.
 451
 452 config INPUT_PCF8574
 453         tristate "PCF8574 Keypad input device"
 454         depends on I2C
 455         help
 456           Say Y here if you want to support a keypad connected via I2C
 457           with a PCF8574.
 458
 459           To compile this driver as a module, choose M here: the
 460           module will be called pcf8574_keypad.
 461
 462 config INPUT_PWM_BEEPER
 463         tristate "PWM beeper support"
 464         depends on HAVE_PWM || PWM
 465         help
 466           Say Y here to get support for PWM based beeper devices.
 467
 468           If unsure, say N.
 469
 470           To compile this driver as a module, choose M here: the module will be
 471           called pwm-beeper.
 472
 473 config INPUT_GPIO_ROTARY_ENCODER
 474         tristate "Rotary encoders connected to GPIO pins"
 475         depends on GPIOLIB
 476         help
 477           Say Y here to add support for rotary encoders connected to GPIO lines.
 478           Check file:Documentation/input/rotary-encoder.txt for more
 479           information.
 480
 481           To compile this driver as a module, choose M here: the
 482           module will be called rotary_encoder.
 483
 484 config INPUT_RB532_BUTTON
 485         tristate "Mikrotik Routerboard 532 button interface"
 486         depends on MIKROTIK_RB532
 487         depends on GPIOLIB
 488         select INPUT_POLLDEV
 489         help
 490           Say Y here if you want support for the S1 button built into
 491           Mikrotik's Routerboard 532.
 492
 493           To compile this driver as a module, choose M here: the
 494           module will be called rb532_button.
 495
 496 config INPUT_DA9052_ONKEY
 497         tristate "Dialog DA9052/DA9053 Onkey"
 498         depends on PMIC_DA9052
 499         help
 500           Support the ONKEY of Dialog DA9052 PMICs as an input device
 501           reporting power button status.
 502
 503           To compile this driver as a module, choose M here: the
 504           module will be called da9052_onkey.
 505
 506 config INPUT_DA9055_ONKEY
 507         tristate "Dialog Semiconductor DA9055 ONKEY"
 508         depends on MFD_DA9055
 509         help
 510           Support the ONKEY of DA9055 PMICs as an input device
 511           reporting power button status.
 512
 513           To compile this driver as a module, choose M here: the module
 514           will be called da9055_onkey.
 515
 516 config INPUT_DM355EVM
 517         tristate "TI DaVinci DM355 EVM Keypad and IR Remote"
 518         depends on MFD_DM355EVM_MSP
 519         select INPUT_SPARSEKMAP
 520         help
 521           Supports the pushbuttons and IR remote used with
 522           the DM355 EVM board.
 523
 524           To compile this driver as a module, choose M here: the
 525           module will be called dm355evm_keys.
 526
 527 config INPUT_BFIN_ROTARY
 528         tristate "Blackfin Rotary support"
 529         depends on BF54x || BF52x
 530         help
 531           Say Y here if you want to use the Blackfin Rotary.
 532
 533           To compile this driver as a module, choose M here: the
 534           module will be called bfin-rotary.
 535
 536 config INPUT_WM831X_ON
 537         tristate "WM831X ON pin"
 538         depends on MFD_WM831X
 539         help
 540           Support the ON pin of WM831X PMICs as an input device
 541           reporting power button status.
 542
 543           To compile this driver as a module, choose M here: the module
 544           will be called wm831x_on.
 545
 546 config INPUT_PCAP
 547         tristate "Motorola EZX PCAP misc input events"
 548         depends on EZX_PCAP
 549         help
 550           Say Y here if you want to use Power key and Headphone button
 551           on Motorola EZX phones.
 552
 553           To compile this driver as a module, choose M here: the
 554           module will be called pcap_keys.
 555
 556 config INPUT_ADXL34X
 557         tristate "Analog Devices ADXL34x Three-Axis Digital Accelerometer"
 558         default n
 559         help
 560           Say Y here if you have a Accelerometer interface using the
 561           ADXL345/6 controller, and your board-specific initialization
 562           code includes that in its table of devices.
 563
 564           This driver can use either I2C or SPI communication to the
 565           ADXL345/6 controller.  Select the appropriate method for
 566           your system.
 567
 568           If unsure, say N (but it's safe to say "Y").
 569
 570           To compile this driver as a module, choose M here: the
 571           module will be called adxl34x.
 572
 573 config INPUT_ADXL34X_I2C
 574         tristate "support I2C bus connection"
 575         depends on INPUT_ADXL34X && I2C
 576         default y
 577         help
 578           Say Y here if you have ADXL345/6 hooked to an I2C bus.
 579
 580           To compile this driver as a module, choose M here: the
 581           module will be called adxl34x-i2c.
 582
 583 config INPUT_ADXL34X_SPI
 584         tristate "support SPI bus connection"
 585         depends on INPUT_ADXL34X && SPI
 586         default y
 587         help
 588           Say Y here if you have ADXL345/6 hooked to a SPI bus.
 589
 590           To compile this driver as a module, choose M here: the
 591           module will be called adxl34x-spi.
 592
 593 config INPUT_IMS_PCU
 594         tristate "IMS Passenger Control Unit driver"
 595         depends on USB
 596         depends on LEDS_CLASS
 597         help
 598           Say Y here if you have system with IMS Rave Passenger Control Unit.
 599
 600           To compile this driver as a module, choose M here: the module will be
 601           called ims_pcu.
 602
 603 config INPUT_CMA3000
 604         tristate "VTI CMA3000 Tri-axis accelerometer"
 605         help
 606           Say Y here if you want to use VTI CMA3000_D0x Accelerometer
 607           driver
 608
 609           This driver currently only supports I2C interface to the
 610           controller. Also select the I2C method.
 611
 612           If unsure, say N
 613
 614           To compile this driver as a module, choose M here: the
 615           module will be called cma3000_d0x.
 616
 617 config INPUT_CMA3000_I2C
 618         tristate "Support I2C bus connection"
 619         depends on INPUT_CMA3000 && I2C
 620         help
 621           Say Y here if you want to use VTI CMA3000_D0x Accelerometer
 622           through I2C interface.
 623
 624           To compile this driver as a module, choose M here: the
 625           module will be called cma3000_d0x_i2c.
 626
 627 config INPUT_XEN_KBDDEV_FRONTEND
 628         tristate "Xen virtual keyboard and mouse support"
 629         depends on XEN
 630         default y
 631         select XEN_XENBUS_FRONTEND
 632         help
 633           This driver implements the front-end of the Xen virtual
 634           keyboard and mouse device driver.  It communicates with a back-end
 635           in another domain.
 636
 637           To compile this driver as a module, choose M here: the
 638           module will be called xen-kbdfront.
 639
 640 config INPUT_SIRFSOC_ONKEY
 641         bool "CSR SiRFSoC power on/off/suspend key support"
 642         depends on ARCH_SIRF && OF
 643         default y
 644         help
 645           Say Y here if you want to support for the SiRFSoC power on/off/suspend key
 646           in Linux, after you press the onkey, system will suspend.
 647
 648           If unsure, say N.
 649
 650 config INPUT_IDEAPAD_SLIDEBAR
 651         tristate "IdeaPad Laptop Slidebar"
 652         depends on INPUT
 653         depends on SERIO_I8042
 654         help
 655           Say Y here if you have an IdeaPad laptop with a slidebar.
 656
 657           To compile this driver as a module, choose M here: the
 658           module will be called ideapad_slidebar.
 659
 660 endif