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