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_KEYSPAN_REMOTE 345 tristate "Keyspan DMR USB remote control" 346 depends on USB_ARCH_HAS_HCD 347 select USB 348 help 349 Say Y here if you want to use a Keyspan DMR USB remote control. 350 Currently only the UIA-11 type of receiver has been tested. The tag 351 on the receiver that connects to the USB port should have a P/N that 352 will tell you what type of DMR you have. The UIA-10 type is not 353 supported at this time. This driver maps all buttons to keypress 354 events. 355 356 To compile this driver as a module, choose M here: the module will 357 be called keyspan_remote. 358 359config INPUT_KXTJ9 360 tristate "Kionix KXTJ9 tri-axis digital accelerometer" 361 depends on I2C 362 help 363 Say Y here to enable support for the Kionix KXTJ9 digital tri-axis 364 accelerometer. 365 366 To compile this driver as a module, choose M here: the module will 367 be called kxtj9. 368 369config INPUT_KXTJ9_POLLED_MODE 370 bool "Enable polling mode support" 371 depends on INPUT_KXTJ9 372 select INPUT_POLLDEV 373 help 374 Say Y here if you need accelerometer to work in polling mode. 375 376config INPUT_POWERMATE 377 tristate "Griffin PowerMate and Contour Jog support" 378 depends on USB_ARCH_HAS_HCD 379 select USB 380 help 381 Say Y here if you want to use Griffin PowerMate or Contour Jog devices. 382 These are aluminum dials which can measure clockwise and anticlockwise 383 rotation. The dial also acts as a pushbutton. The base contains an LED 384 which can be instructed to pulse or to switch to a particular intensity. 385 386 You can download userspace tools from 387 <http://sowerbutts.com/powermate/>. 388 389 To compile this driver as a module, choose M here: the 390 module will be called powermate. 391 392config INPUT_YEALINK 393 tristate "Yealink usb-p1k voip phone" 394 depends on USB_ARCH_HAS_HCD 395 select USB 396 help 397 Say Y here if you want to enable keyboard and LCD functions of the 398 Yealink usb-p1k usb phones. The audio part is enabled by the generic 399 usb sound driver, so you might want to enable that as well. 400 401 For information about how to use these additional functions, see 402 <file:Documentation/input/yealink.txt>. 403 404 To compile this driver as a module, choose M here: the module will be 405 called yealink. 406 407config INPUT_CM109 408 tristate "C-Media CM109 USB I/O Controller" 409 depends on USB_ARCH_HAS_HCD 410 select USB 411 help 412 Say Y here if you want to enable keyboard and buzzer functions of the 413 C-Media CM109 usb phones. The audio part is enabled by the generic 414 usb sound driver, so you might want to enable that as well. 415 416 To compile this driver as a module, choose M here: the module will be 417 called cm109. 418 419config INPUT_REGULATOR_HAPTIC 420 tristate "Regulator haptics support" 421 depends on REGULATOR 422 select INPUT_FF_MEMLESS 423 help 424 This option enables device driver support for the haptic controlled 425 by a regulator. This driver supports ff-memless interface 426 from input framework. 427 428 To compile this driver as a module, choose M here: the 429 module will be called regulator-haptic. 430 431config INPUT_RETU_PWRBUTTON 432 tristate "Retu Power button Driver" 433 depends on MFD_RETU 434 help 435 Say Y here if you want to enable power key reporting via the 436 Retu chips found in Nokia Internet Tablets (770, N800, N810). 437 438 To compile this driver as a module, choose M here. The module will 439 be called retu-pwrbutton. 440 441config INPUT_TPS65218_PWRBUTTON 442 tristate "TPS65218 Power button driver" 443 depends on MFD_TPS65218 444 help 445 Say Y here if you want to enable power buttong reporting for 446 the TPS65218 Power Management IC device. 447 448 To compile this driver as a module, choose M here. The module will 449 be called tps65218-pwrbutton. 450 451config INPUT_AXP20X_PEK 452 tristate "X-Powers AXP20X power button driver" 453 depends on MFD_AXP20X 454 help 455 Say Y here if you want to enable power key reporting via the 456 AXP20X PMIC. 457 458 To compile this driver as a module, choose M here. The module will 459 be called axp20x-pek. 460 461 462config INPUT_TWL4030_PWRBUTTON 463 tristate "TWL4030 Power button Driver" 464 depends on TWL4030_CORE 465 help 466 Say Y here if you want to enable power key reporting via the 467 TWL4030 family of chips. 468 469 To compile this driver as a module, choose M here. The module will 470 be called twl4030_pwrbutton. 471 472config INPUT_TWL4030_VIBRA 473 tristate "Support for TWL4030 Vibrator" 474 depends on TWL4030_CORE 475 select MFD_TWL4030_AUDIO 476 select INPUT_FF_MEMLESS 477 help 478 This option enables support for TWL4030 Vibrator Driver. 479 480 To compile this driver as a module, choose M here. The module will 481 be called twl4030_vibra. 482 483config INPUT_TWL6040_VIBRA 484 tristate "Support for TWL6040 Vibrator" 485 depends on TWL6040_CORE 486 select INPUT_FF_MEMLESS 487 help 488 This option enables support for TWL6040 Vibrator Driver. 489 490 To compile this driver as a module, choose M here. The module will 491 be called twl6040_vibra. 492 493config INPUT_UINPUT 494 tristate "User level driver support" 495 help 496 Say Y here if you want to support user level drivers for input 497 subsystem accessible under char device 10:223 - /dev/input/uinput. 498 499 To compile this driver as a module, choose M here: the 500 module will be called uinput. 501 502config INPUT_SGI_BTNS 503 tristate "SGI Indy/O2 volume button interface" 504 depends on SGI_IP22 || SGI_IP32 505 select INPUT_POLLDEV 506 help 507 Say Y here if you want to support SGI Indy/O2 volume button interface. 508 509 To compile this driver as a module, choose M here: the 510 module will be called sgi_btns. 511 512config HP_SDC_RTC 513 tristate "HP SDC Real Time Clock" 514 depends on (GSC || HP300) && SERIO 515 select HP_SDC 516 help 517 Say Y here if you want to support the built-in real time clock 518 of the HP SDC controller. 519 520config INPUT_PALMAS_PWRBUTTON 521 tristate "Palmas Power button Driver" 522 depends on MFD_PALMAS 523 help 524 Say Y here if you want to enable power key reporting via the 525 Palmas family of PMICs. 526 527 To compile this driver as a module, choose M here. The module will 528 be called palmas_pwrbutton. 529 530config INPUT_PCF50633_PMU 531 tristate "PCF50633 PMU events" 532 depends on MFD_PCF50633 533 help 534 Say Y to include support for delivering PMU events via input 535 layer on NXP PCF50633. 536 537config INPUT_PCF8574 538 tristate "PCF8574 Keypad input device" 539 depends on I2C 540 help 541 Say Y here if you want to support a keypad connected via I2C 542 with a PCF8574. 543 544 To compile this driver as a module, choose M here: the 545 module will be called pcf8574_keypad. 546 547config INPUT_PWM_BEEPER 548 tristate "PWM beeper support" 549 depends on PWM 550 help 551 Say Y here to get support for PWM based beeper devices. 552 553 If unsure, say N. 554 555 To compile this driver as a module, choose M here: the module will be 556 called pwm-beeper. 557 558config INPUT_GPIO_ROTARY_ENCODER 559 tristate "Rotary encoders connected to GPIO pins" 560 depends on GPIOLIB || COMPILE_TEST 561 help 562 Say Y here to add support for rotary encoders connected to GPIO lines. 563 Check file:Documentation/input/rotary-encoder.txt for more 564 information. 565 566 To compile this driver as a module, choose M here: the 567 module will be called rotary_encoder. 568 569config INPUT_RB532_BUTTON 570 tristate "Mikrotik Routerboard 532 button interface" 571 depends on MIKROTIK_RB532 572 depends on GPIOLIB 573 select INPUT_POLLDEV 574 help 575 Say Y here if you want support for the S1 button built into 576 Mikrotik's Routerboard 532. 577 578 To compile this driver as a module, choose M here: the 579 module will be called rb532_button. 580 581config INPUT_DA9052_ONKEY 582 tristate "Dialog DA9052/DA9053 Onkey" 583 depends on PMIC_DA9052 584 help 585 Support the ONKEY of Dialog DA9052 PMICs as an input device 586 reporting power button status. 587 588 To compile this driver as a module, choose M here: the 589 module will be called da9052_onkey. 590 591config INPUT_DA9055_ONKEY 592 tristate "Dialog Semiconductor DA9055 ONKEY" 593 depends on MFD_DA9055 594 help 595 Support the ONKEY of DA9055 PMICs as an input device 596 reporting power button status. 597 598 To compile this driver as a module, choose M here: the module 599 will be called da9055_onkey. 600 601config INPUT_DA9063_ONKEY 602 tristate "Dialog DA9062/63 OnKey" 603 depends on MFD_DA9063 || MFD_DA9062 604 help 605 Support the ONKEY of Dialog DA9063 and DA9062 Power Management ICs 606 as an input device capable of reporting the power button status. 607 608 To compile this driver as a module, choose M here: the module 609 will be called da9063_onkey. 610 611config INPUT_DM355EVM 612 tristate "TI DaVinci DM355 EVM Keypad and IR Remote" 613 depends on MFD_DM355EVM_MSP 614 select INPUT_SPARSEKMAP 615 help 616 Supports the pushbuttons and IR remote used with 617 the DM355 EVM board. 618 619 To compile this driver as a module, choose M here: the 620 module will be called dm355evm_keys. 621 622config INPUT_BFIN_ROTARY 623 tristate "Blackfin Rotary support" 624 depends on BF54x || BF52x 625 help 626 Say Y here if you want to use the Blackfin Rotary. 627 628 To compile this driver as a module, choose M here: the 629 module will be called bfin-rotary. 630 631config INPUT_WM831X_ON 632 tristate "WM831X ON pin" 633 depends on MFD_WM831X 634 help 635 Support the ON pin of WM831X PMICs as an input device 636 reporting power button status. 637 638 To compile this driver as a module, choose M here: the module 639 will be called wm831x_on. 640 641config INPUT_PCAP 642 tristate "Motorola EZX PCAP misc input events" 643 depends on EZX_PCAP 644 help 645 Say Y here if you want to use Power key and Headphone button 646 on Motorola EZX phones. 647 648 To compile this driver as a module, choose M here: the 649 module will be called pcap_keys. 650 651config INPUT_ADXL34X 652 tristate "Analog Devices ADXL34x Three-Axis Digital Accelerometer" 653 default n 654 help 655 Say Y here if you have a Accelerometer interface using the 656 ADXL345/6 controller, and your board-specific initialization 657 code includes that in its table of devices. 658 659 This driver can use either I2C or SPI communication to the 660 ADXL345/6 controller. Select the appropriate method for 661 your system. 662 663 If unsure, say N (but it's safe to say "Y"). 664 665 To compile this driver as a module, choose M here: the 666 module will be called adxl34x. 667 668config INPUT_ADXL34X_I2C 669 tristate "support I2C bus connection" 670 depends on INPUT_ADXL34X && I2C 671 default y 672 help 673 Say Y here if you have ADXL345/6 hooked to an I2C bus. 674 675 To compile this driver as a module, choose M here: the 676 module will be called adxl34x-i2c. 677 678config INPUT_ADXL34X_SPI 679 tristate "support SPI bus connection" 680 depends on INPUT_ADXL34X && SPI 681 default y 682 help 683 Say Y here if you have ADXL345/6 hooked to a SPI bus. 684 685 To compile this driver as a module, choose M here: the 686 module will be called adxl34x-spi. 687 688config INPUT_IMS_PCU 689 tristate "IMS Passenger Control Unit driver" 690 depends on USB 691 depends on LEDS_CLASS 692 help 693 Say Y here if you have system with IMS Rave Passenger Control Unit. 694 695 To compile this driver as a module, choose M here: the module will be 696 called ims_pcu. 697 698config INPUT_CMA3000 699 tristate "VTI CMA3000 Tri-axis accelerometer" 700 help 701 Say Y here if you want to use VTI CMA3000_D0x Accelerometer 702 driver 703 704 This driver currently only supports I2C interface to the 705 controller. Also select the I2C method. 706 707 If unsure, say N 708 709 To compile this driver as a module, choose M here: the 710 module will be called cma3000_d0x. 711 712config INPUT_CMA3000_I2C 713 tristate "Support I2C bus connection" 714 depends on INPUT_CMA3000 && I2C 715 help 716 Say Y here if you want to use VTI CMA3000_D0x Accelerometer 717 through I2C interface. 718 719 To compile this driver as a module, choose M here: the 720 module will be called cma3000_d0x_i2c. 721 722config INPUT_XEN_KBDDEV_FRONTEND 723 tristate "Xen virtual keyboard and mouse support" 724 depends on XEN 725 default y 726 select XEN_XENBUS_FRONTEND 727 help 728 This driver implements the front-end of the Xen virtual 729 keyboard and mouse device driver. It communicates with a back-end 730 in another domain. 731 732 To compile this driver as a module, choose M here: the 733 module will be called xen-kbdfront. 734 735config INPUT_SIRFSOC_ONKEY 736 tristate "CSR SiRFSoC power on/off/suspend key support" 737 depends on ARCH_SIRF && OF 738 default y 739 help 740 Say Y here if you want to support for the SiRFSoC power on/off/suspend key 741 in Linux, after you press the onkey, system will suspend. 742 743 If unsure, say N. 744 745config INPUT_IDEAPAD_SLIDEBAR 746 tristate "IdeaPad Laptop Slidebar" 747 depends on INPUT 748 depends on SERIO_I8042 749 help 750 Say Y here if you have an IdeaPad laptop with a slidebar. 751 752 To compile this driver as a module, choose M here: the 753 module will be called ideapad_slidebar. 754 755config INPUT_SOC_BUTTON_ARRAY 756 tristate "Windows-compatible SoC Button Array" 757 depends on KEYBOARD_GPIO 758 help 759 Say Y here if you have a SoC-based tablet that originally 760 runs Windows 8. 761 762 To compile this driver as a module, choose M here: the 763 module will be called soc_button_array. 764 765config INPUT_DRV260X_HAPTICS 766 tristate "TI DRV260X haptics support" 767 depends on INPUT && I2C 768 depends on GPIOLIB || COMPILE_TEST 769 select INPUT_FF_MEMLESS 770 select REGMAP_I2C 771 help 772 Say Y to enable support for the TI DRV260X haptics driver. 773 774 To compile this driver as a module, choose M here: the 775 module will be called drv260x-haptics. 776 777config INPUT_DRV2665_HAPTICS 778 tristate "TI DRV2665 haptics support" 779 depends on INPUT && I2C 780 select INPUT_FF_MEMLESS 781 select REGMAP_I2C 782 help 783 Say Y to enable support for the TI DRV2665 haptics driver. 784 785 To compile this driver as a module, choose M here: the 786 module will be called drv2665-haptics. 787 788config INPUT_DRV2667_HAPTICS 789 tristate "TI DRV2667 haptics support" 790 depends on INPUT && I2C 791 select INPUT_FF_MEMLESS 792 select REGMAP_I2C 793 help 794 Say Y to enable support for the TI DRV2667 haptics driver. 795 796 To compile this driver as a module, choose M here: the 797 module will be called drv2667-haptics. 798 799endif 800