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_E3X0_BUTTON 97 tristate "NI Ettus Research USRP E3xx Button support." 98 default n 99 help 100 Say Y here to enable support for the NI Ettus Research 101 USRP E3xx Button. 102 103 To compile this driver as a module, choose M here: the 104 module will be called e3x0_button. 105 106config INPUT_PCSPKR 107 tristate "PC Speaker support" 108 depends on PCSPKR_PLATFORM 109 help 110 Say Y here if you want the standard PC Speaker to be used for 111 bells and whistles. 112 113 If unsure, say Y. 114 115 To compile this driver as a module, choose M here: the 116 module will be called pcspkr. 117 118config INPUT_PM8941_PWRKEY 119 tristate "Qualcomm PM8941 power key support" 120 depends on MFD_SPMI_PMIC 121 help 122 Say Y here if you want support for the power key usually found 123 on boards using a Qualcomm PM8941 compatible PMIC. 124 125 If unsure, say Y. 126 127 To compile this driver as a module, choose M here: the module 128 will be called pm8941-pwrkey. 129 130config INPUT_PM8XXX_VIBRATOR 131 tristate "Qualcomm PM8XXX vibrator support" 132 depends on MFD_PM8XXX 133 select INPUT_FF_MEMLESS 134 help 135 This option enables device driver support for the vibrator 136 on Qualcomm PM8xxx chip. This driver supports ff-memless interface 137 from input framework. 138 139 To compile this driver as module, choose M here: the 140 module will be called pm8xxx-vibrator. 141 142config INPUT_PMIC8XXX_PWRKEY 143 tristate "PMIC8XXX power key support" 144 depends on MFD_PM8XXX 145 help 146 Say Y here if you want support for the PMIC8XXX power key. 147 148 If unsure, say N. 149 150 To compile this driver as a module, choose M here: the 151 module will be called pmic8xxx-pwrkey. 152 153config INPUT_SPARCSPKR 154 tristate "SPARC Speaker support" 155 depends on PCI && SPARC64 156 help 157 Say Y here if you want the standard Speaker on Sparc PCI systems 158 to be used for bells and whistles. 159 160 If unsure, say Y. 161 162 To compile this driver as a module, choose M here: the 163 module will be called sparcspkr. 164 165config INPUT_M68K_BEEP 166 tristate "M68k Beeper support" 167 depends on M68K 168 169config INPUT_MAX77693_HAPTIC 170 tristate "MAXIM MAX77693/MAX77843 haptic controller support" 171 depends on (MFD_MAX77693 || MFD_MAX77843) && PWM 172 select INPUT_FF_MEMLESS 173 help 174 This option enables support for the haptic controller on 175 MAXIM MAX77693 and MAX77843 chips. 176 177 To compile this driver as module, choose M here: the 178 module will be called max77693-haptic. 179 180config INPUT_MAX8925_ONKEY 181 tristate "MAX8925 ONKEY support" 182 depends on MFD_MAX8925 183 help 184 Support the ONKEY of MAX8925 PMICs as an input device 185 reporting power button status. 186 187 To compile this driver as a module, choose M here: the module 188 will be called max8925_onkey. 189 190config INPUT_MAX8997_HAPTIC 191 tristate "MAXIM MAX8997 haptic controller support" 192 depends on PWM && MFD_MAX8997 193 select INPUT_FF_MEMLESS 194 help 195 This option enables device driver support for the haptic controller 196 on MAXIM MAX8997 chip. This driver supports ff-memless interface 197 from input framework. 198 199 To compile this driver as module, choose M here: the 200 module will be called max8997-haptic. 201 202config INPUT_MC13783_PWRBUTTON 203 tristate "MC13783 ON buttons" 204 depends on MFD_MC13XXX 205 help 206 Support the ON buttons of MC13783 PMIC as an input device 207 reporting power button status. 208 209 To compile this driver as a module, choose M here: the module 210 will be called mc13783-pwrbutton. 211 212config INPUT_MMA8450 213 tristate "MMA8450 - Freescale's 3-Axis, 8/12-bit Digital Accelerometer" 214 depends on I2C 215 select INPUT_POLLDEV 216 help 217 Say Y here if you want to support Freescale's MMA8450 Accelerometer 218 through I2C interface. 219 220 To compile this driver as a module, choose M here: the 221 module will be called mma8450. 222 223config INPUT_MPU3050 224 tristate "MPU3050 Triaxial gyroscope sensor" 225 depends on I2C 226 help 227 Say Y here if you want to support InvenSense MPU3050 228 connected via an I2C bus. 229 230 To compile this driver as a module, choose M here: the 231 module will be called mpu3050. 232 233config INPUT_APANEL 234 tristate "Fujitsu Lifebook Application Panel buttons" 235 depends on X86 && I2C && LEDS_CLASS 236 select INPUT_POLLDEV 237 select CHECK_SIGNATURE 238 help 239 Say Y here for support of the Application Panel buttons, used on 240 Fujitsu Lifebook. These are attached to the mainboard through 241 an SMBus interface managed by the I2C Intel ICH (i801) driver, 242 which you should also build for this kernel. 243 244 To compile this driver as a module, choose M here: the module will 245 be called apanel. 246 247config INPUT_GP2A 248 tristate "Sharp GP2AP002A00F I2C Proximity/Opto sensor driver" 249 depends on I2C 250 depends on GPIOLIB || COMPILE_TEST 251 help 252 Say Y here if you have a Sharp GP2AP002A00F proximity/als combo-chip 253 hooked to an I2C bus. 254 255 To compile this driver as a module, choose M here: the 256 module will be called gp2ap002a00f. 257 258config INPUT_GPIO_BEEPER 259 tristate "Generic GPIO Beeper support" 260 depends on GPIOLIB || COMPILE_TEST 261 help 262 Say Y here if you have a beeper connected to a GPIO pin. 263 264 To compile this driver as a module, choose M here: the 265 module will be called gpio-beeper. 266 267config INPUT_GPIO_TILT_POLLED 268 tristate "Polled GPIO tilt switch" 269 depends on GPIOLIB || COMPILE_TEST 270 select INPUT_POLLDEV 271 help 272 This driver implements support for tilt switches connected 273 to GPIO pins that are not capable of generating interrupts. 274 275 The list of gpios to use and the mapping of their states 276 to specific angles is done via platform data. 277 278 To compile this driver as a module, choose M here: the 279 module will be called gpio_tilt_polled. 280 281config INPUT_IXP4XX_BEEPER 282 tristate "IXP4XX Beeper support" 283 depends on ARCH_IXP4XX 284 help 285 If you say yes here, you can connect a beeper to the 286 ixp4xx gpio pins. This is used by the LinkSys NSLU2. 287 288 If unsure, say Y. 289 290 To compile this driver as a module, choose M here: the 291 module will be called ixp4xx-beeper. 292 293config INPUT_COBALT_BTNS 294 tristate "Cobalt button interface" 295 depends on MIPS_COBALT 296 select INPUT_POLLDEV 297 help 298 Say Y here if you want to support MIPS Cobalt button interface. 299 300 To compile this driver as a module, choose M here: the 301 module will be called cobalt_btns. 302 303config INPUT_WISTRON_BTNS 304 tristate "x86 Wistron laptop button interface" 305 depends on X86_32 306 select INPUT_POLLDEV 307 select INPUT_SPARSEKMAP 308 select NEW_LEDS 309 select LEDS_CLASS 310 select CHECK_SIGNATURE 311 help 312 Say Y here for support of Wistron laptop button interfaces, used on 313 laptops of various brands, including Acer and Fujitsu-Siemens. If 314 available, mail and wifi LEDs will be controllable via /sys/class/leds. 315 316 To compile this driver as a module, choose M here: the module will 317 be called wistron_btns. 318 319config INPUT_ATLAS_BTNS 320 tristate "x86 Atlas button interface" 321 depends on X86 && ACPI 322 help 323 Say Y here for support of Atlas wallmount touchscreen buttons. 324 The events will show up as scancodes F1 through F9 via evdev. 325 326 To compile this driver as a module, choose M here: the module will 327 be called atlas_btns. 328 329config INPUT_ATI_REMOTE2 330 tristate "ATI / Philips USB RF remote control" 331 depends on USB_ARCH_HAS_HCD 332 select USB 333 help 334 Say Y here if you want to use an ATI or Philips USB RF remote control. 335 These are RF remotes with USB receivers. 336 ATI Remote Wonder II comes with some ATI's All-In-Wonder video cards 337 and is also available as a separate product. 338 This driver provides mouse pointer, left and right mouse buttons, 339 and maps all the other remote buttons to keypress events. 340 341 To compile this driver as a module, choose M here: the module will be 342 called ati_remote2. 343 344config INPUT_KEYCHORD 345 tristate "Key chord input driver support" 346 help 347 Say Y here if you want to enable the key chord driver 348 accessible at /dev/keychord. This driver can be used 349 for receiving notifications when client specified key 350 combinations are pressed. 351 352 To compile this driver as a module, choose M here: the 353 module will be called keychord. 354 355config INPUT_KEYSPAN_REMOTE 356 tristate "Keyspan DMR USB remote control" 357 depends on USB_ARCH_HAS_HCD 358 select USB 359 help 360 Say Y here if you want to use a Keyspan DMR USB remote control. 361 Currently only the UIA-11 type of receiver has been tested. The tag 362 on the receiver that connects to the USB port should have a P/N that 363 will tell you what type of DMR you have. The UIA-10 type is not 364 supported at this time. This driver maps all buttons to keypress 365 events. 366 367 To compile this driver as a module, choose M here: the module will 368 be called keyspan_remote. 369 370config INPUT_KXTJ9 371 tristate "Kionix KXTJ9 tri-axis digital accelerometer" 372 depends on I2C 373 help 374 Say Y here to enable support for the Kionix KXTJ9 digital tri-axis 375 accelerometer. 376 377 To compile this driver as a module, choose M here: the module will 378 be called kxtj9. 379 380config INPUT_KXTJ9_POLLED_MODE 381 bool "Enable polling mode support" 382 depends on INPUT_KXTJ9 383 select INPUT_POLLDEV 384 help 385 Say Y here if you need accelerometer to work in polling mode. 386 387config INPUT_POWERMATE 388 tristate "Griffin PowerMate and Contour Jog support" 389 depends on USB_ARCH_HAS_HCD 390 select USB 391 help 392 Say Y here if you want to use Griffin PowerMate or Contour Jog devices. 393 These are aluminum dials which can measure clockwise and anticlockwise 394 rotation. The dial also acts as a pushbutton. The base contains an LED 395 which can be instructed to pulse or to switch to a particular intensity. 396 397 You can download userspace tools from 398 <http://sowerbutts.com/powermate/>. 399 400 To compile this driver as a module, choose M here: the 401 module will be called powermate. 402 403config INPUT_YEALINK 404 tristate "Yealink usb-p1k voip phone" 405 depends on USB_ARCH_HAS_HCD 406 select USB 407 help 408 Say Y here if you want to enable keyboard and LCD functions of the 409 Yealink usb-p1k usb phones. The audio part is enabled by the generic 410 usb sound driver, so you might want to enable that as well. 411 412 For information about how to use these additional functions, see 413 <file:Documentation/input/yealink.txt>. 414 415 To compile this driver as a module, choose M here: the module will be 416 called yealink. 417 418config INPUT_CM109 419 tristate "C-Media CM109 USB I/O Controller" 420 depends on USB_ARCH_HAS_HCD 421 select USB 422 help 423 Say Y here if you want to enable keyboard and buzzer functions of the 424 C-Media CM109 usb phones. The audio part is enabled by the generic 425 usb sound driver, so you might want to enable that as well. 426 427 To compile this driver as a module, choose M here: the module will be 428 called cm109. 429 430config INPUT_REGULATOR_HAPTIC 431 tristate "Regulator haptics support" 432 depends on REGULATOR 433 select INPUT_FF_MEMLESS 434 help 435 This option enables device driver support for the haptic controlled 436 by a regulator. This driver supports ff-memless interface 437 from input framework. 438 439 To compile this driver as a module, choose M here: the 440 module will be called regulator-haptic. 441 442config INPUT_RETU_PWRBUTTON 443 tristate "Retu Power button Driver" 444 depends on MFD_RETU 445 help 446 Say Y here if you want to enable power key reporting via the 447 Retu chips found in Nokia Internet Tablets (770, N800, N810). 448 449 To compile this driver as a module, choose M here. The module will 450 be called retu-pwrbutton. 451 452config INPUT_TPS65218_PWRBUTTON 453 tristate "TPS65218 Power button driver" 454 depends on MFD_TPS65218 455 help 456 Say Y here if you want to enable power buttong reporting for 457 the TPS65218 Power Management IC device. 458 459 To compile this driver as a module, choose M here. The module will 460 be called tps65218-pwrbutton. 461 462config INPUT_AXP20X_PEK 463 tristate "X-Powers AXP20X power button driver" 464 depends on MFD_AXP20X 465 help 466 Say Y here if you want to enable power key reporting via the 467 AXP20X PMIC. 468 469 To compile this driver as a module, choose M here. The module will 470 be called axp20x-pek. 471 472 473config INPUT_TWL4030_PWRBUTTON 474 tristate "TWL4030 Power button Driver" 475 depends on TWL4030_CORE 476 help 477 Say Y here if you want to enable power key reporting via the 478 TWL4030 family of chips. 479 480 To compile this driver as a module, choose M here. The module will 481 be called twl4030_pwrbutton. 482 483config INPUT_TWL4030_VIBRA 484 tristate "Support for TWL4030 Vibrator" 485 depends on TWL4030_CORE 486 select MFD_TWL4030_AUDIO 487 select INPUT_FF_MEMLESS 488 help 489 This option enables support for TWL4030 Vibrator Driver. 490 491 To compile this driver as a module, choose M here. The module will 492 be called twl4030_vibra. 493 494config INPUT_TWL6040_VIBRA 495 tristate "Support for TWL6040 Vibrator" 496 depends on TWL6040_CORE 497 select INPUT_FF_MEMLESS 498 help 499 This option enables support for TWL6040 Vibrator Driver. 500 501 To compile this driver as a module, choose M here. The module will 502 be called twl6040_vibra. 503 504config INPUT_UINPUT 505 tristate "User level driver support" 506 help 507 Say Y here if you want to support user level drivers for input 508 subsystem accessible under char device 10:223 - /dev/input/uinput. 509 510 To compile this driver as a module, choose M here: the 511 module will be called uinput. 512 513config INPUT_SGI_BTNS 514 tristate "SGI Indy/O2 volume button interface" 515 depends on SGI_IP22 || SGI_IP32 516 select INPUT_POLLDEV 517 help 518 Say Y here if you want to support SGI Indy/O2 volume button interface. 519 520 To compile this driver as a module, choose M here: the 521 module will be called sgi_btns. 522 523config INPUT_GPIO 524 tristate "GPIO driver support" 525 help 526 Say Y here if you want to support gpio based keys, wheels etc... 527 528config HP_SDC_RTC 529 tristate "HP SDC Real Time Clock" 530 depends on (GSC || HP300) && SERIO 531 select HP_SDC 532 help 533 Say Y here if you want to support the built-in real time clock 534 of the HP SDC controller. 535 536config INPUT_PALMAS_PWRBUTTON 537 tristate "Palmas Power button Driver" 538 depends on MFD_PALMAS 539 help 540 Say Y here if you want to enable power key reporting via the 541 Palmas family of PMICs. 542 543 To compile this driver as a module, choose M here. The module will 544 be called palmas_pwrbutton. 545 546config INPUT_PCF50633_PMU 547 tristate "PCF50633 PMU events" 548 depends on MFD_PCF50633 549 help 550 Say Y to include support for delivering PMU events via input 551 layer on NXP PCF50633. 552 553config INPUT_PCF8574 554 tristate "PCF8574 Keypad input device" 555 depends on I2C 556 help 557 Say Y here if you want to support a keypad connected via I2C 558 with a PCF8574. 559 560 To compile this driver as a module, choose M here: the 561 module will be called pcf8574_keypad. 562 563config INPUT_PWM_BEEPER 564 tristate "PWM beeper support" 565 depends on PWM 566 help 567 Say Y here to get support for PWM based beeper devices. 568 569 If unsure, say N. 570 571 To compile this driver as a module, choose M here: the module will be 572 called pwm-beeper. 573 574config INPUT_GPIO_ROTARY_ENCODER 575 tristate "Rotary encoders connected to GPIO pins" 576 depends on GPIOLIB || COMPILE_TEST 577 help 578 Say Y here to add support for rotary encoders connected to GPIO lines. 579 Check file:Documentation/input/rotary-encoder.txt for more 580 information. 581 582 To compile this driver as a module, choose M here: the 583 module will be called rotary_encoder. 584 585config INPUT_RB532_BUTTON 586 tristate "Mikrotik Routerboard 532 button interface" 587 depends on MIKROTIK_RB532 588 depends on GPIOLIB 589 select INPUT_POLLDEV 590 help 591 Say Y here if you want support for the S1 button built into 592 Mikrotik's Routerboard 532. 593 594 To compile this driver as a module, choose M here: the 595 module will be called rb532_button. 596 597config INPUT_DA9052_ONKEY 598 tristate "Dialog DA9052/DA9053 Onkey" 599 depends on PMIC_DA9052 600 help 601 Support the ONKEY of Dialog DA9052 PMICs as an input device 602 reporting power button status. 603 604 To compile this driver as a module, choose M here: the 605 module will be called da9052_onkey. 606 607config INPUT_DA9055_ONKEY 608 tristate "Dialog Semiconductor DA9055 ONKEY" 609 depends on MFD_DA9055 610 help 611 Support the ONKEY of DA9055 PMICs as an input device 612 reporting power button status. 613 614 To compile this driver as a module, choose M here: the module 615 will be called da9055_onkey. 616 617config INPUT_DA9063_ONKEY 618 tristate "Dialog DA9062/63 OnKey" 619 depends on MFD_DA9063 || MFD_DA9062 620 help 621 Support the ONKEY of Dialog DA9063 and DA9062 Power Management ICs 622 as an input device capable of reporting the power button status. 623 624 To compile this driver as a module, choose M here: the module 625 will be called da9063_onkey. 626 627config INPUT_DM355EVM 628 tristate "TI DaVinci DM355 EVM Keypad and IR Remote" 629 depends on MFD_DM355EVM_MSP 630 select INPUT_SPARSEKMAP 631 help 632 Supports the pushbuttons and IR remote used with 633 the DM355 EVM board. 634 635 To compile this driver as a module, choose M here: the 636 module will be called dm355evm_keys. 637 638config INPUT_BFIN_ROTARY 639 tristate "Blackfin Rotary support" 640 depends on BF54x || BF52x 641 help 642 Say Y here if you want to use the Blackfin Rotary. 643 644 To compile this driver as a module, choose M here: the 645 module will be called bfin-rotary. 646 647config INPUT_WM831X_ON 648 tristate "WM831X ON pin" 649 depends on MFD_WM831X 650 help 651 Support the ON pin of WM831X PMICs as an input device 652 reporting power button status. 653 654 To compile this driver as a module, choose M here: the module 655 will be called wm831x_on. 656 657config INPUT_PCAP 658 tristate "Motorola EZX PCAP misc input events" 659 depends on EZX_PCAP 660 help 661 Say Y here if you want to use Power key and Headphone button 662 on Motorola EZX phones. 663 664 To compile this driver as a module, choose M here: the 665 module will be called pcap_keys. 666 667config INPUT_ADXL34X 668 tristate "Analog Devices ADXL34x Three-Axis Digital Accelerometer" 669 default n 670 help 671 Say Y here if you have a Accelerometer interface using the 672 ADXL345/6 controller, and your board-specific initialization 673 code includes that in its table of devices. 674 675 This driver can use either I2C or SPI communication to the 676 ADXL345/6 controller. Select the appropriate method for 677 your system. 678 679 If unsure, say N (but it's safe to say "Y"). 680 681 To compile this driver as a module, choose M here: the 682 module will be called adxl34x. 683 684config INPUT_ADXL34X_I2C 685 tristate "support I2C bus connection" 686 depends on INPUT_ADXL34X && I2C 687 default y 688 help 689 Say Y here if you have ADXL345/6 hooked to an I2C bus. 690 691 To compile this driver as a module, choose M here: the 692 module will be called adxl34x-i2c. 693 694config INPUT_ADXL34X_SPI 695 tristate "support SPI bus connection" 696 depends on INPUT_ADXL34X && SPI 697 default y 698 help 699 Say Y here if you have ADXL345/6 hooked to a SPI bus. 700 701 To compile this driver as a module, choose M here: the 702 module will be called adxl34x-spi. 703 704config INPUT_IMS_PCU 705 tristate "IMS Passenger Control Unit driver" 706 depends on USB 707 depends on LEDS_CLASS 708 help 709 Say Y here if you have system with IMS Rave Passenger Control Unit. 710 711 To compile this driver as a module, choose M here: the module will be 712 called ims_pcu. 713 714config INPUT_CMA3000 715 tristate "VTI CMA3000 Tri-axis accelerometer" 716 help 717 Say Y here if you want to use VTI CMA3000_D0x Accelerometer 718 driver 719 720 This driver currently only supports I2C interface to the 721 controller. Also select the I2C method. 722 723 If unsure, say N 724 725 To compile this driver as a module, choose M here: the 726 module will be called cma3000_d0x. 727 728config INPUT_CMA3000_I2C 729 tristate "Support I2C bus connection" 730 depends on INPUT_CMA3000 && I2C 731 help 732 Say Y here if you want to use VTI CMA3000_D0x Accelerometer 733 through I2C interface. 734 735 To compile this driver as a module, choose M here: the 736 module will be called cma3000_d0x_i2c. 737 738config INPUT_XEN_KBDDEV_FRONTEND 739 tristate "Xen virtual keyboard and mouse support" 740 depends on XEN 741 default y 742 select XEN_XENBUS_FRONTEND 743 help 744 This driver implements the front-end of the Xen virtual 745 keyboard and mouse device driver. It communicates with a back-end 746 in another domain. 747 748 To compile this driver as a module, choose M here: the 749 module will be called xen-kbdfront. 750 751config INPUT_SIRFSOC_ONKEY 752 bool "CSR SiRFSoC power on/off/suspend key support" 753 depends on ARCH_SIRF && OF 754 default y 755 help 756 Say Y here if you want to support for the SiRFSoC power on/off/suspend key 757 in Linux, after you press the onkey, system will suspend. 758 759 If unsure, say N. 760 761config INPUT_IDEAPAD_SLIDEBAR 762 tristate "IdeaPad Laptop Slidebar" 763 depends on INPUT 764 depends on SERIO_I8042 765 help 766 Say Y here if you have an IdeaPad laptop with a slidebar. 767 768 To compile this driver as a module, choose M here: the 769 module will be called ideapad_slidebar. 770 771config INPUT_SOC_BUTTON_ARRAY 772 tristate "Windows-compatible SoC Button Array" 773 depends on KEYBOARD_GPIO 774 help 775 Say Y here if you have a SoC-based tablet that originally 776 runs Windows 8. 777 778 To compile this driver as a module, choose M here: the 779 module will be called soc_button_array. 780 781config INPUT_DRV260X_HAPTICS 782 tristate "TI DRV260X haptics support" 783 depends on INPUT && I2C 784 depends on GPIOLIB || COMPILE_TEST 785 select INPUT_FF_MEMLESS 786 select REGMAP_I2C 787 help 788 Say Y to enable support for the TI DRV260X haptics driver. 789 790 To compile this driver as a module, choose M here: the 791 module will be called drv260x-haptics. 792 793config INPUT_DRV2665_HAPTICS 794 tristate "TI DRV2665 haptics support" 795 depends on INPUT && I2C 796 select INPUT_FF_MEMLESS 797 select REGMAP_I2C 798 help 799 Say Y to enable support for the TI DRV2665 haptics driver. 800 801 To compile this driver as a module, choose M here: the 802 module will be called drv2665-haptics. 803 804config INPUT_DRV2667_HAPTICS 805 tristate "TI DRV2667 haptics support" 806 depends on INPUT && I2C 807 select INPUT_FF_MEMLESS 808 select REGMAP_I2C 809 help 810 Say Y to enable support for the TI DRV2667 haptics driver. 811 812 To compile this driver as a module, choose M here: the 813 module will be called drv2667-haptics. 814 815endif 816