Kconfig 16 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547
  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_AB8500_PONKEY
  21. tristate "AB8500 Pon (PowerOn) Key"
  22. depends on AB8500_CORE
  23. help
  24. Say Y here to use the PowerOn Key for ST-Ericsson's AB8500
  25. Mix-Sig PMIC.
  26. To compile this driver as a module, choose M here: the module
  27. will be called ab8500-ponkey.
  28. config INPUT_AD714X
  29. tristate "Analog Devices AD714x Capacitance Touch Sensor"
  30. help
  31. Say Y here if you want to support an AD7142/3/7/8/7A touch sensor.
  32. You should select a bus connection too.
  33. To compile this driver as a module, choose M here: the
  34. module will be called ad714x.
  35. config INPUT_AD714X_I2C
  36. tristate "support I2C bus connection"
  37. depends on INPUT_AD714X && I2C
  38. default y
  39. help
  40. Say Y here if you have AD7142/AD7147 hooked to an I2C bus.
  41. To compile this driver as a module, choose M here: the
  42. module will be called ad714x-i2c.
  43. config INPUT_AD714X_SPI
  44. tristate "support SPI bus connection"
  45. depends on INPUT_AD714X && SPI
  46. default y
  47. help
  48. Say Y here if you have AD7142/AD7147 hooked to a SPI bus.
  49. To compile this driver as a module, choose M here: the
  50. module will be called ad714x-spi.
  51. config INPUT_BMA150
  52. tristate "BMA150/SMB380 acceleration sensor support"
  53. depends on I2C
  54. select INPUT_POLLDEV
  55. help
  56. Say Y here if you have Bosch Sensortec's BMA150 or SMB380
  57. acceleration sensor hooked to an I2C bus.
  58. To compile this driver as a module, choose M here: the
  59. module will be called bma150.
  60. config INPUT_PCSPKR
  61. tristate "PC Speaker support"
  62. depends on PCSPKR_PLATFORM
  63. help
  64. Say Y here if you want the standard PC Speaker to be used for
  65. bells and whistles.
  66. If unsure, say Y.
  67. To compile this driver as a module, choose M here: the
  68. module will be called pcspkr.
  69. config INPUT_PM8XXX_VIBRATOR
  70. tristate "Qualcomm PM8XXX vibrator support"
  71. depends on MFD_PM8XXX
  72. select INPUT_FF_MEMLESS
  73. help
  74. This option enables device driver support for the vibrator
  75. on Qualcomm PM8xxx chip. This driver supports ff-memless interface
  76. from input framework.
  77. To compile this driver as module, choose M here: the
  78. module will be called pm8xxx-vibrator.
  79. config INPUT_PMIC8XXX_PWRKEY
  80. tristate "PMIC8XXX power key support"
  81. depends on MFD_PM8XXX
  82. help
  83. Say Y here if you want support for the PMIC8XXX power key.
  84. If unsure, say N.
  85. To compile this driver as a module, choose M here: the
  86. module will be called pmic8xxx-pwrkey.
  87. config INPUT_SPARCSPKR
  88. tristate "SPARC Speaker support"
  89. depends on PCI && SPARC64
  90. help
  91. Say Y here if you want the standard Speaker on Sparc PCI systems
  92. to be used for bells and whistles.
  93. If unsure, say Y.
  94. To compile this driver as a module, choose M here: the
  95. module will be called sparcspkr.
  96. config INPUT_M68K_BEEP
  97. tristate "M68k Beeper support"
  98. depends on M68K
  99. config INPUT_MAX8925_ONKEY
  100. tristate "MAX8925 ONKEY support"
  101. depends on MFD_MAX8925
  102. help
  103. Support the ONKEY of MAX8925 PMICs as an input device
  104. reporting power button status.
  105. To compile this driver as a module, choose M here: the module
  106. will be called max8925_onkey.
  107. config INPUT_MC13783_PWRBUTTON
  108. tristate "MC13783 ON buttons"
  109. depends on MFD_MC13783
  110. help
  111. Support the ON buttons of MC13783 PMIC as an input device
  112. reporting power button status.
  113. To compile this driver as a module, choose M here: the module
  114. will be called mc13783-pwrbutton.
  115. config INPUT_MMA8450
  116. tristate "MMA8450 - Freescale's 3-Axis, 8/12-bit Digital Accelerometer"
  117. depends on I2C
  118. select INPUT_POLLDEV
  119. help
  120. Say Y here if you want to support Freescale's MMA8450 Accelerometer
  121. through I2C interface.
  122. To compile this driver as a module, choose M here: the
  123. module will be called mma8450.
  124. config INPUT_MPU3050
  125. tristate "MPU3050 Triaxial gyroscope sensor"
  126. depends on I2C
  127. help
  128. Say Y here if you want to support InvenSense MPU3050
  129. connected via an I2C bus.
  130. To compile this driver as a module, choose M here: the
  131. module will be called mpu3050.
  132. config INPUT_APANEL
  133. tristate "Fujitsu Lifebook Application Panel buttons"
  134. depends on X86 && I2C && LEDS_CLASS
  135. select INPUT_POLLDEV
  136. select CHECK_SIGNATURE
  137. help
  138. Say Y here for support of the Application Panel buttons, used on
  139. Fujitsu Lifebook. These are attached to the mainboard through
  140. an SMBus interface managed by the I2C Intel ICH (i801) driver,
  141. which you should also build for this kernel.
  142. To compile this driver as a module, choose M here: the module will
  143. be called apanel.
  144. config INPUT_IXP4XX_BEEPER
  145. tristate "IXP4XX Beeper support"
  146. depends on ARCH_IXP4XX
  147. help
  148. If you say yes here, you can connect a beeper to the
  149. ixp4xx gpio pins. This is used by the LinkSys NSLU2.
  150. If unsure, say Y.
  151. To compile this driver as a module, choose M here: the
  152. module will be called ixp4xx-beeper.
  153. config INPUT_COBALT_BTNS
  154. tristate "Cobalt button interface"
  155. depends on MIPS_COBALT
  156. select INPUT_POLLDEV
  157. help
  158. Say Y here if you want to support MIPS Cobalt button interface.
  159. To compile this driver as a module, choose M here: the
  160. module will be called cobalt_btns.
  161. config INPUT_WISTRON_BTNS
  162. tristate "x86 Wistron laptop button interface"
  163. depends on X86 && !X86_64
  164. select INPUT_POLLDEV
  165. select INPUT_SPARSEKMAP
  166. select NEW_LEDS
  167. select LEDS_CLASS
  168. select CHECK_SIGNATURE
  169. help
  170. Say Y here for support of Wistron laptop button interfaces, used on
  171. laptops of various brands, including Acer and Fujitsu-Siemens. If
  172. available, mail and wifi LEDs will be controllable via /sys/class/leds.
  173. To compile this driver as a module, choose M here: the module will
  174. be called wistron_btns.
  175. config INPUT_ATLAS_BTNS
  176. tristate "x86 Atlas button interface"
  177. depends on X86 && ACPI
  178. help
  179. Say Y here for support of Atlas wallmount touchscreen buttons.
  180. The events will show up as scancodes F1 through F9 via evdev.
  181. To compile this driver as a module, choose M here: the module will
  182. be called atlas_btns.
  183. config INPUT_ATI_REMOTE2
  184. tristate "ATI / Philips USB RF remote control"
  185. depends on USB_ARCH_HAS_HCD
  186. select USB
  187. help
  188. Say Y here if you want to use an ATI or Philips USB RF remote control.
  189. These are RF remotes with USB receivers.
  190. ATI Remote Wonder II comes with some ATI's All-In-Wonder video cards
  191. and is also available as a separate product.
  192. This driver provides mouse pointer, left and right mouse buttons,
  193. and maps all the other remote buttons to keypress events.
  194. To compile this driver as a module, choose M here: the module will be
  195. called ati_remote2.
  196. config INPUT_KEYSPAN_REMOTE
  197. tristate "Keyspan DMR USB remote control (EXPERIMENTAL)"
  198. depends on EXPERIMENTAL
  199. depends on USB_ARCH_HAS_HCD
  200. select USB
  201. help
  202. Say Y here if you want to use a Keyspan DMR USB remote control.
  203. Currently only the UIA-11 type of receiver has been tested. The tag
  204. on the receiver that connects to the USB port should have a P/N that
  205. will tell you what type of DMR you have. The UIA-10 type is not
  206. supported at this time. This driver maps all buttons to keypress
  207. events.
  208. To compile this driver as a module, choose M here: the module will
  209. be called keyspan_remote.
  210. config INPUT_KXTJ9
  211. tristate "Kionix KXTJ9 tri-axis digital accelerometer"
  212. depends on I2C
  213. help
  214. Say Y here to enable support for the Kionix KXTJ9 digital tri-axis
  215. accelerometer.
  216. To compile this driver as a module, choose M here: the module will
  217. be called kxtj9.
  218. config INPUT_KXTJ9_POLLED_MODE
  219. bool "Enable polling mode support"
  220. depends on INPUT_KXTJ9
  221. select INPUT_POLLDEV
  222. help
  223. Say Y here if you need accelerometer to work in polling mode.
  224. config INPUT_POWERMATE
  225. tristate "Griffin PowerMate and Contour Jog support"
  226. depends on USB_ARCH_HAS_HCD
  227. select USB
  228. help
  229. Say Y here if you want to use Griffin PowerMate or Contour Jog devices.
  230. These are aluminum dials which can measure clockwise and anticlockwise
  231. rotation. The dial also acts as a pushbutton. The base contains an LED
  232. which can be instructed to pulse or to switch to a particular intensity.
  233. You can download userspace tools from
  234. <http://sowerbutts.com/powermate/>.
  235. To compile this driver as a module, choose M here: the
  236. module will be called powermate.
  237. config INPUT_YEALINK
  238. tristate "Yealink usb-p1k voip phone"
  239. depends on EXPERIMENTAL
  240. depends on USB_ARCH_HAS_HCD
  241. select USB
  242. help
  243. Say Y here if you want to enable keyboard and LCD functions of the
  244. Yealink usb-p1k usb phones. The audio part is enabled by the generic
  245. usb sound driver, so you might want to enable that as well.
  246. For information about how to use these additional functions, see
  247. <file:Documentation/input/yealink.txt>.
  248. To compile this driver as a module, choose M here: the module will be
  249. called yealink.
  250. config INPUT_CM109
  251. tristate "C-Media CM109 USB I/O Controller"
  252. depends on EXPERIMENTAL
  253. depends on USB_ARCH_HAS_HCD
  254. select USB
  255. help
  256. Say Y here if you want to enable keyboard and buzzer functions of the
  257. C-Media CM109 usb phones. The audio part is enabled by the generic
  258. usb sound driver, so you might want to enable that as well.
  259. To compile this driver as a module, choose M here: the module will be
  260. called cm109.
  261. config INPUT_TWL4030_PWRBUTTON
  262. tristate "TWL4030 Power button Driver"
  263. depends on TWL4030_CORE
  264. help
  265. Say Y here if you want to enable power key reporting via the
  266. TWL4030 family of chips.
  267. To compile this driver as a module, choose M here. The module will
  268. be called twl4030_pwrbutton.
  269. config INPUT_TWL4030_VIBRA
  270. tristate "Support for TWL4030 Vibrator"
  271. depends on TWL4030_CORE
  272. select MFD_TWL4030_AUDIO
  273. select INPUT_FF_MEMLESS
  274. help
  275. This option enables support for TWL4030 Vibrator Driver.
  276. To compile this driver as a module, choose M here. The module will
  277. be called twl4030_vibra.
  278. config INPUT_TWL6040_VIBRA
  279. tristate "Support for TWL6040 Vibrator"
  280. depends on TWL4030_CORE
  281. select TWL6040_CORE
  282. select INPUT_FF_MEMLESS
  283. help
  284. This option enables support for TWL6040 Vibrator Driver.
  285. To compile this driver as a module, choose M here. The module will
  286. be called twl6040_vibra.
  287. config INPUT_UINPUT
  288. tristate "User level driver support"
  289. help
  290. Say Y here if you want to support user level drivers for input
  291. subsystem accessible under char device 10:223 - /dev/input/uinput.
  292. To compile this driver as a module, choose M here: the
  293. module will be called uinput.
  294. config INPUT_SGI_BTNS
  295. tristate "SGI Indy/O2 volume button interface"
  296. depends on SGI_IP22 || SGI_IP32
  297. select INPUT_POLLDEV
  298. help
  299. Say Y here if you want to support SGI Indy/O2 volume button interface.
  300. To compile this driver as a module, choose M here: the
  301. module will be called sgi_btns.
  302. config HP_SDC_RTC
  303. tristate "HP SDC Real Time Clock"
  304. depends on (GSC || HP300) && SERIO
  305. select HP_SDC
  306. help
  307. Say Y here if you want to support the built-in real time clock
  308. of the HP SDC controller.
  309. config INPUT_PCF50633_PMU
  310. tristate "PCF50633 PMU events"
  311. depends on MFD_PCF50633
  312. help
  313. Say Y to include support for delivering PMU events via input
  314. layer on NXP PCF50633.
  315. config INPUT_PCF8574
  316. tristate "PCF8574 Keypad input device"
  317. depends on I2C && EXPERIMENTAL
  318. help
  319. Say Y here if you want to support a keypad connetced via I2C
  320. with a PCF8574.
  321. To compile this driver as a module, choose M here: the
  322. module will be called pcf8574_keypad.
  323. config INPUT_PWM_BEEPER
  324. tristate "PWM beeper support"
  325. depends on HAVE_PWM
  326. help
  327. Say Y here to get support for PWM based beeper devices.
  328. If unsure, say N.
  329. To compile this driver as a module, choose M here: the module will be
  330. called pwm-beeper.
  331. config INPUT_GPIO_ROTARY_ENCODER
  332. tristate "Rotary encoders connected to GPIO pins"
  333. depends on GPIOLIB && GENERIC_GPIO
  334. help
  335. Say Y here to add support for rotary encoders connected to GPIO lines.
  336. Check file:Documentation/input/rotary-encoder.txt for more
  337. information.
  338. To compile this driver as a module, choose M here: the
  339. module will be called rotary_encoder.
  340. config INPUT_RB532_BUTTON
  341. tristate "Mikrotik Routerboard 532 button interface"
  342. depends on MIKROTIK_RB532
  343. depends on GPIOLIB && GENERIC_GPIO
  344. select INPUT_POLLDEV
  345. help
  346. Say Y here if you want support for the S1 button built into
  347. Mikrotik's Routerboard 532.
  348. To compile this driver as a module, choose M here: the
  349. module will be called rb532_button.
  350. config INPUT_DM355EVM
  351. tristate "TI DaVinci DM355 EVM Keypad and IR Remote"
  352. depends on MFD_DM355EVM_MSP
  353. select INPUT_SPARSEKMAP
  354. help
  355. Supports the pushbuttons and IR remote used with
  356. the DM355 EVM board.
  357. To compile this driver as a module, choose M here: the
  358. module will be called dm355evm_keys.
  359. config INPUT_BFIN_ROTARY
  360. tristate "Blackfin Rotary support"
  361. depends on BF54x || BF52x
  362. help
  363. Say Y here if you want to use the Blackfin Rotary.
  364. To compile this driver as a module, choose M here: the
  365. module will be called bfin-rotary.
  366. config INPUT_WM831X_ON
  367. tristate "WM831X ON pin"
  368. depends on MFD_WM831X
  369. help
  370. Support the ON pin of WM831X PMICs as an input device
  371. reporting power button status.
  372. To compile this driver as a module, choose M here: the module
  373. will be called wm831x_on.
  374. config INPUT_PCAP
  375. tristate "Motorola EZX PCAP misc input events"
  376. depends on EZX_PCAP
  377. help
  378. Say Y here if you want to use Power key and Headphone button
  379. on Motorola EZX phones.
  380. To compile this driver as a module, choose M here: the
  381. module will be called pcap_keys.
  382. config INPUT_ADXL34X
  383. tristate "Analog Devices ADXL34x Three-Axis Digital Accelerometer"
  384. default n
  385. help
  386. Say Y here if you have a Accelerometer interface using the
  387. ADXL345/6 controller, and your board-specific initialization
  388. code includes that in its table of devices.
  389. This driver can use either I2C or SPI communication to the
  390. ADXL345/6 controller. Select the appropriate method for
  391. your system.
  392. If unsure, say N (but it's safe to say "Y").
  393. To compile this driver as a module, choose M here: the
  394. module will be called adxl34x.
  395. config INPUT_ADXL34X_I2C
  396. tristate "support I2C bus connection"
  397. depends on INPUT_ADXL34X && I2C
  398. default y
  399. help
  400. Say Y here if you have ADXL345/6 hooked to an I2C bus.
  401. To compile this driver as a module, choose M here: the
  402. module will be called adxl34x-i2c.
  403. config INPUT_ADXL34X_SPI
  404. tristate "support SPI bus connection"
  405. depends on INPUT_ADXL34X && SPI
  406. default y
  407. help
  408. Say Y here if you have ADXL345/6 hooked to a SPI bus.
  409. To compile this driver as a module, choose M here: the
  410. module will be called adxl34x-spi.
  411. config INPUT_CMA3000
  412. tristate "VTI CMA3000 Tri-axis accelerometer"
  413. help
  414. Say Y here if you want to use VTI CMA3000_D0x Accelerometer
  415. driver
  416. This driver currently only supports I2C interface to the
  417. controller. Also select the I2C method.
  418. If unsure, say N
  419. To compile this driver as a module, choose M here: the
  420. module will be called cma3000_d0x.
  421. config INPUT_CMA3000_I2C
  422. tristate "Support I2C bus connection"
  423. depends on INPUT_CMA3000 && I2C
  424. help
  425. Say Y here if you want to use VTI CMA3000_D0x Accelerometer
  426. through I2C interface.
  427. To compile this driver as a module, choose M here: the
  428. module will be called cma3000_d0x_i2c.
  429. config INPUT_XEN_KBDDEV_FRONTEND
  430. tristate "Xen virtual keyboard and mouse support"
  431. depends on XEN_FBDEV_FRONTEND
  432. default y
  433. select XEN_XENBUS_FRONTEND
  434. help
  435. This driver implements the front-end of the Xen virtual
  436. keyboard and mouse device driver. It communicates with a back-end
  437. in another domain.
  438. To compile this driver as a module, choose M here: the
  439. module will be called xen-kbdfront.
  440. endif