Kconfig 23 KB

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