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