Kconfig 24 KB

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