Kconfig 23 KB

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