1# 2# Input misc drivers configuration 3# 4menuconfig 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 13if INPUT_MISC 14 15config 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 25config 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 35config 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 45config 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 55config 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 65config 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 76config 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 88config 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 100config 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 111config 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 123config INPUT_M68K_BEEP 124 tristate "M68k Beeper support" 125 depends on M68K 126 127config 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 137config 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 149config 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 159config 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 170config 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 180config 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 194config 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 205config 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 219config 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 231config 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 241config 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 257config 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 267config 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 282config INPUT_KEYCHORD 283 tristate "Key chord input driver support" 284 help 285 Say Y here if you want to enable the key chord driver 286 accessible at /dev/keychord. This driver can be used 287 for receiving notifications when client specified key 288 combinations are pressed. 289 290 To compile this driver as a module, choose M here: the 291 module will be called keychord. 292 293config INPUT_KEYSPAN_REMOTE 294 tristate "Keyspan DMR USB remote control (EXPERIMENTAL)" 295 depends on EXPERIMENTAL 296 depends on USB_ARCH_HAS_HCD 297 select USB 298 help 299 Say Y here if you want to use a Keyspan DMR USB remote control. 300 Currently only the UIA-11 type of receiver has been tested. The tag 301 on the receiver that connects to the USB port should have a P/N that 302 will tell you what type of DMR you have. The UIA-10 type is not 303 supported at this time. This driver maps all buttons to keypress 304 events. 305 306 To compile this driver as a module, choose M here: the module will 307 be called keyspan_remote. 308 309config INPUT_KXTJ9 310 tristate "Kionix KXTJ9 tri-axis digital accelerometer" 311 depends on I2C 312 help 313 Say Y here to enable support for the Kionix KXTJ9 digital tri-axis 314 accelerometer. 315 316 To compile this driver as a module, choose M here: the module will 317 be called kxtj9. 318 319config INPUT_KXTJ9_POLLED_MODE 320 bool "Enable polling mode support" 321 depends on INPUT_KXTJ9 322 select INPUT_POLLDEV 323 help 324 Say Y here if you need accelerometer to work in polling mode. 325 326config INPUT_POWERMATE 327 tristate "Griffin PowerMate and Contour Jog support" 328 depends on USB_ARCH_HAS_HCD 329 select USB 330 help 331 Say Y here if you want to use Griffin PowerMate or Contour Jog devices. 332 These are aluminum dials which can measure clockwise and anticlockwise 333 rotation. The dial also acts as a pushbutton. The base contains an LED 334 which can be instructed to pulse or to switch to a particular intensity. 335 336 You can download userspace tools from 337 <http://sowerbutts.com/powermate/>. 338 339 To compile this driver as a module, choose M here: the 340 module will be called powermate. 341 342config INPUT_YEALINK 343 tristate "Yealink usb-p1k voip phone" 344 depends on EXPERIMENTAL 345 depends on USB_ARCH_HAS_HCD 346 select USB 347 help 348 Say Y here if you want to enable keyboard and LCD functions of the 349 Yealink usb-p1k usb phones. The audio part is enabled by the generic 350 usb sound driver, so you might want to enable that as well. 351 352 For information about how to use these additional functions, see 353 <file:Documentation/input/yealink.txt>. 354 355 To compile this driver as a module, choose M here: the module will be 356 called yealink. 357 358config INPUT_CM109 359 tristate "C-Media CM109 USB I/O Controller" 360 depends on EXPERIMENTAL 361 depends on USB_ARCH_HAS_HCD 362 select USB 363 help 364 Say Y here if you want to enable keyboard and buzzer functions of the 365 C-Media CM109 usb phones. The audio part is enabled by the generic 366 usb sound driver, so you might want to enable that as well. 367 368 To compile this driver as a module, choose M here: the module will be 369 called cm109. 370 371config INPUT_TWL4030_PWRBUTTON 372 tristate "TWL4030 Power button Driver" 373 depends on TWL4030_CORE 374 help 375 Say Y here if you want to enable power key reporting via the 376 TWL4030 family of chips. 377 378 To compile this driver as a module, choose M here. The module will 379 be called twl4030_pwrbutton. 380 381config INPUT_TWL4030_VIBRA 382 tristate "Support for TWL4030 Vibrator" 383 depends on TWL4030_CORE 384 select MFD_TWL4030_AUDIO 385 select INPUT_FF_MEMLESS 386 help 387 This option enables support for TWL4030 Vibrator Driver. 388 389 To compile this driver as a module, choose M here. The module will 390 be called twl4030_vibra. 391 392config INPUT_TWL6040_VIBRA 393 tristate "Support for TWL6040 Vibrator" 394 depends on TWL6040_CORE 395 select INPUT_FF_MEMLESS 396 help 397 This option enables support for TWL6040 Vibrator Driver. 398 399 To compile this driver as a module, choose M here. The module will 400 be called twl6040_vibra. 401 402config INPUT_UINPUT 403 tristate "User level driver support" 404 help 405 Say Y here if you want to support user level drivers for input 406 subsystem accessible under char device 10:223 - /dev/input/uinput. 407 408 To compile this driver as a module, choose M here: the 409 module will be called uinput. 410 411config INPUT_SGI_BTNS 412 tristate "SGI Indy/O2 volume button interface" 413 depends on SGI_IP22 || SGI_IP32 414 select INPUT_POLLDEV 415 help 416 Say Y here if you want to support SGI Indy/O2 volume button interface. 417 418 To compile this driver as a module, choose M here: the 419 module will be called sgi_btns. 420 421config INPUT_GPIO 422 tristate "GPIO driver support" 423 help 424 Say Y here if you want to support gpio based keys, wheels etc... 425 426config HP_SDC_RTC 427 tristate "HP SDC Real Time Clock" 428 depends on (GSC || HP300) && SERIO 429 select HP_SDC 430 help 431 Say Y here if you want to support the built-in real time clock 432 of the HP SDC controller. 433 434config INPUT_PCF50633_PMU 435 tristate "PCF50633 PMU events" 436 depends on MFD_PCF50633 437 help 438 Say Y to include support for delivering PMU events via input 439 layer on NXP PCF50633. 440 441config INPUT_PCF8574 442 tristate "PCF8574 Keypad input device" 443 depends on I2C && EXPERIMENTAL 444 help 445 Say Y here if you want to support a keypad connected via I2C 446 with a PCF8574. 447 448 To compile this driver as a module, choose M here: the 449 module will be called pcf8574_keypad. 450 451config INPUT_PWM_BEEPER 452 tristate "PWM beeper support" 453 depends on HAVE_PWM 454 help 455 Say Y here to get support for PWM based beeper devices. 456 457 If unsure, say N. 458 459 To compile this driver as a module, choose M here: the module will be 460 called pwm-beeper. 461 462config INPUT_GPIO_ROTARY_ENCODER 463 tristate "Rotary encoders connected to GPIO pins" 464 depends on GPIOLIB && GENERIC_GPIO 465 help 466 Say Y here to add support for rotary encoders connected to GPIO lines. 467 Check file:Documentation/input/rotary-encoder.txt for more 468 information. 469 470 To compile this driver as a module, choose M here: the 471 module will be called rotary_encoder. 472 473config INPUT_RB532_BUTTON 474 tristate "Mikrotik Routerboard 532 button interface" 475 depends on MIKROTIK_RB532 476 depends on GPIOLIB && GENERIC_GPIO 477 select INPUT_POLLDEV 478 help 479 Say Y here if you want support for the S1 button built into 480 Mikrotik's Routerboard 532. 481 482 To compile this driver as a module, choose M here: the 483 module will be called rb532_button. 484 485config INPUT_DA9052_ONKEY 486 tristate "Dialog DA9052/DA9053 Onkey" 487 depends on PMIC_DA9052 488 help 489 Support the ONKEY of Dialog DA9052 PMICs as an input device 490 reporting power button status. 491 492 To compile this driver as a module, choose M here: the 493 module will be called da9052_onkey. 494 495config INPUT_DM355EVM 496 tristate "TI DaVinci DM355 EVM Keypad and IR Remote" 497 depends on MFD_DM355EVM_MSP 498 select INPUT_SPARSEKMAP 499 help 500 Supports the pushbuttons and IR remote used with 501 the DM355 EVM board. 502 503 To compile this driver as a module, choose M here: the 504 module will be called dm355evm_keys. 505 506config INPUT_BFIN_ROTARY 507 tristate "Blackfin Rotary support" 508 depends on BF54x || BF52x 509 help 510 Say Y here if you want to use the Blackfin Rotary. 511 512 To compile this driver as a module, choose M here: the 513 module will be called bfin-rotary. 514 515config INPUT_WM831X_ON 516 tristate "WM831X ON pin" 517 depends on MFD_WM831X 518 help 519 Support the ON pin of WM831X PMICs as an input device 520 reporting power button status. 521 522 To compile this driver as a module, choose M here: the module 523 will be called wm831x_on. 524 525config INPUT_PCAP 526 tristate "Motorola EZX PCAP misc input events" 527 depends on EZX_PCAP 528 help 529 Say Y here if you want to use Power key and Headphone button 530 on Motorola EZX phones. 531 532 To compile this driver as a module, choose M here: the 533 module will be called pcap_keys. 534 535config INPUT_ADXL34X 536 tristate "Analog Devices ADXL34x Three-Axis Digital Accelerometer" 537 default n 538 help 539 Say Y here if you have a Accelerometer interface using the 540 ADXL345/6 controller, and your board-specific initialization 541 code includes that in its table of devices. 542 543 This driver can use either I2C or SPI communication to the 544 ADXL345/6 controller. Select the appropriate method for 545 your system. 546 547 If unsure, say N (but it's safe to say "Y"). 548 549 To compile this driver as a module, choose M here: the 550 module will be called adxl34x. 551 552config INPUT_ADXL34X_I2C 553 tristate "support I2C bus connection" 554 depends on INPUT_ADXL34X && I2C 555 default y 556 help 557 Say Y here if you have ADXL345/6 hooked to an I2C bus. 558 559 To compile this driver as a module, choose M here: the 560 module will be called adxl34x-i2c. 561 562config INPUT_ADXL34X_SPI 563 tristate "support SPI bus connection" 564 depends on INPUT_ADXL34X && SPI 565 default y 566 help 567 Say Y here if you have ADXL345/6 hooked to a SPI bus. 568 569 To compile this driver as a module, choose M here: the 570 module will be called adxl34x-spi. 571 572config INPUT_CMA3000 573 tristate "VTI CMA3000 Tri-axis accelerometer" 574 help 575 Say Y here if you want to use VTI CMA3000_D0x Accelerometer 576 driver 577 578 This driver currently only supports I2C interface to the 579 controller. Also select the I2C method. 580 581 If unsure, say N 582 583 To compile this driver as a module, choose M here: the 584 module will be called cma3000_d0x. 585 586config INPUT_CMA3000_I2C 587 tristate "Support I2C bus connection" 588 depends on INPUT_CMA3000 && I2C 589 help 590 Say Y here if you want to use VTI CMA3000_D0x Accelerometer 591 through I2C interface. 592 593 To compile this driver as a module, choose M here: the 594 module will be called cma3000_d0x_i2c. 595 596config INPUT_XEN_KBDDEV_FRONTEND 597 tristate "Xen virtual keyboard and mouse support" 598 depends on XEN 599 default y 600 select XEN_XENBUS_FRONTEND 601 help 602 This driver implements the front-end of the Xen virtual 603 keyboard and mouse device driver. It communicates with a back-end 604 in another domain. 605 606 To compile this driver as a module, choose M here: the 607 module will be called xen-kbdfront. 608 609endif 610