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