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