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_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 35config 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 45config 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 55config 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 65config 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 75config 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 85config 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 96config 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 108config 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 120config 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 131config 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 143config INPUT_M68K_BEEP 144 tristate "M68k Beeper support" 145 depends on M68K 146 147config 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 157config INPUT_MAX8997_HAPTIC 158 tristate "MAXIM MAX8997 haptic controller support" 159 depends on 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 169config INPUT_MC13783_PWRBUTTON 170 tristate "MC13783 ON buttons" 171 depends on MFD_MC13XXX 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 179config 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 190config 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 200config 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 214config 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 225config INPUT_GPIO_BEEPER 226 tristate "Generic GPIO Beeper support" 227 depends on GPIOLIB 228 help 229 Say Y here if you have a beeper connected to a GPIO pin. 230 231 To compile this driver as a module, choose M here: the 232 module will be called gpio-beeper. 233 234config INPUT_GPIO_TILT_POLLED 235 tristate "Polled GPIO tilt switch" 236 depends on GPIOLIB 237 select INPUT_POLLDEV 238 help 239 This driver implements support for tilt switches connected 240 to GPIO pins that are not capable of generating interrupts. 241 242 The list of gpios to use and the mapping of their states 243 to specific angles is done via platform data. 244 245 To compile this driver as a module, choose M here: the 246 module will be called gpio_tilt_polled. 247 248config INPUT_IXP4XX_BEEPER 249 tristate "IXP4XX Beeper support" 250 depends on ARCH_IXP4XX 251 help 252 If you say yes here, you can connect a beeper to the 253 ixp4xx gpio pins. This is used by the LinkSys NSLU2. 254 255 If unsure, say Y. 256 257 To compile this driver as a module, choose M here: the 258 module will be called ixp4xx-beeper. 259 260config INPUT_COBALT_BTNS 261 tristate "Cobalt button interface" 262 depends on MIPS_COBALT 263 select INPUT_POLLDEV 264 help 265 Say Y here if you want to support MIPS Cobalt button interface. 266 267 To compile this driver as a module, choose M here: the 268 module will be called cobalt_btns. 269 270config INPUT_WISTRON_BTNS 271 tristate "x86 Wistron laptop button interface" 272 depends on X86_32 273 select INPUT_POLLDEV 274 select INPUT_SPARSEKMAP 275 select NEW_LEDS 276 select LEDS_CLASS 277 select CHECK_SIGNATURE 278 help 279 Say Y here for support of Wistron laptop button interfaces, used on 280 laptops of various brands, including Acer and Fujitsu-Siemens. If 281 available, mail and wifi LEDs will be controllable via /sys/class/leds. 282 283 To compile this driver as a module, choose M here: the module will 284 be called wistron_btns. 285 286config INPUT_ATLAS_BTNS 287 tristate "x86 Atlas button interface" 288 depends on X86 && ACPI 289 help 290 Say Y here for support of Atlas wallmount touchscreen buttons. 291 The events will show up as scancodes F1 through F9 via evdev. 292 293 To compile this driver as a module, choose M here: the module will 294 be called atlas_btns. 295 296config INPUT_ATI_REMOTE2 297 tristate "ATI / Philips USB RF remote control" 298 depends on USB_ARCH_HAS_HCD 299 select USB 300 help 301 Say Y here if you want to use an ATI or Philips USB RF remote control. 302 These are RF remotes with USB receivers. 303 ATI Remote Wonder II comes with some ATI's All-In-Wonder video cards 304 and is also available as a separate product. 305 This driver provides mouse pointer, left and right mouse buttons, 306 and maps all the other remote buttons to keypress events. 307 308 To compile this driver as a module, choose M here: the module will be 309 called ati_remote2. 310 311config INPUT_KEYSPAN_REMOTE 312 tristate "Keyspan DMR USB remote control" 313 depends on USB_ARCH_HAS_HCD 314 select USB 315 help 316 Say Y here if you want to use a Keyspan DMR USB remote control. 317 Currently only the UIA-11 type of receiver has been tested. The tag 318 on the receiver that connects to the USB port should have a P/N that 319 will tell you what type of DMR you have. The UIA-10 type is not 320 supported at this time. This driver maps all buttons to keypress 321 events. 322 323 To compile this driver as a module, choose M here: the module will 324 be called keyspan_remote. 325 326config INPUT_KXTJ9 327 tristate "Kionix KXTJ9 tri-axis digital accelerometer" 328 depends on I2C 329 help 330 Say Y here to enable support for the Kionix KXTJ9 digital tri-axis 331 accelerometer. 332 333 To compile this driver as a module, choose M here: the module will 334 be called kxtj9. 335 336config INPUT_KXTJ9_POLLED_MODE 337 bool "Enable polling mode support" 338 depends on INPUT_KXTJ9 339 select INPUT_POLLDEV 340 help 341 Say Y here if you need accelerometer to work in polling mode. 342 343config INPUT_POWERMATE 344 tristate "Griffin PowerMate and Contour Jog support" 345 depends on USB_ARCH_HAS_HCD 346 select USB 347 help 348 Say Y here if you want to use Griffin PowerMate or Contour Jog devices. 349 These are aluminum dials which can measure clockwise and anticlockwise 350 rotation. The dial also acts as a pushbutton. The base contains an LED 351 which can be instructed to pulse or to switch to a particular intensity. 352 353 You can download userspace tools from 354 <http://sowerbutts.com/powermate/>. 355 356 To compile this driver as a module, choose M here: the 357 module will be called powermate. 358 359config INPUT_YEALINK 360 tristate "Yealink usb-p1k voip phone" 361 depends on USB_ARCH_HAS_HCD 362 select USB 363 help 364 Say Y here if you want to enable keyboard and LCD functions of the 365 Yealink usb-p1k 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 For information about how to use these additional functions, see 369 <file:Documentation/input/yealink.txt>. 370 371 To compile this driver as a module, choose M here: the module will be 372 called yealink. 373 374config INPUT_CM109 375 tristate "C-Media CM109 USB I/O Controller" 376 depends on USB_ARCH_HAS_HCD 377 select USB 378 help 379 Say Y here if you want to enable keyboard and buzzer functions of the 380 C-Media CM109 usb phones. The audio part is enabled by the generic 381 usb sound driver, so you might want to enable that as well. 382 383 To compile this driver as a module, choose M here: the module will be 384 called cm109. 385 386config INPUT_RETU_PWRBUTTON 387 tristate "Retu Power button Driver" 388 depends on MFD_RETU 389 help 390 Say Y here if you want to enable power key reporting via the 391 Retu chips found in Nokia Internet Tablets (770, N800, N810). 392 393 To compile this driver as a module, choose M here. The module will 394 be called retu-pwrbutton. 395 396config INPUT_TWL4030_PWRBUTTON 397 tristate "TWL4030 Power button Driver" 398 depends on TWL4030_CORE 399 help 400 Say Y here if you want to enable power key reporting via the 401 TWL4030 family of chips. 402 403 To compile this driver as a module, choose M here. The module will 404 be called twl4030_pwrbutton. 405 406config INPUT_TWL4030_VIBRA 407 tristate "Support for TWL4030 Vibrator" 408 depends on TWL4030_CORE 409 select MFD_TWL4030_AUDIO 410 select INPUT_FF_MEMLESS 411 help 412 This option enables support for TWL4030 Vibrator Driver. 413 414 To compile this driver as a module, choose M here. The module will 415 be called twl4030_vibra. 416 417config INPUT_TWL6040_VIBRA 418 tristate "Support for TWL6040 Vibrator" 419 depends on TWL6040_CORE 420 select INPUT_FF_MEMLESS 421 help 422 This option enables support for TWL6040 Vibrator Driver. 423 424 To compile this driver as a module, choose M here. The module will 425 be called twl6040_vibra. 426 427config INPUT_UINPUT 428 tristate "User level driver support" 429 help 430 Say Y here if you want to support user level drivers for input 431 subsystem accessible under char device 10:223 - /dev/input/uinput. 432 433 To compile this driver as a module, choose M here: the 434 module will be called uinput. 435 436config INPUT_SGI_BTNS 437 tristate "SGI Indy/O2 volume button interface" 438 depends on SGI_IP22 || SGI_IP32 439 select INPUT_POLLDEV 440 help 441 Say Y here if you want to support SGI Indy/O2 volume button interface. 442 443 To compile this driver as a module, choose M here: the 444 module will be called sgi_btns. 445 446config HP_SDC_RTC 447 tristate "HP SDC Real Time Clock" 448 depends on (GSC || HP300) && SERIO 449 select HP_SDC 450 help 451 Say Y here if you want to support the built-in real time clock 452 of the HP SDC controller. 453 454config INPUT_PCF50633_PMU 455 tristate "PCF50633 PMU events" 456 depends on MFD_PCF50633 457 help 458 Say Y to include support for delivering PMU events via input 459 layer on NXP PCF50633. 460 461config INPUT_PCF8574 462 tristate "PCF8574 Keypad input device" 463 depends on I2C 464 help 465 Say Y here if you want to support a keypad connected via I2C 466 with a PCF8574. 467 468 To compile this driver as a module, choose M here: the 469 module will be called pcf8574_keypad. 470 471config INPUT_PWM_BEEPER 472 tristate "PWM beeper support" 473 depends on PWM 474 help 475 Say Y here to get support for PWM based beeper devices. 476 477 If unsure, say N. 478 479 To compile this driver as a module, choose M here: the module will be 480 called pwm-beeper. 481 482config INPUT_GPIO_ROTARY_ENCODER 483 tristate "Rotary encoders connected to GPIO pins" 484 depends on GPIOLIB 485 help 486 Say Y here to add support for rotary encoders connected to GPIO lines. 487 Check file:Documentation/input/rotary-encoder.txt for more 488 information. 489 490 To compile this driver as a module, choose M here: the 491 module will be called rotary_encoder. 492 493config INPUT_RB532_BUTTON 494 tristate "Mikrotik Routerboard 532 button interface" 495 depends on MIKROTIK_RB532 496 depends on GPIOLIB 497 select INPUT_POLLDEV 498 help 499 Say Y here if you want support for the S1 button built into 500 Mikrotik's Routerboard 532. 501 502 To compile this driver as a module, choose M here: the 503 module will be called rb532_button. 504 505config INPUT_DA9052_ONKEY 506 tristate "Dialog DA9052/DA9053 Onkey" 507 depends on PMIC_DA9052 508 help 509 Support the ONKEY of Dialog DA9052 PMICs as an input device 510 reporting power button status. 511 512 To compile this driver as a module, choose M here: the 513 module will be called da9052_onkey. 514 515config INPUT_DA9055_ONKEY 516 tristate "Dialog Semiconductor DA9055 ONKEY" 517 depends on MFD_DA9055 518 help 519 Support the ONKEY of DA9055 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 da9055_onkey. 524 525config INPUT_DM355EVM 526 tristate "TI DaVinci DM355 EVM Keypad and IR Remote" 527 depends on MFD_DM355EVM_MSP 528 select INPUT_SPARSEKMAP 529 help 530 Supports the pushbuttons and IR remote used with 531 the DM355 EVM board. 532 533 To compile this driver as a module, choose M here: the 534 module will be called dm355evm_keys. 535 536config INPUT_BFIN_ROTARY 537 tristate "Blackfin Rotary support" 538 depends on BF54x || BF52x 539 help 540 Say Y here if you want to use the Blackfin Rotary. 541 542 To compile this driver as a module, choose M here: the 543 module will be called bfin-rotary. 544 545config INPUT_WM831X_ON 546 tristate "WM831X ON pin" 547 depends on MFD_WM831X 548 help 549 Support the ON pin of WM831X PMICs as an input device 550 reporting power button status. 551 552 To compile this driver as a module, choose M here: the module 553 will be called wm831x_on. 554 555config INPUT_PCAP 556 tristate "Motorola EZX PCAP misc input events" 557 depends on EZX_PCAP 558 help 559 Say Y here if you want to use Power key and Headphone button 560 on Motorola EZX phones. 561 562 To compile this driver as a module, choose M here: the 563 module will be called pcap_keys. 564 565config INPUT_ADXL34X 566 tristate "Analog Devices ADXL34x Three-Axis Digital Accelerometer" 567 default n 568 help 569 Say Y here if you have a Accelerometer interface using the 570 ADXL345/6 controller, and your board-specific initialization 571 code includes that in its table of devices. 572 573 This driver can use either I2C or SPI communication to the 574 ADXL345/6 controller. Select the appropriate method for 575 your system. 576 577 If unsure, say N (but it's safe to say "Y"). 578 579 To compile this driver as a module, choose M here: the 580 module will be called adxl34x. 581 582config INPUT_ADXL34X_I2C 583 tristate "support I2C bus connection" 584 depends on INPUT_ADXL34X && I2C 585 default y 586 help 587 Say Y here if you have ADXL345/6 hooked to an I2C bus. 588 589 To compile this driver as a module, choose M here: the 590 module will be called adxl34x-i2c. 591 592config INPUT_ADXL34X_SPI 593 tristate "support SPI bus connection" 594 depends on INPUT_ADXL34X && SPI 595 default y 596 help 597 Say Y here if you have ADXL345/6 hooked to a SPI bus. 598 599 To compile this driver as a module, choose M here: the 600 module will be called adxl34x-spi. 601 602config INPUT_IMS_PCU 603 tristate "IMS Passenger Control Unit driver" 604 depends on USB 605 depends on LEDS_CLASS 606 help 607 Say Y here if you have system with IMS Rave Passenger Control Unit. 608 609 To compile this driver as a module, choose M here: the module will be 610 called ims_pcu. 611 612config INPUT_CMA3000 613 tristate "VTI CMA3000 Tri-axis accelerometer" 614 help 615 Say Y here if you want to use VTI CMA3000_D0x Accelerometer 616 driver 617 618 This driver currently only supports I2C interface to the 619 controller. Also select the I2C method. 620 621 If unsure, say N 622 623 To compile this driver as a module, choose M here: the 624 module will be called cma3000_d0x. 625 626config INPUT_CMA3000_I2C 627 tristate "Support I2C bus connection" 628 depends on INPUT_CMA3000 && I2C 629 help 630 Say Y here if you want to use VTI CMA3000_D0x Accelerometer 631 through I2C interface. 632 633 To compile this driver as a module, choose M here: the 634 module will be called cma3000_d0x_i2c. 635 636config INPUT_XEN_KBDDEV_FRONTEND 637 tristate "Xen virtual keyboard and mouse support" 638 depends on XEN 639 default y 640 select XEN_XENBUS_FRONTEND 641 help 642 This driver implements the front-end of the Xen virtual 643 keyboard and mouse device driver. It communicates with a back-end 644 in another domain. 645 646 To compile this driver as a module, choose M here: the 647 module will be called xen-kbdfront. 648 649config INPUT_SIRFSOC_ONKEY 650 bool "CSR SiRFSoC power on/off/suspend key support" 651 depends on ARCH_SIRF && OF 652 default y 653 help 654 Say Y here if you want to support for the SiRFSoC power on/off/suspend key 655 in Linux, after you press the onkey, system will suspend. 656 657 If unsure, say N. 658 659config INPUT_IDEAPAD_SLIDEBAR 660 tristate "IdeaPad Laptop Slidebar" 661 depends on INPUT 662 depends on SERIO_I8042 663 help 664 Say Y here if you have an IdeaPad laptop with a slidebar. 665 666 To compile this driver as a module, choose M here: the 667 module will be called ideapad_slidebar. 668 669config INPUT_SOC_BUTTON_ARRAY 670 tristate "Windows-compatible SoC Button Array" 671 depends on KEYBOARD_GPIO 672 help 673 Say Y here if you have a SoC-based tablet that originally 674 runs Windows 8. 675 676 To compile this driver as a module, choose M here: the 677 module will be called soc_button_array. 678 679config INPUT_DRV260X_HAPTICS 680 tristate "TI DRV260X haptics support" 681 depends on INPUT && I2C && GPIOLIB 682 select INPUT_FF_MEMLESS 683 select REGMAP_I2C 684 help 685 Say Y to enable support for the TI DRV260X haptics driver. 686 687 To compile this driver as a module, choose M here: the 688 module will be called drv260x-haptics. 689 690endif 691