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