Kconfig 17 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594
  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_MAX8997_HAPTIC
  108. tristate "MAXIM MAX8997 haptic controller support"
  109. depends on HAVE_PWM && MFD_MAX8997
  110. select INPUT_FF_MEMLESS
  111. help
  112. This option enables device driver support for the haptic controller
  113. on MAXIM MAX8997 chip. This driver supports ff-memless interface
  114. from input framework.
  115. To compile this driver as module, choose M here: the
  116. module will be called max8997-haptic.
  117. config INPUT_MC13783_PWRBUTTON
  118. tristate "MC13783 ON buttons"
  119. depends on MFD_MC13783
  120. help
  121. Support the ON buttons of MC13783 PMIC as an input device
  122. reporting power button status.
  123. To compile this driver as a module, choose M here: the module
  124. will be called mc13783-pwrbutton.
  125. config INPUT_MMA8450
  126. tristate "MMA8450 - Freescale's 3-Axis, 8/12-bit Digital Accelerometer"
  127. depends on I2C
  128. select INPUT_POLLDEV
  129. help
  130. Say Y here if you want to support Freescale's MMA8450 Accelerometer
  131. through I2C interface.
  132. To compile this driver as a module, choose M here: the
  133. module will be called mma8450.
  134. config INPUT_MPU3050
  135. tristate "MPU3050 Triaxial gyroscope sensor"
  136. depends on I2C
  137. help
  138. Say Y here if you want to support InvenSense MPU3050
  139. connected via an I2C bus.
  140. To compile this driver as a module, choose M here: the
  141. module will be called mpu3050.
  142. config INPUT_APANEL
  143. tristate "Fujitsu Lifebook Application Panel buttons"
  144. depends on X86 && I2C && LEDS_CLASS
  145. select INPUT_POLLDEV
  146. select CHECK_SIGNATURE
  147. help
  148. Say Y here for support of the Application Panel buttons, used on
  149. Fujitsu Lifebook. These are attached to the mainboard through
  150. an SMBus interface managed by the I2C Intel ICH (i801) driver,
  151. which you should also build for this kernel.
  152. To compile this driver as a module, choose M here: the module will
  153. be called apanel.
  154. config INPUT_GP2A
  155. tristate "Sharp GP2AP002A00F I2C Proximity/Opto sensor driver"
  156. depends on I2C
  157. depends on GENERIC_GPIO
  158. help
  159. Say Y here if you have a Sharp GP2AP002A00F proximity/als combo-chip
  160. hooked to an I2C bus.
  161. To compile this driver as a module, choose M here: the
  162. module will be called gp2ap002a00f.
  163. config INPUT_GPIO_TILT_POLLED
  164. tristate "Polled GPIO tilt switch"
  165. depends on GENERIC_GPIO
  166. select INPUT_POLLDEV
  167. help
  168. This driver implements support for tilt switches connected
  169. to GPIO pins that are not capable of generating interrupts.
  170. The list of gpios to use and the mapping of their states
  171. to specific angles is done via platform data.
  172. To compile this driver as a module, choose M here: the
  173. module will be called gpio_tilt_polled.
  174. config INPUT_IXP4XX_BEEPER
  175. tristate "IXP4XX Beeper support"
  176. depends on ARCH_IXP4XX
  177. help
  178. If you say yes here, you can connect a beeper to the
  179. ixp4xx gpio pins. This is used by the LinkSys NSLU2.
  180. If unsure, say Y.
  181. To compile this driver as a module, choose M here: the
  182. module will be called ixp4xx-beeper.
  183. config INPUT_COBALT_BTNS
  184. tristate "Cobalt button interface"
  185. depends on MIPS_COBALT
  186. select INPUT_POLLDEV
  187. help
  188. Say Y here if you want to support MIPS Cobalt button interface.
  189. To compile this driver as a module, choose M here: the
  190. module will be called cobalt_btns.
  191. config INPUT_WISTRON_BTNS
  192. tristate "x86 Wistron laptop button interface"
  193. depends on X86 && !X86_64
  194. select INPUT_POLLDEV
  195. select INPUT_SPARSEKMAP
  196. select NEW_LEDS
  197. select LEDS_CLASS
  198. select CHECK_SIGNATURE
  199. help
  200. Say Y here for support of Wistron laptop button interfaces, used on
  201. laptops of various brands, including Acer and Fujitsu-Siemens. If
  202. available, mail and wifi LEDs will be controllable via /sys/class/leds.
  203. To compile this driver as a module, choose M here: the module will
  204. be called wistron_btns.
  205. config INPUT_ATLAS_BTNS
  206. tristate "x86 Atlas button interface"
  207. depends on X86 && ACPI
  208. help
  209. Say Y here for support of Atlas wallmount touchscreen buttons.
  210. The events will show up as scancodes F1 through F9 via evdev.
  211. To compile this driver as a module, choose M here: the module will
  212. be called atlas_btns.
  213. config INPUT_ATI_REMOTE2
  214. tristate "ATI / Philips USB RF remote control"
  215. depends on USB_ARCH_HAS_HCD
  216. select USB
  217. help
  218. Say Y here if you want to use an ATI or Philips USB RF remote control.
  219. These are RF remotes with USB receivers.
  220. ATI Remote Wonder II comes with some ATI's All-In-Wonder video cards
  221. and is also available as a separate product.
  222. This driver provides mouse pointer, left and right mouse buttons,
  223. and maps all the other remote buttons to keypress events.
  224. To compile this driver as a module, choose M here: the module will be
  225. called ati_remote2.
  226. config INPUT_KEYSPAN_REMOTE
  227. tristate "Keyspan DMR USB remote control (EXPERIMENTAL)"
  228. depends on EXPERIMENTAL
  229. depends on USB_ARCH_HAS_HCD
  230. select USB
  231. help
  232. Say Y here if you want to use a Keyspan DMR USB remote control.
  233. Currently only the UIA-11 type of receiver has been tested. The tag
  234. on the receiver that connects to the USB port should have a P/N that
  235. will tell you what type of DMR you have. The UIA-10 type is not
  236. supported at this time. This driver maps all buttons to keypress
  237. events.
  238. To compile this driver as a module, choose M here: the module will
  239. be called keyspan_remote.
  240. config INPUT_KXTJ9
  241. tristate "Kionix KXTJ9 tri-axis digital accelerometer"
  242. depends on I2C
  243. help
  244. Say Y here to enable support for the Kionix KXTJ9 digital tri-axis
  245. accelerometer.
  246. To compile this driver as a module, choose M here: the module will
  247. be called kxtj9.
  248. config INPUT_KXTJ9_POLLED_MODE
  249. bool "Enable polling mode support"
  250. depends on INPUT_KXTJ9
  251. select INPUT_POLLDEV
  252. help
  253. Say Y here if you need accelerometer to work in polling mode.
  254. config INPUT_POWERMATE
  255. tristate "Griffin PowerMate and Contour Jog support"
  256. depends on USB_ARCH_HAS_HCD
  257. select USB
  258. help
  259. Say Y here if you want to use Griffin PowerMate or Contour Jog devices.
  260. These are aluminum dials which can measure clockwise and anticlockwise
  261. rotation. The dial also acts as a pushbutton. The base contains an LED
  262. which can be instructed to pulse or to switch to a particular intensity.
  263. You can download userspace tools from
  264. <http://sowerbutts.com/powermate/>.
  265. To compile this driver as a module, choose M here: the
  266. module will be called powermate.
  267. config INPUT_YEALINK
  268. tristate "Yealink usb-p1k voip phone"
  269. depends on EXPERIMENTAL
  270. depends on USB_ARCH_HAS_HCD
  271. select USB
  272. help
  273. Say Y here if you want to enable keyboard and LCD functions of the
  274. Yealink usb-p1k usb phones. The audio part is enabled by the generic
  275. usb sound driver, so you might want to enable that as well.
  276. For information about how to use these additional functions, see
  277. <file:Documentation/input/yealink.txt>.
  278. To compile this driver as a module, choose M here: the module will be
  279. called yealink.
  280. config INPUT_CM109
  281. tristate "C-Media CM109 USB I/O Controller"
  282. depends on EXPERIMENTAL
  283. depends on USB_ARCH_HAS_HCD
  284. select USB
  285. help
  286. Say Y here if you want to enable keyboard and buzzer functions of the
  287. C-Media CM109 usb phones. The audio part is enabled by the generic
  288. usb sound driver, so you might want to enable that as well.
  289. To compile this driver as a module, choose M here: the module will be
  290. called cm109.
  291. config INPUT_TWL4030_PWRBUTTON
  292. tristate "TWL4030 Power button Driver"
  293. depends on TWL4030_CORE
  294. help
  295. Say Y here if you want to enable power key reporting via the
  296. TWL4030 family of chips.
  297. To compile this driver as a module, choose M here. The module will
  298. be called twl4030_pwrbutton.
  299. config INPUT_TWL4030_VIBRA
  300. tristate "Support for TWL4030 Vibrator"
  301. depends on TWL4030_CORE
  302. select MFD_TWL4030_AUDIO
  303. select INPUT_FF_MEMLESS
  304. help
  305. This option enables support for TWL4030 Vibrator Driver.
  306. To compile this driver as a module, choose M here. The module will
  307. be called twl4030_vibra.
  308. config INPUT_TWL6040_VIBRA
  309. tristate "Support for TWL6040 Vibrator"
  310. depends on TWL4030_CORE
  311. select TWL6040_CORE
  312. select INPUT_FF_MEMLESS
  313. help
  314. This option enables support for TWL6040 Vibrator Driver.
  315. To compile this driver as a module, choose M here. The module will
  316. be called twl6040_vibra.
  317. config INPUT_UINPUT
  318. tristate "User level driver support"
  319. help
  320. Say Y here if you want to support user level drivers for input
  321. subsystem accessible under char device 10:223 - /dev/input/uinput.
  322. To compile this driver as a module, choose M here: the
  323. module will be called uinput.
  324. config INPUT_SGI_BTNS
  325. tristate "SGI Indy/O2 volume button interface"
  326. depends on SGI_IP22 || SGI_IP32
  327. select INPUT_POLLDEV
  328. help
  329. Say Y here if you want to support SGI Indy/O2 volume button interface.
  330. To compile this driver as a module, choose M here: the
  331. module will be called sgi_btns.
  332. config HP_SDC_RTC
  333. tristate "HP SDC Real Time Clock"
  334. depends on (GSC || HP300) && SERIO
  335. select HP_SDC
  336. help
  337. Say Y here if you want to support the built-in real time clock
  338. of the HP SDC controller.
  339. config INPUT_PCF50633_PMU
  340. tristate "PCF50633 PMU events"
  341. depends on MFD_PCF50633
  342. help
  343. Say Y to include support for delivering PMU events via input
  344. layer on NXP PCF50633.
  345. config INPUT_PCF8574
  346. tristate "PCF8574 Keypad input device"
  347. depends on I2C && EXPERIMENTAL
  348. help
  349. Say Y here if you want to support a keypad connected via I2C
  350. with a PCF8574.
  351. To compile this driver as a module, choose M here: the
  352. module will be called pcf8574_keypad.
  353. config INPUT_PWM_BEEPER
  354. tristate "PWM beeper support"
  355. depends on HAVE_PWM
  356. help
  357. Say Y here to get support for PWM based beeper devices.
  358. If unsure, say N.
  359. To compile this driver as a module, choose M here: the module will be
  360. called pwm-beeper.
  361. config INPUT_GPIO_ROTARY_ENCODER
  362. tristate "Rotary encoders connected to GPIO pins"
  363. depends on GPIOLIB && GENERIC_GPIO
  364. help
  365. Say Y here to add support for rotary encoders connected to GPIO lines.
  366. Check file:Documentation/input/rotary-encoder.txt for more
  367. information.
  368. To compile this driver as a module, choose M here: the
  369. module will be called rotary_encoder.
  370. config INPUT_RB532_BUTTON
  371. tristate "Mikrotik Routerboard 532 button interface"
  372. depends on MIKROTIK_RB532
  373. depends on GPIOLIB && GENERIC_GPIO
  374. select INPUT_POLLDEV
  375. help
  376. Say Y here if you want support for the S1 button built into
  377. Mikrotik's Routerboard 532.
  378. To compile this driver as a module, choose M here: the
  379. module will be called rb532_button.
  380. config INPUT_DA9052_ONKEY
  381. tristate "Dialog DA9052/DA9053 Onkey"
  382. depends on PMIC_DA9052
  383. help
  384. Support the ONKEY of Dialog DA9052 PMICs as an input device
  385. reporting power button status.
  386. To compile this driver as a module, choose M here: the
  387. module will be called da9052_onkey.
  388. config INPUT_DM355EVM
  389. tristate "TI DaVinci DM355 EVM Keypad and IR Remote"
  390. depends on MFD_DM355EVM_MSP
  391. select INPUT_SPARSEKMAP
  392. help
  393. Supports the pushbuttons and IR remote used with
  394. the DM355 EVM board.
  395. To compile this driver as a module, choose M here: the
  396. module will be called dm355evm_keys.
  397. config INPUT_BFIN_ROTARY
  398. tristate "Blackfin Rotary support"
  399. depends on BF54x || BF52x
  400. help
  401. Say Y here if you want to use the Blackfin Rotary.
  402. To compile this driver as a module, choose M here: the
  403. module will be called bfin-rotary.
  404. config INPUT_WM831X_ON
  405. tristate "WM831X ON pin"
  406. depends on MFD_WM831X
  407. help
  408. Support the ON pin of WM831X PMICs as an input device
  409. reporting power button status.
  410. To compile this driver as a module, choose M here: the module
  411. will be called wm831x_on.
  412. config INPUT_PCAP
  413. tristate "Motorola EZX PCAP misc input events"
  414. depends on EZX_PCAP
  415. help
  416. Say Y here if you want to use Power key and Headphone button
  417. on Motorola EZX phones.
  418. To compile this driver as a module, choose M here: the
  419. module will be called pcap_keys.
  420. config INPUT_ADXL34X
  421. tristate "Analog Devices ADXL34x Three-Axis Digital Accelerometer"
  422. default n
  423. help
  424. Say Y here if you have a Accelerometer interface using the
  425. ADXL345/6 controller, and your board-specific initialization
  426. code includes that in its table of devices.
  427. This driver can use either I2C or SPI communication to the
  428. ADXL345/6 controller. Select the appropriate method for
  429. your system.
  430. If unsure, say N (but it's safe to say "Y").
  431. To compile this driver as a module, choose M here: the
  432. module will be called adxl34x.
  433. config INPUT_ADXL34X_I2C
  434. tristate "support I2C bus connection"
  435. depends on INPUT_ADXL34X && I2C
  436. default y
  437. help
  438. Say Y here if you have ADXL345/6 hooked to an I2C bus.
  439. To compile this driver as a module, choose M here: the
  440. module will be called adxl34x-i2c.
  441. config INPUT_ADXL34X_SPI
  442. tristate "support SPI bus connection"
  443. depends on INPUT_ADXL34X && SPI
  444. default y
  445. help
  446. Say Y here if you have ADXL345/6 hooked to a SPI bus.
  447. To compile this driver as a module, choose M here: the
  448. module will be called adxl34x-spi.
  449. config INPUT_CMA3000
  450. tristate "VTI CMA3000 Tri-axis accelerometer"
  451. help
  452. Say Y here if you want to use VTI CMA3000_D0x Accelerometer
  453. driver
  454. This driver currently only supports I2C interface to the
  455. controller. Also select the I2C method.
  456. If unsure, say N
  457. To compile this driver as a module, choose M here: the
  458. module will be called cma3000_d0x.
  459. config INPUT_CMA3000_I2C
  460. tristate "Support I2C bus connection"
  461. depends on INPUT_CMA3000 && I2C
  462. help
  463. Say Y here if you want to use VTI CMA3000_D0x Accelerometer
  464. through I2C interface.
  465. To compile this driver as a module, choose M here: the
  466. module will be called cma3000_d0x_i2c.
  467. config INPUT_XEN_KBDDEV_FRONTEND
  468. tristate "Xen virtual keyboard and mouse support"
  469. depends on XEN
  470. default y
  471. select XEN_XENBUS_FRONTEND
  472. help
  473. This driver implements the front-end of the Xen virtual
  474. keyboard and mouse device driver. It communicates with a back-end
  475. in another domain.
  476. To compile this driver as a module, choose M here: the
  477. module will be called xen-kbdfront.
  478. endif