Kconfig 21 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662663664665666667668669670671672673674675676677678679680681682683684685686687688689690691692693694695696697698699700701702703704705706707708709710711712713714715716717718719720721722
  1. #
  2. # Input misc drivers configuration
  3. #
  4. menuconfig 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. If unsure, say Y.
  11. if INPUT_MISC
  12. config INPUT_88PM860X_ONKEY
  13. tristate "88PM860x ONKEY support"
  14. depends on MFD_88PM860X
  15. help
  16. Support the ONKEY of Marvell 88PM860x PMICs as an input device
  17. reporting power button status.
  18. To compile this driver as a module, choose M here: the module
  19. will be called 88pm860x_onkey.
  20. config INPUT_88PM80X_ONKEY
  21. tristate "88PM80x ONKEY support"
  22. depends on MFD_88PM800
  23. help
  24. Support the ONKEY of Marvell 88PM80x PMICs as an input device
  25. reporting power button status.
  26. To compile this driver as a module, choose M here: the module
  27. will be called 88pm80x_onkey.
  28. config INPUT_AB8500_PONKEY
  29. tristate "AB8500 Pon (PowerOn) Key"
  30. depends on AB8500_CORE
  31. help
  32. Say Y here to use the PowerOn Key for ST-Ericsson's AB8500
  33. Mix-Sig PMIC.
  34. To compile this driver as a module, choose M here: the module
  35. will be called ab8500-ponkey.
  36. config INPUT_AD714X
  37. tristate "Analog Devices AD714x Capacitance Touch Sensor"
  38. help
  39. Say Y here if you want to support an AD7142/3/7/8/7A touch sensor.
  40. You should select a bus connection too.
  41. To compile this driver as a module, choose M here: the
  42. module will be called ad714x.
  43. config INPUT_AD714X_I2C
  44. tristate "support I2C bus connection"
  45. depends on INPUT_AD714X && I2C
  46. default y
  47. help
  48. Say Y here if you have AD7142/AD7147 hooked to an I2C bus.
  49. To compile this driver as a module, choose M here: the
  50. module will be called ad714x-i2c.
  51. config INPUT_AD714X_SPI
  52. tristate "support SPI bus connection"
  53. depends on INPUT_AD714X && SPI
  54. default y
  55. help
  56. Say Y here if you have AD7142/AD7147 hooked to a SPI bus.
  57. To compile this driver as a module, choose M here: the
  58. module will be called ad714x-spi.
  59. config INPUT_ARIZONA_HAPTICS
  60. tristate "Arizona haptics support"
  61. depends on MFD_ARIZONA && SND_SOC
  62. select INPUT_FF_MEMLESS
  63. help
  64. Say Y to enable support for the haptics module in Arizona CODECs.
  65. To compile this driver as a module, choose M here: the
  66. module will be called arizona-haptics.
  67. config INPUT_BMA150
  68. tristate "BMA150/SMB380 acceleration sensor support"
  69. depends on I2C
  70. select INPUT_POLLDEV
  71. help
  72. Say Y here if you have Bosch Sensortec's BMA150 or SMB380
  73. acceleration sensor hooked to an I2C bus.
  74. To compile this driver as a module, choose M here: the
  75. module will be called bma150.
  76. config INPUT_PCSPKR
  77. tristate "PC Speaker support"
  78. depends on PCSPKR_PLATFORM
  79. help
  80. Say Y here if you want the standard PC Speaker to be used for
  81. bells and whistles.
  82. If unsure, say Y.
  83. To compile this driver as a module, choose M here: the
  84. module will be called pcspkr.
  85. config INPUT_PM8XXX_VIBRATOR
  86. tristate "Qualcomm PM8XXX vibrator support"
  87. depends on MFD_PM8XXX
  88. select INPUT_FF_MEMLESS
  89. help
  90. This option enables device driver support for the vibrator
  91. on Qualcomm PM8xxx chip. This driver supports ff-memless interface
  92. from input framework.
  93. To compile this driver as module, choose M here: the
  94. module will be called pm8xxx-vibrator.
  95. config INPUT_PMIC8XXX_PWRKEY
  96. tristate "PMIC8XXX power key support"
  97. depends on MFD_PM8XXX
  98. help
  99. Say Y here if you want support for the PMIC8XXX power key.
  100. If unsure, say N.
  101. To compile this driver as a module, choose M here: the
  102. module will be called pmic8xxx-pwrkey.
  103. config INPUT_SPARCSPKR
  104. tristate "SPARC Speaker support"
  105. depends on PCI && SPARC64
  106. help
  107. Say Y here if you want the standard Speaker on Sparc PCI systems
  108. to be used for bells and whistles.
  109. If unsure, say Y.
  110. To compile this driver as a module, choose M here: the
  111. module will be called sparcspkr.
  112. config INPUT_M68K_BEEP
  113. tristate "M68k Beeper support"
  114. depends on M68K
  115. config INPUT_MAX77693_HAPTIC
  116. tristate "MAXIM MAX77693 haptic controller support"
  117. depends on MFD_MAX77693 && PWM
  118. select INPUT_FF_MEMLESS
  119. help
  120. This option enables support for the haptic controller on
  121. MAXIM MAX77693 chip.
  122. To compile this driver as module, choose M here: the
  123. module will be called max77693-haptic.
  124. config INPUT_MAX8925_ONKEY
  125. tristate "MAX8925 ONKEY support"
  126. depends on MFD_MAX8925
  127. help
  128. Support the ONKEY of MAX8925 PMICs as an input device
  129. reporting power button status.
  130. To compile this driver as a module, choose M here: the module
  131. will be called max8925_onkey.
  132. config INPUT_MAX8997_HAPTIC
  133. tristate "MAXIM MAX8997 haptic controller support"
  134. depends on PWM && MFD_MAX8997
  135. select INPUT_FF_MEMLESS
  136. help
  137. This option enables device driver support for the haptic controller
  138. on MAXIM MAX8997 chip. This driver supports ff-memless interface
  139. from input framework.
  140. To compile this driver as module, choose M here: the
  141. module will be called max8997-haptic.
  142. config INPUT_MC13783_PWRBUTTON
  143. tristate "MC13783 ON buttons"
  144. depends on MFD_MC13XXX
  145. help
  146. Support the ON buttons of MC13783 PMIC as an input device
  147. reporting power button status.
  148. To compile this driver as a module, choose M here: the module
  149. will be called mc13783-pwrbutton.
  150. config INPUT_MMA8450
  151. tristate "MMA8450 - Freescale's 3-Axis, 8/12-bit Digital Accelerometer"
  152. depends on I2C
  153. select INPUT_POLLDEV
  154. help
  155. Say Y here if you want to support Freescale's MMA8450 Accelerometer
  156. through I2C interface.
  157. To compile this driver as a module, choose M here: the
  158. module will be called mma8450.
  159. config INPUT_MPU3050
  160. tristate "MPU3050 Triaxial gyroscope sensor"
  161. depends on I2C
  162. help
  163. Say Y here if you want to support InvenSense MPU3050
  164. connected via an I2C bus.
  165. To compile this driver as a module, choose M here: the
  166. module will be called mpu3050.
  167. config INPUT_APANEL
  168. tristate "Fujitsu Lifebook Application Panel buttons"
  169. depends on X86 && I2C && LEDS_CLASS
  170. select INPUT_POLLDEV
  171. select CHECK_SIGNATURE
  172. help
  173. Say Y here for support of the Application Panel buttons, used on
  174. Fujitsu Lifebook. These are attached to the mainboard through
  175. an SMBus interface managed by the I2C Intel ICH (i801) driver,
  176. which you should also build for this kernel.
  177. To compile this driver as a module, choose M here: the module will
  178. be called apanel.
  179. config INPUT_GP2A
  180. tristate "Sharp GP2AP002A00F I2C Proximity/Opto sensor driver"
  181. depends on I2C
  182. depends on GPIOLIB
  183. help
  184. Say Y here if you have a Sharp GP2AP002A00F proximity/als combo-chip
  185. hooked to an I2C bus.
  186. To compile this driver as a module, choose M here: the
  187. module will be called gp2ap002a00f.
  188. config INPUT_GPIO_BEEPER
  189. tristate "Generic GPIO Beeper support"
  190. depends on GPIOLIB
  191. help
  192. Say Y here if you have a beeper connected to a GPIO pin.
  193. To compile this driver as a module, choose M here: the
  194. module will be called gpio-beeper.
  195. config INPUT_GPIO_TILT_POLLED
  196. tristate "Polled GPIO tilt switch"
  197. depends on GPIOLIB
  198. select INPUT_POLLDEV
  199. help
  200. This driver implements support for tilt switches connected
  201. to GPIO pins that are not capable of generating interrupts.
  202. The list of gpios to use and the mapping of their states
  203. to specific angles is done via platform data.
  204. To compile this driver as a module, choose M here: the
  205. module will be called gpio_tilt_polled.
  206. config INPUT_IXP4XX_BEEPER
  207. tristate "IXP4XX Beeper support"
  208. depends on ARCH_IXP4XX
  209. help
  210. If you say yes here, you can connect a beeper to the
  211. ixp4xx gpio pins. This is used by the LinkSys NSLU2.
  212. If unsure, say Y.
  213. To compile this driver as a module, choose M here: the
  214. module will be called ixp4xx-beeper.
  215. config INPUT_COBALT_BTNS
  216. tristate "Cobalt button interface"
  217. depends on MIPS_COBALT
  218. select INPUT_POLLDEV
  219. help
  220. Say Y here if you want to support MIPS Cobalt button interface.
  221. To compile this driver as a module, choose M here: the
  222. module will be called cobalt_btns.
  223. config INPUT_WISTRON_BTNS
  224. tristate "x86 Wistron laptop button interface"
  225. depends on X86_32
  226. select INPUT_POLLDEV
  227. select INPUT_SPARSEKMAP
  228. select NEW_LEDS
  229. select LEDS_CLASS
  230. select CHECK_SIGNATURE
  231. help
  232. Say Y here for support of Wistron laptop button interfaces, used on
  233. laptops of various brands, including Acer and Fujitsu-Siemens. If
  234. available, mail and wifi LEDs will be controllable via /sys/class/leds.
  235. To compile this driver as a module, choose M here: the module will
  236. be called wistron_btns.
  237. config INPUT_ATLAS_BTNS
  238. tristate "x86 Atlas button interface"
  239. depends on X86 && ACPI
  240. help
  241. Say Y here for support of Atlas wallmount touchscreen buttons.
  242. The events will show up as scancodes F1 through F9 via evdev.
  243. To compile this driver as a module, choose M here: the module will
  244. be called atlas_btns.
  245. config INPUT_ATI_REMOTE2
  246. tristate "ATI / Philips USB RF remote control"
  247. depends on USB_ARCH_HAS_HCD
  248. select USB
  249. help
  250. Say Y here if you want to use an ATI or Philips USB RF remote control.
  251. These are RF remotes with USB receivers.
  252. ATI Remote Wonder II comes with some ATI's All-In-Wonder video cards
  253. and is also available as a separate product.
  254. This driver provides mouse pointer, left and right mouse buttons,
  255. and maps all the other remote buttons to keypress events.
  256. To compile this driver as a module, choose M here: the module will be
  257. called ati_remote2.
  258. config INPUT_KEYSPAN_REMOTE
  259. tristate "Keyspan DMR USB remote control"
  260. depends on USB_ARCH_HAS_HCD
  261. select USB
  262. help
  263. Say Y here if you want to use a Keyspan DMR USB remote control.
  264. Currently only the UIA-11 type of receiver has been tested. The tag
  265. on the receiver that connects to the USB port should have a P/N that
  266. will tell you what type of DMR you have. The UIA-10 type is not
  267. supported at this time. This driver maps all buttons to keypress
  268. events.
  269. To compile this driver as a module, choose M here: the module will
  270. be called keyspan_remote.
  271. config INPUT_KXTJ9
  272. tristate "Kionix KXTJ9 tri-axis digital accelerometer"
  273. depends on I2C
  274. help
  275. Say Y here to enable support for the Kionix KXTJ9 digital tri-axis
  276. accelerometer.
  277. To compile this driver as a module, choose M here: the module will
  278. be called kxtj9.
  279. config INPUT_KXTJ9_POLLED_MODE
  280. bool "Enable polling mode support"
  281. depends on INPUT_KXTJ9
  282. select INPUT_POLLDEV
  283. help
  284. Say Y here if you need accelerometer to work in polling mode.
  285. config INPUT_POWERMATE
  286. tristate "Griffin PowerMate and Contour Jog support"
  287. depends on USB_ARCH_HAS_HCD
  288. select USB
  289. help
  290. Say Y here if you want to use Griffin PowerMate or Contour Jog devices.
  291. These are aluminum dials which can measure clockwise and anticlockwise
  292. rotation. The dial also acts as a pushbutton. The base contains an LED
  293. which can be instructed to pulse or to switch to a particular intensity.
  294. You can download userspace tools from
  295. <http://sowerbutts.com/powermate/>.
  296. To compile this driver as a module, choose M here: the
  297. module will be called powermate.
  298. config INPUT_YEALINK
  299. tristate "Yealink usb-p1k voip phone"
  300. depends on USB_ARCH_HAS_HCD
  301. select USB
  302. help
  303. Say Y here if you want to enable keyboard and LCD functions of the
  304. Yealink usb-p1k usb phones. The audio part is enabled by the generic
  305. usb sound driver, so you might want to enable that as well.
  306. For information about how to use these additional functions, see
  307. <file:Documentation/input/yealink.txt>.
  308. To compile this driver as a module, choose M here: the module will be
  309. called yealink.
  310. config INPUT_CM109
  311. tristate "C-Media CM109 USB I/O Controller"
  312. depends on USB_ARCH_HAS_HCD
  313. select USB
  314. help
  315. Say Y here if you want to enable keyboard and buzzer functions of the
  316. C-Media CM109 usb phones. The audio part is enabled by the generic
  317. usb sound driver, so you might want to enable that as well.
  318. To compile this driver as a module, choose M here: the module will be
  319. called cm109.
  320. config INPUT_RETU_PWRBUTTON
  321. tristate "Retu Power button Driver"
  322. depends on MFD_RETU
  323. help
  324. Say Y here if you want to enable power key reporting via the
  325. Retu chips found in Nokia Internet Tablets (770, N800, N810).
  326. To compile this driver as a module, choose M here. The module will
  327. be called retu-pwrbutton.
  328. config INPUT_TWL4030_PWRBUTTON
  329. tristate "TWL4030 Power button Driver"
  330. depends on TWL4030_CORE
  331. help
  332. Say Y here if you want to enable power key reporting via the
  333. TWL4030 family of chips.
  334. To compile this driver as a module, choose M here. The module will
  335. be called twl4030_pwrbutton.
  336. config INPUT_TWL4030_VIBRA
  337. tristate "Support for TWL4030 Vibrator"
  338. depends on TWL4030_CORE
  339. select MFD_TWL4030_AUDIO
  340. select INPUT_FF_MEMLESS
  341. help
  342. This option enables support for TWL4030 Vibrator Driver.
  343. To compile this driver as a module, choose M here. The module will
  344. be called twl4030_vibra.
  345. config INPUT_TWL6040_VIBRA
  346. tristate "Support for TWL6040 Vibrator"
  347. depends on TWL6040_CORE
  348. select INPUT_FF_MEMLESS
  349. help
  350. This option enables support for TWL6040 Vibrator Driver.
  351. To compile this driver as a module, choose M here. The module will
  352. be called twl6040_vibra.
  353. config INPUT_UINPUT
  354. tristate "User level driver support"
  355. help
  356. Say Y here if you want to support user level drivers for input
  357. subsystem accessible under char device 10:223 - /dev/input/uinput.
  358. To compile this driver as a module, choose M here: the
  359. module will be called uinput.
  360. config INPUT_SGI_BTNS
  361. tristate "SGI Indy/O2 volume button interface"
  362. depends on SGI_IP22 || SGI_IP32
  363. select INPUT_POLLDEV
  364. help
  365. Say Y here if you want to support SGI Indy/O2 volume button interface.
  366. To compile this driver as a module, choose M here: the
  367. module will be called sgi_btns.
  368. config HP_SDC_RTC
  369. tristate "HP SDC Real Time Clock"
  370. depends on (GSC || HP300) && SERIO
  371. select HP_SDC
  372. help
  373. Say Y here if you want to support the built-in real time clock
  374. of the HP SDC controller.
  375. config INPUT_PALMAS_PWRBUTTON
  376. tristate "Palmas Power button Driver"
  377. depends on MFD_PALMAS
  378. help
  379. Say Y here if you want to enable power key reporting via the
  380. Palmas family of PMICs.
  381. To compile this driver as a module, choose M here. The module will
  382. be called palmas_pwrbutton.
  383. config INPUT_PCF50633_PMU
  384. tristate "PCF50633 PMU events"
  385. depends on MFD_PCF50633
  386. help
  387. Say Y to include support for delivering PMU events via input
  388. layer on NXP PCF50633.
  389. config INPUT_PCF8574
  390. tristate "PCF8574 Keypad input device"
  391. depends on I2C
  392. help
  393. Say Y here if you want to support a keypad connected via I2C
  394. with a PCF8574.
  395. To compile this driver as a module, choose M here: the
  396. module will be called pcf8574_keypad.
  397. config INPUT_PWM_BEEPER
  398. tristate "PWM beeper support"
  399. depends on PWM
  400. help
  401. Say Y here to get support for PWM based beeper devices.
  402. If unsure, say N.
  403. To compile this driver as a module, choose M here: the module will be
  404. called pwm-beeper.
  405. config INPUT_GPIO_ROTARY_ENCODER
  406. tristate "Rotary encoders connected to GPIO pins"
  407. depends on GPIOLIB
  408. help
  409. Say Y here to add support for rotary encoders connected to GPIO lines.
  410. Check file:Documentation/input/rotary-encoder.txt for more
  411. information.
  412. To compile this driver as a module, choose M here: the
  413. module will be called rotary_encoder.
  414. config INPUT_RB532_BUTTON
  415. tristate "Mikrotik Routerboard 532 button interface"
  416. depends on MIKROTIK_RB532
  417. depends on GPIOLIB
  418. select INPUT_POLLDEV
  419. help
  420. Say Y here if you want support for the S1 button built into
  421. Mikrotik's Routerboard 532.
  422. To compile this driver as a module, choose M here: the
  423. module will be called rb532_button.
  424. config INPUT_DA9052_ONKEY
  425. tristate "Dialog DA9052/DA9053 Onkey"
  426. depends on PMIC_DA9052
  427. help
  428. Support the ONKEY of Dialog DA9052 PMICs as an input device
  429. reporting power button status.
  430. To compile this driver as a module, choose M here: the
  431. module will be called da9052_onkey.
  432. config INPUT_DA9055_ONKEY
  433. tristate "Dialog Semiconductor DA9055 ONKEY"
  434. depends on MFD_DA9055
  435. help
  436. Support the ONKEY of DA9055 PMICs as an input device
  437. reporting power button status.
  438. To compile this driver as a module, choose M here: the module
  439. will be called da9055_onkey.
  440. config INPUT_DM355EVM
  441. tristate "TI DaVinci DM355 EVM Keypad and IR Remote"
  442. depends on MFD_DM355EVM_MSP
  443. select INPUT_SPARSEKMAP
  444. help
  445. Supports the pushbuttons and IR remote used with
  446. the DM355 EVM board.
  447. To compile this driver as a module, choose M here: the
  448. module will be called dm355evm_keys.
  449. config INPUT_BFIN_ROTARY
  450. tristate "Blackfin Rotary support"
  451. depends on BF54x || BF52x
  452. help
  453. Say Y here if you want to use the Blackfin Rotary.
  454. To compile this driver as a module, choose M here: the
  455. module will be called bfin-rotary.
  456. config INPUT_WM831X_ON
  457. tristate "WM831X ON pin"
  458. depends on MFD_WM831X
  459. help
  460. Support the ON pin of WM831X PMICs as an input device
  461. reporting power button status.
  462. To compile this driver as a module, choose M here: the module
  463. will be called wm831x_on.
  464. config INPUT_PCAP
  465. tristate "Motorola EZX PCAP misc input events"
  466. depends on EZX_PCAP
  467. help
  468. Say Y here if you want to use Power key and Headphone button
  469. on Motorola EZX phones.
  470. To compile this driver as a module, choose M here: the
  471. module will be called pcap_keys.
  472. config INPUT_ADXL34X
  473. tristate "Analog Devices ADXL34x Three-Axis Digital Accelerometer"
  474. default n
  475. help
  476. Say Y here if you have a Accelerometer interface using the
  477. ADXL345/6 controller, and your board-specific initialization
  478. code includes that in its table of devices.
  479. This driver can use either I2C or SPI communication to the
  480. ADXL345/6 controller. Select the appropriate method for
  481. your system.
  482. If unsure, say N (but it's safe to say "Y").
  483. To compile this driver as a module, choose M here: the
  484. module will be called adxl34x.
  485. config INPUT_ADXL34X_I2C
  486. tristate "support I2C bus connection"
  487. depends on INPUT_ADXL34X && I2C
  488. default y
  489. help
  490. Say Y here if you have ADXL345/6 hooked to an I2C bus.
  491. To compile this driver as a module, choose M here: the
  492. module will be called adxl34x-i2c.
  493. config INPUT_ADXL34X_SPI
  494. tristate "support SPI bus connection"
  495. depends on INPUT_ADXL34X && SPI
  496. default y
  497. help
  498. Say Y here if you have ADXL345/6 hooked to a SPI bus.
  499. To compile this driver as a module, choose M here: the
  500. module will be called adxl34x-spi.
  501. config INPUT_IMS_PCU
  502. tristate "IMS Passenger Control Unit driver"
  503. depends on USB
  504. depends on LEDS_CLASS
  505. help
  506. Say Y here if you have system with IMS Rave Passenger Control Unit.
  507. To compile this driver as a module, choose M here: the module will be
  508. called ims_pcu.
  509. config INPUT_CMA3000
  510. tristate "VTI CMA3000 Tri-axis accelerometer"
  511. help
  512. Say Y here if you want to use VTI CMA3000_D0x Accelerometer
  513. driver
  514. This driver currently only supports I2C interface to the
  515. controller. Also select the I2C method.
  516. If unsure, say N
  517. To compile this driver as a module, choose M here: the
  518. module will be called cma3000_d0x.
  519. config INPUT_CMA3000_I2C
  520. tristate "Support I2C bus connection"
  521. depends on INPUT_CMA3000 && I2C
  522. help
  523. Say Y here if you want to use VTI CMA3000_D0x Accelerometer
  524. through I2C interface.
  525. To compile this driver as a module, choose M here: the
  526. module will be called cma3000_d0x_i2c.
  527. config INPUT_XEN_KBDDEV_FRONTEND
  528. tristate "Xen virtual keyboard and mouse support"
  529. depends on XEN
  530. default y
  531. select XEN_XENBUS_FRONTEND
  532. help
  533. This driver implements the front-end of the Xen virtual
  534. keyboard and mouse device driver. It communicates with a back-end
  535. in another domain.
  536. To compile this driver as a module, choose M here: the
  537. module will be called xen-kbdfront.
  538. config INPUT_SIRFSOC_ONKEY
  539. bool "CSR SiRFSoC power on/off/suspend key support"
  540. depends on ARCH_SIRF && OF
  541. default y
  542. help
  543. Say Y here if you want to support for the SiRFSoC power on/off/suspend key
  544. in Linux, after you press the onkey, system will suspend.
  545. If unsure, say N.
  546. config INPUT_IDEAPAD_SLIDEBAR
  547. tristate "IdeaPad Laptop Slidebar"
  548. depends on INPUT
  549. depends on SERIO_I8042
  550. help
  551. Say Y here if you have an IdeaPad laptop with a slidebar.
  552. To compile this driver as a module, choose M here: the
  553. module will be called ideapad_slidebar.
  554. config INPUT_SOC_BUTTON_ARRAY
  555. tristate "Windows-compatible SoC Button Array"
  556. depends on KEYBOARD_GPIO
  557. help
  558. Say Y here if you have a SoC-based tablet that originally
  559. runs Windows 8.
  560. To compile this driver as a module, choose M here: the
  561. module will be called soc_button_array.
  562. config INPUT_DRV260X_HAPTICS
  563. tristate "TI DRV260X haptics support"
  564. depends on INPUT && I2C && GPIOLIB
  565. select INPUT_FF_MEMLESS
  566. select REGMAP_I2C
  567. help
  568. Say Y to enable support for the TI DRV260X haptics driver.
  569. To compile this driver as a module, choose M here: the
  570. module will be called drv260x-haptics.
  571. config INPUT_DRV2667_HAPTICS
  572. tristate "TI DRV2667 haptics support"
  573. depends on INPUT && I2C
  574. select INPUT_FF_MEMLESS
  575. select REGMAP_I2C
  576. help
  577. Say Y to enable support for the TI DRV2667 haptics driver.
  578. To compile this driver as a module, choose M here: the
  579. module will be called drv260x-haptics.
  580. endif