Kconfig 16 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469
  1. #
  2. # USB Gadget support on a system involves
  3. # (a) a peripheral controller, and
  4. # (b) the gadget driver using it.
  5. #
  6. # NOTE: Gadget support ** DOES NOT ** depend on host-side CONFIG_USB !!
  7. #
  8. # - Host systems (like PCs) need CONFIG_USB (with "A" jacks).
  9. # - Peripherals (like PDAs) need CONFIG_USB_GADGET (with "B" jacks).
  10. # - Some systems have both kinds of controllers.
  11. #
  12. # With help from a special transceiver and a "Mini-AB" jack, systems with
  13. # both kinds of controller can also support "USB On-the-Go" (CONFIG_USB_OTG).
  14. #
  15. menu "USB Gadget Support"
  16. config USB_GADGET
  17. tristate "Support for USB Gadgets"
  18. help
  19. USB is a master/slave protocol, organized with one master
  20. host (such as a PC) controlling up to 127 peripheral devices.
  21. The USB hardware is asymmetric, which makes it easier to set up:
  22. you can't connect a "to-the-host" connector to a peripheral.
  23. Linux can run in the host, or in the peripheral. In both cases
  24. you need a low level bus controller driver, and some software
  25. talking to it. Peripheral controllers are often discrete silicon,
  26. or are integrated with the CPU in a microcontroller. The more
  27. familiar host side controllers have names like "EHCI", "OHCI",
  28. or "UHCI", and are usually integrated into southbridges on PC
  29. motherboards.
  30. Enable this configuration option if you want to run Linux inside
  31. a USB peripheral device. Configure one hardware driver for your
  32. peripheral/device side bus controller, and a "gadget driver" for
  33. your peripheral protocol. (If you use modular gadget drivers,
  34. you may configure more than one.)
  35. If in doubt, say "N" and don't enable these drivers; most people
  36. don't have this kind of hardware (except maybe inside Linux PDAs).
  37. For more information, see <http://www.linux-usb.org/gadget> and
  38. the kernel DocBook documentation for this API.
  39. config USB_GADGET_DEBUG_FILES
  40. boolean "Debugging information files"
  41. depends on USB_GADGET && PROC_FS
  42. help
  43. Some of the drivers in the "gadget" framework can expose
  44. debugging information in files such as /proc/driver/udc
  45. (for a peripheral controller). The information in these
  46. files may help when you're troubleshooting or bringing up a
  47. driver on a new board. Enable these files by choosing "Y"
  48. here. If in doubt, or to conserve kernel memory, say "N".
  49. config USB_GADGET_SELECTED
  50. boolean
  51. #
  52. # USB Peripheral Controller Support
  53. #
  54. choice
  55. prompt "USB Peripheral Controller"
  56. depends on USB_GADGET
  57. help
  58. A USB device uses a controller to talk to its host.
  59. Systems should have only one such upstream link.
  60. Many controller drivers are platform-specific; these
  61. often need board-specific hooks.
  62. config USB_GADGET_FSL_USB2
  63. boolean "Freescale Highspeed USB DR Peripheral Controller"
  64. depends on MPC834x || PPC_MPC831x
  65. select USB_GADGET_DUALSPEED
  66. help
  67. Some of Freescale PowerPC processors have a High Speed
  68. Dual-Role(DR) USB controller, which supports device mode.
  69. The number of programmable endpoints is different through
  70. SOC revisions.
  71. Say "y" to link the driver statically, or "m" to build a
  72. dynamically linked module called "fsl_usb2_udc" and force
  73. all gadget drivers to also be dynamically linked.
  74. config USB_FSL_USB2
  75. tristate
  76. depends on USB_GADGET_FSL_USB2
  77. default USB_GADGET
  78. select USB_GADGET_SELECTED
  79. config USB_GADGET_NET2280
  80. boolean "NetChip 228x"
  81. depends on PCI
  82. select USB_GADGET_DUALSPEED
  83. help
  84. NetChip 2280 / 2282 is a PCI based USB peripheral controller which
  85. supports both full and high speed USB 2.0 data transfers.
  86. It has six configurable endpoints, as well as endpoint zero
  87. (for control transfers) and several endpoints with dedicated
  88. functions.
  89. Say "y" to link the driver statically, or "m" to build a
  90. dynamically linked module called "net2280" and force all
  91. gadget drivers to also be dynamically linked.
  92. config USB_NET2280
  93. tristate
  94. depends on USB_GADGET_NET2280
  95. default USB_GADGET
  96. select USB_GADGET_SELECTED
  97. config USB_GADGET_PXA2XX
  98. boolean "PXA 25x or IXP 4xx"
  99. depends on (ARCH_PXA && PXA25x) || ARCH_IXP4XX
  100. help
  101. Intel's PXA 25x series XScale ARM-5TE processors include
  102. an integrated full speed USB 1.1 device controller. The
  103. controller in the IXP 4xx series is register-compatible.
  104. It has fifteen fixed-function endpoints, as well as endpoint
  105. zero (for control transfers).
  106. Say "y" to link the driver statically, or "m" to build a
  107. dynamically linked module called "pxa2xx_udc" and force all
  108. gadget drivers to also be dynamically linked.
  109. config USB_PXA2XX
  110. tristate
  111. depends on USB_GADGET_PXA2XX
  112. default USB_GADGET
  113. select USB_GADGET_SELECTED
  114. # if there's only one gadget driver, using only two bulk endpoints,
  115. # don't waste memory for the other endpoints
  116. config USB_PXA2XX_SMALL
  117. depends on USB_GADGET_PXA2XX
  118. bool
  119. default n if USB_ETH_RNDIS
  120. default y if USB_ZERO
  121. default y if USB_ETH
  122. default y if USB_G_SERIAL
  123. config USB_GADGET_GOKU
  124. boolean "Toshiba TC86C001 'Goku-S'"
  125. depends on PCI
  126. help
  127. The Toshiba TC86C001 is a PCI device which includes controllers
  128. for full speed USB devices, IDE, I2C, SIO, plus a USB host (OHCI).
  129. The device controller has three configurable (bulk or interrupt)
  130. endpoints, plus endpoint zero (for control transfers).
  131. Say "y" to link the driver statically, or "m" to build a
  132. dynamically linked module called "goku_udc" and to force all
  133. gadget drivers to also be dynamically linked.
  134. config USB_GOKU
  135. tristate
  136. depends on USB_GADGET_GOKU
  137. default USB_GADGET
  138. select USB_GADGET_SELECTED
  139. config USB_GADGET_LH7A40X
  140. boolean "LH7A40X"
  141. depends on ARCH_LH7A40X
  142. help
  143. This driver provides USB Device Controller driver for LH7A40x
  144. config USB_LH7A40X
  145. tristate
  146. depends on USB_GADGET_LH7A40X
  147. default USB_GADGET
  148. select USB_GADGET_SELECTED
  149. config USB_GADGET_OMAP
  150. boolean "OMAP USB Device Controller"
  151. depends on ARCH_OMAP
  152. select ISP1301_OMAP if MACH_OMAP_H2 || MACH_OMAP_H3
  153. help
  154. Many Texas Instruments OMAP processors have flexible full
  155. speed USB device controllers, with support for up to 30
  156. endpoints (plus endpoint zero). This driver supports the
  157. controller in the OMAP 1611, and should work with controllers
  158. in other OMAP processors too, given minor tweaks.
  159. Say "y" to link the driver statically, or "m" to build a
  160. dynamically linked module called "omap_udc" and force all
  161. gadget drivers to also be dynamically linked.
  162. config USB_OMAP
  163. tristate
  164. depends on USB_GADGET_OMAP
  165. default USB_GADGET
  166. select USB_GADGET_SELECTED
  167. config USB_OTG
  168. boolean "OTG Support"
  169. depends on USB_GADGET_OMAP && ARCH_OMAP_OTG && USB_OHCI_HCD
  170. help
  171. The most notable feature of USB OTG is support for a
  172. "Dual-Role" device, which can act as either a device
  173. or a host. The initial role choice can be changed
  174. later, when two dual-role devices talk to each other.
  175. Select this only if your OMAP board has a Mini-AB connector.
  176. config USB_GADGET_AT91
  177. boolean "AT91 USB Device Port"
  178. depends on ARCH_AT91 && !ARCH_AT91SAM9RL
  179. select USB_GADGET_SELECTED
  180. help
  181. Many Atmel AT91 processors (such as the AT91RM2000) have a
  182. full speed USB Device Port with support for five configurable
  183. endpoints (plus endpoint zero).
  184. Say "y" to link the driver statically, or "m" to build a
  185. dynamically linked module called "at91_udc" and force all
  186. gadget drivers to also be dynamically linked.
  187. config USB_AT91
  188. tristate
  189. depends on USB_GADGET_AT91
  190. default USB_GADGET
  191. config USB_GADGET_M66592
  192. boolean "M66592 driver"
  193. select USB_GADGET_DUALSPEED
  194. help
  195. M66592 is a USB 2.0 peripheral controller.
  196. It has seven configurable endpoints, and endpoint zero.
  197. Say "y" to link the driver statically, or "m" to build a
  198. dynamically linked module called "m66592_udc" and force all
  199. gadget drivers to also be dynamically linked.
  200. config USB_M66592
  201. tristate
  202. depends on USB_GADGET_M66592
  203. default USB_GADGET
  204. select USB_GADGET_SELECTED
  205. config USB_GADGET_DUMMY_HCD
  206. boolean "Dummy HCD (DEVELOPMENT)"
  207. depends on (USB=y || (USB=m && USB_GADGET=m)) && EXPERIMENTAL
  208. select USB_GADGET_DUALSPEED
  209. help
  210. This host controller driver emulates USB, looping all data transfer
  211. requests back to a USB "gadget driver" in the same host. The host
  212. side is the master; the gadget side is the slave. Gadget drivers
  213. can be high, full, or low speed; and they have access to endpoints
  214. like those from NET2280, PXA2xx, or SA1100 hardware.
  215. This may help in some stages of creating a driver to embed in a
  216. Linux device, since it lets you debug several parts of the gadget
  217. driver without its hardware or drivers being involved.
  218. Since such a gadget side driver needs to interoperate with a host
  219. side Linux-USB device driver, this may help to debug both sides
  220. of a USB protocol stack.
  221. Say "y" to link the driver statically, or "m" to build a
  222. dynamically linked module called "dummy_hcd" and force all
  223. gadget drivers to also be dynamically linked.
  224. config USB_DUMMY_HCD
  225. tristate
  226. depends on USB_GADGET_DUMMY_HCD
  227. default USB_GADGET
  228. select USB_GADGET_SELECTED
  229. # NOTE: Please keep dummy_hcd LAST so that "real hardware" appears
  230. # first and will be selected by default.
  231. endchoice
  232. config USB_GADGET_DUALSPEED
  233. bool
  234. depends on USB_GADGET
  235. default n
  236. help
  237. Means that gadget drivers should include extra descriptors
  238. and code to handle dual-speed controllers.
  239. #
  240. # USB Gadget Drivers
  241. #
  242. choice
  243. tristate "USB Gadget Drivers"
  244. depends on USB_GADGET && USB_GADGET_SELECTED
  245. default USB_ETH
  246. help
  247. A Linux "Gadget Driver" talks to the USB Peripheral Controller
  248. driver through the abstract "gadget" API. Some other operating
  249. systems call these "client" drivers, of which "class drivers"
  250. are a subset (implementing a USB device class specification).
  251. A gadget driver implements one or more USB functions using
  252. the peripheral hardware.
  253. Gadget drivers are hardware-neutral, or "platform independent",
  254. except that they sometimes must understand quirks or limitations
  255. of the particular controllers they work with. For example, when
  256. a controller doesn't support alternate configurations or provide
  257. enough of the right types of endpoints, the gadget driver might
  258. not be able work with that controller, or might need to implement
  259. a less common variant of a device class protocol.
  260. # this first set of drivers all depend on bulk-capable hardware.
  261. config USB_ZERO
  262. tristate "Gadget Zero (DEVELOPMENT)"
  263. depends on EXPERIMENTAL
  264. help
  265. Gadget Zero is a two-configuration device. It either sinks and
  266. sources bulk data; or it loops back a configurable number of
  267. transfers. It also implements control requests, for "chapter 9"
  268. conformance. The driver needs only two bulk-capable endpoints, so
  269. it can work on top of most device-side usb controllers. It's
  270. useful for testing, and is also a working example showing how
  271. USB "gadget drivers" can be written.
  272. Make this be the first driver you try using on top of any new
  273. USB peripheral controller driver. Then you can use host-side
  274. test software, like the "usbtest" driver, to put your hardware
  275. and its driver through a basic set of functional tests.
  276. Gadget Zero also works with the host-side "usb-skeleton" driver,
  277. and with many kinds of host-side test software. You may need
  278. to tweak product and vendor IDs before host software knows about
  279. this device, and arrange to select an appropriate configuration.
  280. Say "y" to link the driver statically, or "m" to build a
  281. dynamically linked module called "g_zero".
  282. config USB_ZERO_HNPTEST
  283. boolean "HNP Test Device"
  284. depends on USB_ZERO && USB_OTG
  285. help
  286. You can configure this device to enumerate using the device
  287. identifiers of the USB-OTG test device. That means that when
  288. this gadget connects to another OTG device, with this one using
  289. the "B-Peripheral" role, that device will use HNP to let this
  290. one serve as the USB host instead (in the "B-Host" role).
  291. config USB_ETH
  292. tristate "Ethernet Gadget (with CDC Ethernet support)"
  293. depends on NET
  294. help
  295. This driver implements Ethernet style communication, in either
  296. of two ways:
  297. - The "Communication Device Class" (CDC) Ethernet Control Model.
  298. That protocol is often avoided with pure Ethernet adapters, in
  299. favor of simpler vendor-specific hardware, but is widely
  300. supported by firmware for smart network devices.
  301. - On hardware can't implement that protocol, a simple CDC subset
  302. is used, placing fewer demands on USB.
  303. RNDIS support is a third option, more demanding than that subset.
  304. Within the USB device, this gadget driver exposes a network device
  305. "usbX", where X depends on what other networking devices you have.
  306. Treat it like a two-node Ethernet link: host, and gadget.
  307. The Linux-USB host-side "usbnet" driver interoperates with this
  308. driver, so that deep I/O queues can be supported. On 2.4 kernels,
  309. use "CDCEther" instead, if you're using the CDC option. That CDC
  310. mode should also interoperate with standard CDC Ethernet class
  311. drivers on other host operating systems.
  312. Say "y" to link the driver statically, or "m" to build a
  313. dynamically linked module called "g_ether".
  314. config USB_ETH_RNDIS
  315. bool "RNDIS support (EXPERIMENTAL)"
  316. depends on USB_ETH && EXPERIMENTAL
  317. default y
  318. help
  319. Microsoft Windows XP bundles the "Remote NDIS" (RNDIS) protocol,
  320. and Microsoft provides redistributable binary RNDIS drivers for
  321. older versions of Windows.
  322. If you say "y" here, the Ethernet gadget driver will try to provide
  323. a second device configuration, supporting RNDIS to talk to such
  324. Microsoft USB hosts.
  325. To make MS-Windows work with this, use Documentation/usb/linux.inf
  326. as the "driver info file". For versions of MS-Windows older than
  327. XP, you'll need to download drivers from Microsoft's website; a URL
  328. is given in comments found in that info file.
  329. config USB_GADGETFS
  330. tristate "Gadget Filesystem (EXPERIMENTAL)"
  331. depends on EXPERIMENTAL
  332. help
  333. This driver provides a filesystem based API that lets user mode
  334. programs implement a single-configuration USB device, including
  335. endpoint I/O and control requests that don't relate to enumeration.
  336. All endpoints, transfer speeds, and transfer types supported by
  337. the hardware are available, through read() and write() calls.
  338. Say "y" to link the driver statically, or "m" to build a
  339. dynamically linked module called "gadgetfs".
  340. config USB_FILE_STORAGE
  341. tristate "File-backed Storage Gadget"
  342. depends on BLOCK
  343. help
  344. The File-backed Storage Gadget acts as a USB Mass Storage
  345. disk drive. As its storage repository it can use a regular
  346. file or a block device (in much the same way as the "loop"
  347. device driver), specified as a module parameter.
  348. Say "y" to link the driver statically, or "m" to build a
  349. dynamically linked module called "g_file_storage".
  350. config USB_FILE_STORAGE_TEST
  351. bool "File-backed Storage Gadget testing version"
  352. depends on USB_FILE_STORAGE
  353. default n
  354. help
  355. Say "y" to generate the larger testing version of the
  356. File-backed Storage Gadget, useful for probing the
  357. behavior of USB Mass Storage hosts. Not needed for
  358. normal operation.
  359. config USB_G_SERIAL
  360. tristate "Serial Gadget (with CDC ACM support)"
  361. help
  362. The Serial Gadget talks to the Linux-USB generic serial driver.
  363. This driver supports a CDC-ACM module option, which can be used
  364. to interoperate with MS-Windows hosts or with the Linux-USB
  365. "cdc-acm" driver.
  366. Say "y" to link the driver statically, or "m" to build a
  367. dynamically linked module called "g_serial".
  368. For more information, see Documentation/usb/gadget_serial.txt
  369. which includes instructions and a "driver info file" needed to
  370. make MS-Windows work with this driver.
  371. config USB_MIDI_GADGET
  372. tristate "MIDI Gadget (EXPERIMENTAL)"
  373. depends on SND && EXPERIMENTAL
  374. select SND_RAWMIDI
  375. help
  376. The MIDI Gadget acts as a USB Audio device, with one MIDI
  377. input and one MIDI output. These MIDI jacks appear as
  378. a sound "card" in the ALSA sound system. Other MIDI
  379. connections can then be made on the gadget system, using
  380. ALSA's aconnect utility etc.
  381. Say "y" to link the driver statically, or "m" to build a
  382. dynamically linked module called "g_midi".
  383. # put drivers that need isochronous transfer support (for audio
  384. # or video class gadget drivers), or specific hardware, here.
  385. # - none yet
  386. endchoice
  387. endmenu