Kconfig 17 KB

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