Kconfig 6.5 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210
  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_PCSPKR
  13. tristate "PC Speaker support"
  14. depends on PCSPKR_PLATFORM
  15. help
  16. Say Y here if you want the standard PC Speaker to be used for
  17. bells and whistles.
  18. If unsure, say Y.
  19. To compile this driver as a module, choose M here: the
  20. module will be called pcspkr.
  21. config INPUT_SPARCSPKR
  22. tristate "SPARC Speaker support"
  23. depends on PCI && SPARC64
  24. help
  25. Say Y here if you want the standard Speaker on Sparc PCI systems
  26. to be used for bells and whistles.
  27. If unsure, say Y.
  28. To compile this driver as a module, choose M here: the
  29. module will be called sparcspkr.
  30. config INPUT_M68K_BEEP
  31. tristate "M68k Beeper support"
  32. depends on M68K
  33. config INPUT_APANEL
  34. tristate "Fujitsu Lifebook Application Panel buttons"
  35. depends on X86 && I2C && LEDS_CLASS
  36. select INPUT_POLLDEV
  37. select CHECK_SIGNATURE
  38. help
  39. Say Y here for support of the Application Panel buttons, used on
  40. Fujitsu Lifebook. These are attached to the mainboard through
  41. an SMBus interface managed by the I2C Intel ICH (i801) driver,
  42. which you should also build for this kernel.
  43. To compile this driver as a module, choose M here: the module will
  44. be called apanel.
  45. config INPUT_IXP4XX_BEEPER
  46. tristate "IXP4XX Beeper support"
  47. depends on ARCH_IXP4XX
  48. help
  49. If you say yes here, you can connect a beeper to the
  50. ixp4xx gpio pins. This is used by the LinkSys NSLU2.
  51. If unsure, say Y.
  52. To compile this driver as a module, choose M here: the
  53. module will be called ixp4xx-beeper.
  54. config INPUT_COBALT_BTNS
  55. tristate "Cobalt button interface"
  56. depends on MIPS_COBALT
  57. select INPUT_POLLDEV
  58. help
  59. Say Y here if you want to support MIPS Cobalt button interface.
  60. To compile this driver as a module, choose M here: the
  61. module will be called cobalt_btns.
  62. config INPUT_WISTRON_BTNS
  63. tristate "x86 Wistron laptop button interface"
  64. depends on X86 && !X86_64
  65. select INPUT_POLLDEV
  66. select NEW_LEDS
  67. select LEDS_CLASS
  68. select CHECK_SIGNATURE
  69. help
  70. Say Y here for support of Wistron laptop button interfaces, used on
  71. laptops of various brands, including Acer and Fujitsu-Siemens. If
  72. available, mail and wifi LEDs will be controllable via /sys/class/leds.
  73. To compile this driver as a module, choose M here: the module will
  74. be called wistron_btns.
  75. config INPUT_ATLAS_BTNS
  76. tristate "x86 Atlas button interface"
  77. depends on X86 && ACPI
  78. help
  79. Say Y here for support of Atlas wallmount touchscreen buttons.
  80. The events will show up as scancodes F1 through F9 via evdev.
  81. To compile this driver as a module, choose M here: the module will
  82. be called atlas_btns.
  83. config INPUT_ATI_REMOTE
  84. tristate "ATI / X10 USB RF remote control"
  85. depends on USB_ARCH_HAS_HCD
  86. select USB
  87. help
  88. Say Y here if you want to use an ATI or X10 "Lola" USB remote control.
  89. These are RF remotes with USB receivers.
  90. The ATI remote comes with many of ATI's All-In-Wonder video cards.
  91. The X10 "Lola" remote is available at:
  92. <http://www.x10.com/products/lola_sg1.htm>
  93. This driver provides mouse pointer, left and right mouse buttons,
  94. and maps all the other remote buttons to keypress events.
  95. To compile this driver as a module, choose M here: the module will be
  96. called ati_remote.
  97. config INPUT_ATI_REMOTE2
  98. tristate "ATI / Philips USB RF remote control"
  99. depends on USB_ARCH_HAS_HCD
  100. select USB
  101. help
  102. Say Y here if you want to use an ATI or Philips USB RF remote control.
  103. These are RF remotes with USB receivers.
  104. ATI Remote Wonder II comes with some ATI's All-In-Wonder video cards
  105. and is also available as a separate product.
  106. This driver provides mouse pointer, left and right mouse buttons,
  107. and maps all the other remote buttons to keypress events.
  108. To compile this driver as a module, choose M here: the module will be
  109. called ati_remote2.
  110. config INPUT_KEYSPAN_REMOTE
  111. tristate "Keyspan DMR USB remote control (EXPERIMENTAL)"
  112. depends on EXPERIMENTAL
  113. depends on USB_ARCH_HAS_HCD
  114. select USB
  115. help
  116. Say Y here if you want to use a Keyspan DMR USB remote control.
  117. Currently only the UIA-11 type of receiver has been tested. The tag
  118. on the receiver that connects to the USB port should have a P/N that
  119. will tell you what type of DMR you have. The UIA-10 type is not
  120. supported at this time. This driver maps all buttons to keypress
  121. events.
  122. To compile this driver as a module, choose M here: the module will
  123. be called keyspan_remote.
  124. config INPUT_POWERMATE
  125. tristate "Griffin PowerMate and Contour Jog support"
  126. depends on USB_ARCH_HAS_HCD
  127. select USB
  128. help
  129. Say Y here if you want to use Griffin PowerMate or Contour Jog devices.
  130. These are aluminum dials which can measure clockwise and anticlockwise
  131. rotation. The dial also acts as a pushbutton. The base contains an LED
  132. which can be instructed to pulse or to switch to a particular intensity.
  133. You can download userspace tools from
  134. <http://sowerbutts.com/powermate/>.
  135. To compile this driver as a module, choose M here: the
  136. module will be called powermate.
  137. config INPUT_YEALINK
  138. tristate "Yealink usb-p1k voip phone"
  139. depends on EXPERIMENTAL
  140. depends on USB_ARCH_HAS_HCD
  141. select USB
  142. help
  143. Say Y here if you want to enable keyboard and LCD functions of the
  144. Yealink usb-p1k usb phones. The audio part is enabled by the generic
  145. usb sound driver, so you might want to enable that as well.
  146. For information about how to use these additional functions, see
  147. <file:Documentation/input/yealink.txt>.
  148. To compile this driver as a module, choose M here: the module will be
  149. called yealink.
  150. config INPUT_UINPUT
  151. tristate "User level driver support"
  152. help
  153. Say Y here if you want to support user level drivers for input
  154. subsystem accessible under char device 10:223 - /dev/input/uinput.
  155. To compile this driver as a module, choose M here: the
  156. module will be called uinput.
  157. config INPUT_SGI_BTNS
  158. tristate "SGI Indy/O2 volume button interface"
  159. depends on SGI_IP22 || SGI_IP32
  160. select INPUT_POLLDEV
  161. help
  162. Say Y here if you want to support SGI Indy/O2 volume button interface.
  163. To compile this driver as a module, choose M here: the
  164. module will be called sgi_btns.
  165. config HP_SDC_RTC
  166. tristate "HP SDC Real Time Clock"
  167. depends on GSC || HP300
  168. select HP_SDC
  169. help
  170. Say Y here if you want to support the built-in real time clock
  171. of the HP SDC controller.
  172. endif