Kconfig 10 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306
  1. #
  2. # USB Miscellaneous driver configuration
  3. #
  4. comment "USB Miscellaneous drivers"
  5. depends on USB
  6. config USB_EMI62
  7. tristate "EMI 6|2m USB Audio interface support"
  8. depends on USB
  9. ---help---
  10. This driver loads firmware to Emagic EMI 6|2m low latency USB
  11. Audio and Midi interface.
  12. After firmware load the device is handled with standard linux
  13. USB Audio driver.
  14. This code is also available as a module ( = code which can be
  15. inserted in and removed from the running kernel whenever you want).
  16. The module will be called audio. If you want to compile it as a
  17. module, say M here and read <file:Documentation/kbuild/modules.txt>.
  18. config USB_EMI26
  19. tristate "EMI 2|6 USB Audio interface support"
  20. depends on USB
  21. ---help---
  22. This driver loads firmware to Emagic EMI 2|6 low latency USB
  23. Audio interface.
  24. After firmware load the device is handled with standard linux
  25. USB Audio driver.
  26. To compile this driver as a module, choose M here: the
  27. module will be called emi26.
  28. config USB_ADUTUX
  29. tristate "ADU devices from Ontrak Control Systems"
  30. depends on USB
  31. help
  32. Say Y if you want to use an ADU device from Ontrak Control
  33. Systems.
  34. To compile this driver as a module, choose M here. The module
  35. will be called adutux.
  36. config USB_SEVSEG
  37. tristate "USB 7-Segment LED Display"
  38. depends on USB
  39. help
  40. Say Y here if you have a USB 7-Segment Display by Delcom
  41. To compile this driver as a module, choose M here: the
  42. module will be called usbsevseg.
  43. config USB_RIO500
  44. tristate "USB Diamond Rio500 support"
  45. depends on USB
  46. help
  47. Say Y here if you want to connect a USB Rio500 mp3 player to your
  48. computer's USB port. Please read <file:Documentation/usb/rio.txt>
  49. for more information.
  50. To compile this driver as a module, choose M here: the
  51. module will be called rio500.
  52. config USB_LEGOTOWER
  53. tristate "USB Lego Infrared Tower support"
  54. depends on USB
  55. help
  56. Say Y here if you want to connect a USB Lego Infrared Tower to your
  57. computer's USB port.
  58. This code is also available as a module ( = code which can be
  59. inserted in and removed from the running kernel whenever you want).
  60. The module will be called legousbtower. If you want to compile it as
  61. a module, say M here and read
  62. <file:Documentation/kbuild/modules.txt>.
  63. config USB_LCD
  64. tristate "USB LCD driver support"
  65. depends on USB
  66. help
  67. Say Y here if you want to connect an USBLCD to your computer's
  68. USB port. The USBLCD is a small USB interface board for
  69. alphanumeric LCD modules. See <http://www.usblcd.de/> for more
  70. information.
  71. To compile this driver as a module, choose M here: the
  72. module will be called usblcd.
  73. config USB_LED
  74. tristate "USB LED driver support"
  75. depends on USB
  76. help
  77. Say Y here if you want to connect an USBLED device to your
  78. computer's USB port.
  79. To compile this driver as a module, choose M here: the
  80. module will be called usbled.
  81. config USB_CYPRESS_CY7C63
  82. tristate "Cypress CY7C63xxx USB driver support"
  83. depends on USB
  84. help
  85. Say Y here if you want to connect a Cypress CY7C63xxx
  86. micro controller to your computer's USB port. Currently this
  87. driver supports the pre-programmed devices (incl. firmware)
  88. by AK Modul-Bus Computer GmbH.
  89. Please see: http://www.ak-modul-bus.de/stat/mikrocontroller.html
  90. To compile this driver as a module, choose M here: the
  91. module will be called cypress_cy7c63.
  92. config USB_CYTHERM
  93. tristate "Cypress USB thermometer driver support"
  94. depends on USB
  95. help
  96. Say Y here if you want to connect a Cypress USB thermometer
  97. device to your computer's USB port. This device is also known
  98. as the Cypress USB Starter kit or demo board. The Elektor
  99. magazine published a modified version of this device in issue
  100. #291.
  101. To compile this driver as a module, choose M here: the
  102. module will be called cytherm.
  103. config USB_IDMOUSE
  104. tristate "Siemens ID USB Mouse Fingerprint sensor support"
  105. depends on USB
  106. help
  107. Say Y here if you want to use the fingerprint sensor on
  108. the Siemens ID Mouse. There is also a Siemens ID Mouse
  109. _Professional_, which has not been tested with this driver,
  110. but uses the same sensor and may therefore work.
  111. This driver creates an entry "/dev/idmouseX" or "/dev/usb/idmouseX",
  112. which can be used by, e.g.,"cat /dev/idmouse0 > fingerprint.pnm".
  113. See also <http://www.fs.tum.de/~echtler/idmouse/>.
  114. config USB_FTDI_ELAN
  115. tristate "Elan PCMCIA CardBus Adapter USB Client"
  116. depends on USB
  117. default M
  118. help
  119. ELAN's Uxxx series of adapters are USB to PCMCIA CardBus adapters.
  120. Currently only the U132 adapter is available.
  121. The U132 is specifically designed for CardBus PC cards that contain
  122. an OHCI host controller. Typical PC cards are the Orange Mobile 3G
  123. Option GlobeTrotter Fusion card. The U132 adapter will *NOT* work
  124. with PC cards that do not contain an OHCI controller. To use a U132
  125. adapter you will need this "ftdi-elan" module as well as the "u132-hcd"
  126. module which is a USB host controller driver that talks to the OHCI
  127. controller within CardBus card that are inserted in the U132 adapter.
  128. This driver has been tested with a CardBus OHCI USB adapter, and
  129. worked with a USB PEN Drive inserted into the first USB port of
  130. the PCCARD. A rather pointless thing to do, but useful for testing.
  131. See also the USB_U132_HCD entry "Elan U132 Adapter Host Controller"
  132. It is safe to say M here.
  133. config USB_APPLEDISPLAY
  134. tristate "Apple Cinema Display support"
  135. depends on USB
  136. select BACKLIGHT_LCD_SUPPORT
  137. select BACKLIGHT_CLASS_DEVICE
  138. help
  139. Say Y here if you want to control the backlight of Apple Cinema
  140. Displays over USB. This driver provides a sysfs interface.
  141. source "drivers/usb/misc/sisusbvga/Kconfig"
  142. config USB_LD
  143. tristate "USB LD driver"
  144. depends on USB
  145. help
  146. This driver is for generic USB devices that use interrupt transfers,
  147. like LD Didactic's USB devices.
  148. To compile this driver as a module, choose M here: the
  149. module will be called ldusb.
  150. config USB_TRANCEVIBRATOR
  151. tristate "PlayStation 2 Trance Vibrator driver support"
  152. depends on USB
  153. help
  154. Say Y here if you want to connect a PlayStation 2 Trance Vibrator
  155. device to your computer's USB port.
  156. To compile this driver as a module, choose M here: the
  157. module will be called trancevibrator.
  158. config USB_IOWARRIOR
  159. tristate "IO Warrior driver support"
  160. depends on USB
  161. help
  162. Say Y here if you want to support the IO Warrior devices from Code
  163. Mercenaries. This includes support for the following devices:
  164. IO Warrior 40
  165. IO Warrior 24
  166. IO Warrior 56
  167. IO Warrior 24 Power Vampire
  168. To compile this driver as a module, choose M here: the
  169. module will be called iowarrior.
  170. config USB_TEST
  171. tristate "USB testing driver"
  172. depends on USB
  173. help
  174. This driver is for testing host controller software. It is used
  175. with specialized device firmware for regression and stress testing,
  176. to help prevent problems from cropping up with "real" drivers.
  177. See <http://www.linux-usb.org/usbtest/> for more information,
  178. including sample test device firmware and "how to use it".
  179. config USB_EHSET_TEST_FIXTURE
  180. tristate "USB EHSET Test Fixture Driver"
  181. depends on USB && USB_EHCI_EHSET
  182. default n
  183. help
  184. Say Y here if you want to use EHSET Test Fixture device for host
  185. compliance testing.
  186. This driver initiates test modes on the downstream port to which the
  187. test fixture is attached.
  188. See <http://www.usb.org/developers/onthego/EHSET_v1.01.pdf>
  189. for more information.
  190. config USB_ISIGHTFW
  191. tristate "iSight firmware loading support"
  192. depends on USB
  193. select FW_LOADER
  194. help
  195. This driver loads firmware for USB Apple iSight cameras, allowing
  196. them to be driven by the USB video class driver available at
  197. http://linux-uvc.berlios.de
  198. The firmware for this driver must be extracted from the MacOS
  199. driver beforehand. Tools for doing so are available at
  200. http://bersace03.free.fr
  201. config USB_YUREX
  202. tristate "USB YUREX driver support"
  203. depends on USB
  204. help
  205. Say Y here if you want to connect a YUREX to your computer's
  206. USB port. The YUREX is a leg-shakes sensor. See
  207. <http://bbu.kayac.com/en/> for further information.
  208. This driver supports read/write of leg-shakes counter and
  209. fasync for the counter update via a device file /dev/yurex*.
  210. To compile this driver as a module, choose M here: the
  211. module will be called yurex.
  212. config USB_QCOM_DIAG_BRIDGE
  213. tristate "USB Qualcomm diagnostic bridge driver"
  214. depends on USB
  215. help
  216. Say Y here if you have a Qualcomm modem device connected via USB that
  217. will be bridged in kernel space. This driver communicates with the
  218. diagnostic interface and allows for bridging with the diag forwarding
  219. driver.
  220. To compile this driver as a module, choose M here: the
  221. module will be called diag_bridge. If unsure, choose N.
  222. config USB_QCOM_DIAG_BRIDGE_TEST
  223. tristate "USB Qualcomm diagnostic bridge driver test"
  224. depends on USB && USB_QCOM_DIAG_BRIDGE
  225. help
  226. Say Y here if you want to enable the test hook for the
  227. Qualcomm diag bridge driver. When enabled, this will create
  228. a debugfs file entry named "diag_bridge_test" which can be used
  229. to send a ping command to the diag port of the modem over USB.
  230. To compile this driver as a module, choose M here: the
  231. module will be called diag_bridge_test. If unsure, choose N.
  232. config USB_QCOM_MDM_BRIDGE
  233. tristate "USB Qualcomm modem bridge driver for DUN and RMNET"
  234. depends on USB
  235. help
  236. Say Y here if you have a Qualcomm modem device connected via USB that
  237. will be bridged in kernel space. This driver works as a bridge to pass
  238. control and data packets between the modem and peripheral usb gadget
  239. driver for dial up network and RMNET.
  240. To compile this driver as a module, choose M here: the module
  241. will be called mdm_bridge. If unsure, choose N.
  242. config USB_QCOM_KS_BRIDGE
  243. tristate "USB Qualcomm kick start bridge"
  244. depends on USB
  245. help
  246. Say Y here if you have a Qualcomm modem device connected via USB that
  247. will be bridged in kernel space. This driver works as a bridge to pass
  248. boot images, ram-dumps and efs sync
  249. To compile this driver as a module, choose M here: the module
  250. will be called ks_bridge. If unsure, choose N.