Kconfig 10 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343
  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_PCSPKR
  21. tristate "PC Speaker support"
  22. depends on PCSPKR_PLATFORM
  23. help
  24. Say Y here if you want the standard PC Speaker to be used for
  25. bells and whistles.
  26. If unsure, say Y.
  27. To compile this driver as a module, choose M here: the
  28. module will be called pcspkr.
  29. config INPUT_SPARCSPKR
  30. tristate "SPARC Speaker support"
  31. depends on PCI && SPARC64
  32. help
  33. Say Y here if you want the standard Speaker on Sparc PCI systems
  34. to be used for bells and whistles.
  35. If unsure, say Y.
  36. To compile this driver as a module, choose M here: the
  37. module will be called sparcspkr.
  38. config INPUT_M68K_BEEP
  39. tristate "M68k Beeper support"
  40. depends on M68K
  41. config INPUT_APANEL
  42. tristate "Fujitsu Lifebook Application Panel buttons"
  43. depends on X86 && I2C && LEDS_CLASS
  44. select INPUT_POLLDEV
  45. select CHECK_SIGNATURE
  46. help
  47. Say Y here for support of the Application Panel buttons, used on
  48. Fujitsu Lifebook. These are attached to the mainboard through
  49. an SMBus interface managed by the I2C Intel ICH (i801) driver,
  50. which you should also build for this kernel.
  51. To compile this driver as a module, choose M here: the module will
  52. be called apanel.
  53. config INPUT_IXP4XX_BEEPER
  54. tristate "IXP4XX Beeper support"
  55. depends on ARCH_IXP4XX
  56. help
  57. If you say yes here, you can connect a beeper to the
  58. ixp4xx gpio pins. This is used by the LinkSys NSLU2.
  59. If unsure, say Y.
  60. To compile this driver as a module, choose M here: the
  61. module will be called ixp4xx-beeper.
  62. config INPUT_COBALT_BTNS
  63. tristate "Cobalt button interface"
  64. depends on MIPS_COBALT
  65. select INPUT_POLLDEV
  66. help
  67. Say Y here if you want to support MIPS Cobalt button interface.
  68. To compile this driver as a module, choose M here: the
  69. module will be called cobalt_btns.
  70. config INPUT_WISTRON_BTNS
  71. tristate "x86 Wistron laptop button interface"
  72. depends on X86 && !X86_64
  73. select INPUT_POLLDEV
  74. select INPUT_SPARSEKMAP
  75. select NEW_LEDS
  76. select LEDS_CLASS
  77. select CHECK_SIGNATURE
  78. help
  79. Say Y here for support of Wistron laptop button interfaces, used on
  80. laptops of various brands, including Acer and Fujitsu-Siemens. If
  81. available, mail and wifi LEDs will be controllable via /sys/class/leds.
  82. To compile this driver as a module, choose M here: the module will
  83. be called wistron_btns.
  84. config INPUT_ATLAS_BTNS
  85. tristate "x86 Atlas button interface"
  86. depends on X86 && ACPI
  87. help
  88. Say Y here for support of Atlas wallmount touchscreen buttons.
  89. The events will show up as scancodes F1 through F9 via evdev.
  90. To compile this driver as a module, choose M here: the module will
  91. be called atlas_btns.
  92. config INPUT_ATI_REMOTE
  93. tristate "ATI / X10 USB RF remote control"
  94. depends on USB_ARCH_HAS_HCD
  95. select USB
  96. help
  97. Say Y here if you want to use an ATI or X10 "Lola" USB remote control.
  98. These are RF remotes with USB receivers.
  99. The ATI remote comes with many of ATI's All-In-Wonder video cards.
  100. The X10 "Lola" remote is available at:
  101. <http://www.x10.com/products/lola_sg1.htm>
  102. This driver provides mouse pointer, left and right mouse buttons,
  103. and maps all the other remote buttons to keypress events.
  104. To compile this driver as a module, choose M here: the module will be
  105. called ati_remote.
  106. config INPUT_ATI_REMOTE2
  107. tristate "ATI / Philips USB RF remote control"
  108. depends on USB_ARCH_HAS_HCD
  109. select USB
  110. help
  111. Say Y here if you want to use an ATI or Philips USB RF remote control.
  112. These are RF remotes with USB receivers.
  113. ATI Remote Wonder II comes with some ATI's All-In-Wonder video cards
  114. and is also available as a separate product.
  115. This driver provides mouse pointer, left and right mouse buttons,
  116. and maps all the other remote buttons to keypress events.
  117. To compile this driver as a module, choose M here: the module will be
  118. called ati_remote2.
  119. config INPUT_KEYSPAN_REMOTE
  120. tristate "Keyspan DMR USB remote control (EXPERIMENTAL)"
  121. depends on EXPERIMENTAL
  122. depends on USB_ARCH_HAS_HCD
  123. select USB
  124. help
  125. Say Y here if you want to use a Keyspan DMR USB remote control.
  126. Currently only the UIA-11 type of receiver has been tested. The tag
  127. on the receiver that connects to the USB port should have a P/N that
  128. will tell you what type of DMR you have. The UIA-10 type is not
  129. supported at this time. This driver maps all buttons to keypress
  130. events.
  131. To compile this driver as a module, choose M here: the module will
  132. be called keyspan_remote.
  133. config INPUT_POWERMATE
  134. tristate "Griffin PowerMate and Contour Jog support"
  135. depends on USB_ARCH_HAS_HCD
  136. select USB
  137. help
  138. Say Y here if you want to use Griffin PowerMate or Contour Jog devices.
  139. These are aluminum dials which can measure clockwise and anticlockwise
  140. rotation. The dial also acts as a pushbutton. The base contains an LED
  141. which can be instructed to pulse or to switch to a particular intensity.
  142. You can download userspace tools from
  143. <http://sowerbutts.com/powermate/>.
  144. To compile this driver as a module, choose M here: the
  145. module will be called powermate.
  146. config INPUT_YEALINK
  147. tristate "Yealink usb-p1k voip phone"
  148. depends on EXPERIMENTAL
  149. depends on USB_ARCH_HAS_HCD
  150. select USB
  151. help
  152. Say Y here if you want to enable keyboard and LCD functions of the
  153. Yealink usb-p1k usb phones. The audio part is enabled by the generic
  154. usb sound driver, so you might want to enable that as well.
  155. For information about how to use these additional functions, see
  156. <file:Documentation/input/yealink.txt>.
  157. To compile this driver as a module, choose M here: the module will be
  158. called yealink.
  159. config INPUT_CM109
  160. tristate "C-Media CM109 USB I/O Controller"
  161. depends on EXPERIMENTAL
  162. depends on USB_ARCH_HAS_HCD
  163. select USB
  164. help
  165. Say Y here if you want to enable keyboard and buzzer functions of the
  166. C-Media CM109 usb phones. The audio part is enabled by the generic
  167. usb sound driver, so you might want to enable that as well.
  168. To compile this driver as a module, choose M here: the module will be
  169. called cm109.
  170. config INPUT_TWL4030_PWRBUTTON
  171. tristate "TWL4030 Power button Driver"
  172. depends on TWL4030_CORE
  173. help
  174. Say Y here if you want to enable power key reporting via the
  175. TWL4030 family of chips.
  176. To compile this driver as a module, choose M here. The module will
  177. be called twl4030_pwrbutton.
  178. config INPUT_TWL4030_VIBRA
  179. tristate "Support for TWL4030 Vibrator"
  180. depends on TWL4030_CORE
  181. select TWL4030_CODEC
  182. select INPUT_FF_MEMLESS
  183. help
  184. This option enables support for TWL4030 Vibrator Driver.
  185. To compile this driver as a module, choose M here. The module will
  186. be called twl4030_vibra.
  187. config INPUT_UINPUT
  188. tristate "User level driver support"
  189. help
  190. Say Y here if you want to support user level drivers for input
  191. subsystem accessible under char device 10:223 - /dev/input/uinput.
  192. To compile this driver as a module, choose M here: the
  193. module will be called uinput.
  194. config INPUT_SGI_BTNS
  195. tristate "SGI Indy/O2 volume button interface"
  196. depends on SGI_IP22 || SGI_IP32
  197. select INPUT_POLLDEV
  198. help
  199. Say Y here if you want to support SGI Indy/O2 volume button interface.
  200. To compile this driver as a module, choose M here: the
  201. module will be called sgi_btns.
  202. config INPUT_WINBOND_CIR
  203. tristate "Winbond IR remote control"
  204. depends on X86 && PNP
  205. select NEW_LEDS
  206. select LEDS_CLASS
  207. select LEDS_TRIGGERS
  208. select BITREVERSE
  209. help
  210. Say Y here if you want to use the IR remote functionality found
  211. in some Winbond SuperI/O chips. Currently only the WPCD376I
  212. chip is supported (included in some Intel Media series motherboards).
  213. IR Receive and wake-on-IR from suspend and power-off is currently
  214. supported.
  215. To compile this driver as a module, choose M here: the module will be
  216. called winbond_cir.
  217. config HP_SDC_RTC
  218. tristate "HP SDC Real Time Clock"
  219. depends on (GSC || HP300) && SERIO
  220. select HP_SDC
  221. help
  222. Say Y here if you want to support the built-in real time clock
  223. of the HP SDC controller.
  224. config INPUT_PCF50633_PMU
  225. tristate "PCF50633 PMU events"
  226. depends on MFD_PCF50633
  227. help
  228. Say Y to include support for delivering PMU events via input
  229. layer on NXP PCF50633.
  230. config INPUT_GPIO_ROTARY_ENCODER
  231. tristate "Rotary encoders connected to GPIO pins"
  232. depends on GPIOLIB && GENERIC_GPIO
  233. help
  234. Say Y here to add support for rotary encoders connected to GPIO lines.
  235. Check file:Documentation/input/rotary-encoder.txt for more
  236. information.
  237. To compile this driver as a module, choose M here: the
  238. module will be called rotary_encoder.
  239. config INPUT_RB532_BUTTON
  240. tristate "Mikrotik Routerboard 532 button interface"
  241. depends on MIKROTIK_RB532
  242. depends on GPIOLIB && GENERIC_GPIO
  243. select INPUT_POLLDEV
  244. help
  245. Say Y here if you want support for the S1 button built into
  246. Mikrotik's Routerboard 532.
  247. To compile this driver as a module, choose M here: the
  248. module will be called rb532_button.
  249. config INPUT_DM355EVM
  250. tristate "TI DaVinci DM355 EVM Keypad and IR Remote"
  251. depends on MFD_DM355EVM_MSP
  252. select INPUT_SPARSEKMAP
  253. help
  254. Supports the pushbuttons and IR remote used with
  255. the DM355 EVM board.
  256. To compile this driver as a module, choose M here: the
  257. module will be called dm355evm_keys.
  258. config INPUT_BFIN_ROTARY
  259. tristate "Blackfin Rotary support"
  260. depends on BF54x || BF52x
  261. help
  262. Say Y here if you want to use the Blackfin Rotary.
  263. To compile this driver as a module, choose M here: the
  264. module will be called bfin-rotary.
  265. config INPUT_WM831X_ON
  266. tristate "WM831X ON pin"
  267. depends on MFD_WM831X
  268. help
  269. Support the ON pin of WM831X PMICs as an input device
  270. reporting power button status.
  271. To compile this driver as a module, choose M here: the module
  272. will be called wm831x_on.
  273. config INPUT_PCAP
  274. tristate "Motorola EZX PCAP misc input events"
  275. depends on EZX_PCAP
  276. help
  277. Say Y here if you want to use Power key and Headphone button
  278. on Motorola EZX phones.
  279. To compile this driver as a module, choose M here: the
  280. module will be called pcap_keys.
  281. endif