Kconfig 33 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662663664665666667668669670671672673674675676677678679680681682683684685686687688689690691692693694695696697698699700701702703704705706707708709710711712713714715716717718719720721722723724725726727728729730731732733734735736737738739740741742743744745746747748749750751752753754755756757758759760761762763764765766767768769770771772773774775776777778779780781782783784785786787788789790791792793794795796797798799800801802803804805806807808809810811812813814815816817818819820821822823824825826827828829830831832833834835836837838839840841842843844845846847848849850851852853854855856857858859860861862863864865866867868869870871872873874875876877878879880881882883884885886887888889890891892893894895896897898899900901902903904905906907908909910911912913914915916917918919920921922923924925926927928929930931932933934935936937938939940941
  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. menuconfig USB_GADGET
  16. tristate "USB Gadget Support"
  17. select NLS
  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. if USB_GADGET
  40. config USB_GADGET_DEBUG
  41. boolean "Debugging messages (DEVELOPMENT)"
  42. depends on DEBUG_KERNEL
  43. help
  44. Many controller and gadget drivers will print some debugging
  45. messages if you use this option to ask for those messages.
  46. Avoid enabling these messages, even if you're actively
  47. debugging such a driver. Many drivers will emit so many
  48. messages that the driver timings are affected, which will
  49. either create new failure modes or remove the one you're
  50. trying to track down. Never enable these messages for a
  51. production build.
  52. config USB_GADGET_DEBUG_FILES
  53. boolean "Debugging information files (DEVELOPMENT)"
  54. depends on PROC_FS
  55. help
  56. Some of the drivers in the "gadget" framework can expose
  57. debugging information in files such as /proc/driver/udc
  58. (for a peripheral controller). The information in these
  59. files may help when you're troubleshooting or bringing up a
  60. driver on a new board. Enable these files by choosing "Y"
  61. here. If in doubt, or to conserve kernel memory, say "N".
  62. config USB_GADGET_DEBUG_FS
  63. boolean "Debugging information files in debugfs (DEVELOPMENT)"
  64. depends on DEBUG_FS
  65. help
  66. Some of the drivers in the "gadget" framework can expose
  67. debugging information in files under /sys/kernel/debug/.
  68. The information in these files may help when you're
  69. troubleshooting or bringing up a driver on a new board.
  70. Enable these files by choosing "Y" here. If in doubt, or
  71. to conserve kernel memory, say "N".
  72. config USB_GADGET_VBUS_DRAW
  73. int "Maximum VBUS Power usage (2-500 mA)"
  74. range 2 500
  75. default 2
  76. help
  77. Some devices need to draw power from USB when they are
  78. configured, perhaps to operate circuitry or to recharge
  79. batteries. This is in addition to any local power supply,
  80. such as an AC adapter or batteries.
  81. Enter the maximum power your device draws through USB, in
  82. milliAmperes. The permitted range of values is 2 - 500 mA;
  83. 0 mA would be legal, but can make some hosts misbehave.
  84. This value will be used except for system-specific gadget
  85. drivers that have more specific information.
  86. config USB_GADGET_STORAGE_NUM_BUFFERS
  87. int "Number of storage pipeline buffers"
  88. range 2 4
  89. default 2
  90. help
  91. Usually 2 buffers are enough to establish a good buffering
  92. pipeline. The number may be increased in order to compensate
  93. for a bursty VFS behaviour. For instance there may be CPU wake up
  94. latencies that makes the VFS to appear bursty in a system with
  95. an CPU on-demand governor. Especially if DMA is doing IO to
  96. offload the CPU. In this case the CPU will go into power
  97. save often and spin up occasionally to move data within VFS.
  98. If selecting USB_GADGET_DEBUG_FILES this value may be set by
  99. a module parameter as well.
  100. If unsure, say 2.
  101. #
  102. # USB Peripheral Controller Support
  103. #
  104. # The order here is alphabetical, except that integrated controllers go
  105. # before discrete ones so they will be the initial/default value:
  106. # - integrated/SOC controllers first
  107. # - licensed IP used in both SOC and discrete versions
  108. # - discrete ones (including all PCI-only controllers)
  109. # - debug/dummy gadget+hcd is last.
  110. #
  111. menu "USB Peripheral Controller"
  112. #
  113. # Integrated controllers
  114. #
  115. config USB_AT91
  116. tristate "Atmel AT91 USB Device Port"
  117. depends on ARCH_AT91
  118. help
  119. Many Atmel AT91 processors (such as the AT91RM2000) have a
  120. full speed USB Device Port with support for five configurable
  121. endpoints (plus endpoint zero).
  122. Say "y" to link the driver statically, or "m" to build a
  123. dynamically linked module called "at91_udc" and force all
  124. gadget drivers to also be dynamically linked.
  125. config USB_LPC32XX
  126. tristate "LPC32XX USB Peripheral Controller"
  127. depends on ARCH_LPC32XX
  128. select USB_ISP1301
  129. help
  130. This option selects the USB device controller in the LPC32xx SoC.
  131. Say "y" to link the driver statically, or "m" to build a
  132. dynamically linked module called "lpc32xx_udc" and force all
  133. gadget drivers to also be dynamically linked.
  134. config USB_ATMEL_USBA
  135. tristate "Atmel USBA"
  136. depends on AVR32 || ARCH_AT91SAM9RL || ARCH_AT91SAM9G45
  137. help
  138. USBA is the integrated high-speed USB Device controller on
  139. the AT32AP700x, some AT91SAM9 and AT91CAP9 processors from Atmel.
  140. config USB_BCM63XX_UDC
  141. tristate "Broadcom BCM63xx Peripheral Controller"
  142. depends on BCM63XX
  143. help
  144. Many Broadcom BCM63xx chipsets (such as the BCM6328) have a
  145. high speed USB Device Port with support for four fixed endpoints
  146. (plus endpoint zero).
  147. Say "y" to link the driver statically, or "m" to build a
  148. dynamically linked module called "bcm63xx_udc".
  149. config USB_FSL_USB2
  150. tristate "Freescale Highspeed USB DR Peripheral Controller"
  151. depends on FSL_SOC || ARCH_MXC
  152. select USB_FSL_MPH_DR_OF if OF
  153. help
  154. Some of Freescale PowerPC and i.MX processors have a High Speed
  155. Dual-Role(DR) USB controller, which supports device mode.
  156. The number of programmable endpoints is different through
  157. SOC revisions.
  158. Say "y" to link the driver statically, or "m" to build a
  159. dynamically linked module called "fsl_usb2_udc" and force
  160. all gadget drivers to also be dynamically linked.
  161. config USB_FUSB300
  162. tristate "Faraday FUSB300 USB Peripheral Controller"
  163. depends on !PHYS_ADDR_T_64BIT
  164. help
  165. Faraday usb device controller FUSB300 driver
  166. config USB_OMAP
  167. tristate "OMAP USB Device Controller"
  168. depends on ARCH_OMAP1
  169. select ISP1301_OMAP if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_H4_OTG
  170. select USB_OTG_UTILS if ARCH_OMAP
  171. help
  172. Many Texas Instruments OMAP processors have flexible full
  173. speed USB device controllers, with support for up to 30
  174. endpoints (plus endpoint zero). This driver supports the
  175. controller in the OMAP 1611, and should work with controllers
  176. in other OMAP processors too, given minor tweaks.
  177. Say "y" to link the driver statically, or "m" to build a
  178. dynamically linked module called "omap_udc" and force all
  179. gadget drivers to also be dynamically linked.
  180. config USB_PXA25X
  181. tristate "PXA 25x or IXP 4xx"
  182. depends on (ARCH_PXA && PXA25x) || ARCH_IXP4XX
  183. select USB_OTG_UTILS
  184. help
  185. Intel's PXA 25x series XScale ARM-5TE processors include
  186. an integrated full speed USB 1.1 device controller. The
  187. controller in the IXP 4xx series is register-compatible.
  188. It has fifteen fixed-function endpoints, as well as endpoint
  189. zero (for control transfers).
  190. Say "y" to link the driver statically, or "m" to build a
  191. dynamically linked module called "pxa25x_udc" and force all
  192. gadget drivers to also be dynamically linked.
  193. # if there's only one gadget driver, using only two bulk endpoints,
  194. # don't waste memory for the other endpoints
  195. config USB_PXA25X_SMALL
  196. depends on USB_PXA25X
  197. bool
  198. default n if USB_ETH_RNDIS
  199. default y if USB_ZERO
  200. default y if USB_ETH
  201. default y if USB_G_SERIAL
  202. config USB_R8A66597
  203. tristate "Renesas R8A66597 USB Peripheral Controller"
  204. help
  205. R8A66597 is a discrete USB host and peripheral controller chip that
  206. supports both full and high speed USB 2.0 data transfers.
  207. It has nine configurable endpoints, and endpoint zero.
  208. Say "y" to link the driver statically, or "m" to build a
  209. dynamically linked module called "r8a66597_udc" and force all
  210. gadget drivers to also be dynamically linked.
  211. config USB_RENESAS_USBHS_UDC
  212. tristate 'Renesas USBHS controller'
  213. depends on USB_RENESAS_USBHS
  214. help
  215. Renesas USBHS is a discrete USB host and peripheral controller chip
  216. that supports both full and high speed USB 2.0 data transfers.
  217. It has nine or more configurable endpoints, and endpoint zero.
  218. Say "y" to link the driver statically, or "m" to build a
  219. dynamically linked module called "renesas_usbhs" and force all
  220. gadget drivers to also be dynamically linked.
  221. config USB_PXA27X
  222. tristate "PXA 27x"
  223. depends on ARCH_PXA && (PXA27x || PXA3xx)
  224. select USB_OTG_UTILS
  225. help
  226. Intel's PXA 27x series XScale ARM v5TE processors include
  227. an integrated full speed USB 1.1 device controller.
  228. It has up to 23 endpoints, as well as endpoint zero (for
  229. control transfers).
  230. Say "y" to link the driver statically, or "m" to build a
  231. dynamically linked module called "pxa27x_udc" and force all
  232. gadget drivers to also be dynamically linked.
  233. config USB_S3C_HSOTG
  234. tristate "S3C HS/OtG USB Device controller"
  235. depends on S3C_DEV_USB_HSOTG
  236. help
  237. The Samsung S3C64XX USB2.0 high-speed gadget controller
  238. integrated into the S3C64XX series SoC.
  239. config USB_IMX
  240. tristate "Freescale i.MX1 USB Peripheral Controller"
  241. depends on ARCH_MXC
  242. help
  243. Freescale's i.MX1 includes an integrated full speed
  244. USB 1.1 device controller.
  245. It has Six fixed-function endpoints, as well as endpoint
  246. zero (for control transfers).
  247. Say "y" to link the driver statically, or "m" to build a
  248. dynamically linked module called "imx_udc" and force all
  249. gadget drivers to also be dynamically linked.
  250. config USB_S3C2410
  251. tristate "S3C2410 USB Device Controller"
  252. depends on ARCH_S3C24XX
  253. help
  254. Samsung's S3C2410 is an ARM-4 processor with an integrated
  255. full speed USB 1.1 device controller. It has 4 configurable
  256. endpoints, as well as endpoint zero (for control transfers).
  257. This driver has been tested on the S3C2410, S3C2412, and
  258. S3C2440 processors.
  259. config USB_S3C2410_DEBUG
  260. boolean "S3C2410 udc debug messages"
  261. depends on USB_S3C2410
  262. config USB_S3C_HSUDC
  263. tristate "S3C2416, S3C2443 and S3C2450 USB Device Controller"
  264. depends on ARCH_S3C24XX
  265. help
  266. Samsung's S3C2416, S3C2443 and S3C2450 is an ARM9 based SoC
  267. integrated with dual speed USB 2.0 device controller. It has
  268. 8 endpoints, as well as endpoint zero.
  269. This driver has been tested on S3C2416 and S3C2450 processors.
  270. config USB_MV_UDC
  271. tristate "Marvell USB2.0 Device Controller"
  272. help
  273. Marvell Socs (including PXA and MMP series) include a high speed
  274. USB2.0 OTG controller, which can be configured as high speed or
  275. full speed USB peripheral.
  276. config USB_MV_U3D
  277. tristate "MARVELL PXA2128 USB 3.0 controller"
  278. depends on CPU_MMP3
  279. select USB_GADGET_DUALSPEED
  280. select USB_GADGET_SUPERSPEED
  281. help
  282. MARVELL PXA2128 Processor series include a super speed USB3.0 device
  283. controller, which support super speed USB peripheral.
  284. #
  285. # Controllers available in both integrated and discrete versions
  286. #
  287. # musb builds in ../musb along with host support
  288. config USB_GADGET_MUSB_HDRC
  289. tristate "Inventra HDRC USB Peripheral (TI, ADI, ...)"
  290. depends on USB_MUSB_HDRC
  291. help
  292. This OTG-capable silicon IP is used in dual designs including
  293. the TI DaVinci, OMAP 243x, OMAP 343x, TUSB 6010, and ADI Blackfin
  294. config USB_M66592
  295. tristate "Renesas M66592 USB Peripheral Controller"
  296. help
  297. M66592 is a discrete USB peripheral controller chip that
  298. supports both full and high speed USB 2.0 data transfers.
  299. It has seven configurable endpoints, and endpoint zero.
  300. Say "y" to link the driver statically, or "m" to build a
  301. dynamically linked module called "m66592_udc" and force all
  302. gadget drivers to also be dynamically linked.
  303. #
  304. # Controllers available only in discrete form (and all PCI controllers)
  305. #
  306. config USB_AMD5536UDC
  307. tristate "AMD5536 UDC"
  308. depends on PCI
  309. help
  310. The AMD5536 UDC is part of the AMD Geode CS5536, an x86 southbridge.
  311. It is a USB Highspeed DMA capable USB device controller. Beside ep0
  312. it provides 4 IN and 4 OUT endpoints (bulk or interrupt type).
  313. The UDC port supports OTG operation, and may be used as a host port
  314. if it's not being used to implement peripheral or OTG roles.
  315. Say "y" to link the driver statically, or "m" to build a
  316. dynamically linked module called "amd5536udc" and force all
  317. gadget drivers to also be dynamically linked.
  318. config USB_FSL_QE
  319. tristate "Freescale QE/CPM USB Device Controller"
  320. depends on FSL_SOC && (QUICC_ENGINE || CPM)
  321. help
  322. Some of Freescale PowerPC processors have a Full Speed
  323. QE/CPM2 USB controller, which support device mode with 4
  324. programmable endpoints. This driver supports the
  325. controller in the MPC8360 and MPC8272, and should work with
  326. controllers having QE or CPM2, given minor tweaks.
  327. Set CONFIG_USB_GADGET to "m" to build this driver as a
  328. dynamically linked module called "fsl_qe_udc".
  329. config USB_NET2272
  330. tristate "PLX NET2272"
  331. help
  332. PLX NET2272 is a USB peripheral controller which supports
  333. both full and high speed USB 2.0 data transfers.
  334. It has three configurable endpoints, as well as endpoint zero
  335. (for control transfer).
  336. Say "y" to link the driver statically, or "m" to build a
  337. dynamically linked module called "net2272" and force all
  338. gadget drivers to also be dynamically linked.
  339. config USB_NET2272_DMA
  340. boolean "Support external DMA controller"
  341. depends on USB_NET2272
  342. help
  343. The NET2272 part can optionally support an external DMA
  344. controller, but your board has to have support in the
  345. driver itself.
  346. If unsure, say "N" here. The driver works fine in PIO mode.
  347. config USB_NET2280
  348. tristate "NetChip 228x"
  349. depends on PCI
  350. help
  351. NetChip 2280 / 2282 is a PCI based USB peripheral controller which
  352. supports both full and high speed USB 2.0 data transfers.
  353. It has six configurable endpoints, as well as endpoint zero
  354. (for control transfers) and several endpoints with dedicated
  355. functions.
  356. Say "y" to link the driver statically, or "m" to build a
  357. dynamically linked module called "net2280" and force all
  358. gadget drivers to also be dynamically linked.
  359. config USB_GOKU
  360. tristate "Toshiba TC86C001 'Goku-S'"
  361. depends on PCI
  362. help
  363. The Toshiba TC86C001 is a PCI device which includes controllers
  364. for full speed USB devices, IDE, I2C, SIO, plus a USB host (OHCI).
  365. The device controller has three configurable (bulk or interrupt)
  366. endpoints, plus endpoint zero (for control transfers).
  367. Say "y" to link the driver statically, or "m" to build a
  368. dynamically linked module called "goku_udc" and to force all
  369. gadget drivers to also be dynamically linked.
  370. config USB_EG20T
  371. tristate "Intel EG20T PCH/LAPIS Semiconductor IOH(ML7213/ML7831) UDC"
  372. depends on PCI
  373. help
  374. This is a USB device driver for EG20T PCH.
  375. EG20T PCH is the platform controller hub that is used in Intel's
  376. general embedded platform. EG20T PCH has USB device interface.
  377. Using this interface, it is able to access system devices connected
  378. to USB device.
  379. This driver enables USB device function.
  380. USB device is a USB peripheral controller which
  381. supports both full and high speed USB 2.0 data transfers.
  382. This driver supports both control transfer and bulk transfer modes.
  383. This driver dose not support interrupt transfer or isochronous
  384. transfer modes.
  385. This driver also can be used for LAPIS Semiconductor's ML7213 which is
  386. for IVI(In-Vehicle Infotainment) use.
  387. ML7831 is for general purpose use.
  388. ML7213/ML7831 is companion chip for Intel Atom E6xx series.
  389. ML7213/ML7831 is completely compatible for Intel EG20T PCH.
  390. #
  391. # LAST -- dummy/emulated controller
  392. #
  393. config USB_DUMMY_HCD
  394. tristate "Dummy HCD (DEVELOPMENT)"
  395. depends on USB=y || (USB=m && USB_GADGET=m)
  396. help
  397. This host controller driver emulates USB, looping all data transfer
  398. requests back to a USB "gadget driver" in the same host. The host
  399. side is the master; the gadget side is the slave. Gadget drivers
  400. can be high, full, or low speed; and they have access to endpoints
  401. like those from NET2280, PXA2xx, or SA1100 hardware.
  402. This may help in some stages of creating a driver to embed in a
  403. Linux device, since it lets you debug several parts of the gadget
  404. driver without its hardware or drivers being involved.
  405. Since such a gadget side driver needs to interoperate with a host
  406. side Linux-USB device driver, this may help to debug both sides
  407. of a USB protocol stack.
  408. Say "y" to link the driver statically, or "m" to build a
  409. dynamically linked module called "dummy_hcd" and force all
  410. gadget drivers to also be dynamically linked.
  411. # NOTE: Please keep dummy_hcd LAST so that "real hardware" appears
  412. # first and will be selected by default.
  413. endmenu
  414. #
  415. # USB Gadget Drivers
  416. #
  417. # composite based drivers
  418. config USB_LIBCOMPOSITE
  419. tristate
  420. depends on USB_GADGET
  421. choice
  422. tristate "USB Gadget Drivers"
  423. default USB_ETH
  424. help
  425. A Linux "Gadget Driver" talks to the USB Peripheral Controller
  426. driver through the abstract "gadget" API. Some other operating
  427. systems call these "client" drivers, of which "class drivers"
  428. are a subset (implementing a USB device class specification).
  429. A gadget driver implements one or more USB functions using
  430. the peripheral hardware.
  431. Gadget drivers are hardware-neutral, or "platform independent",
  432. except that they sometimes must understand quirks or limitations
  433. of the particular controllers they work with. For example, when
  434. a controller doesn't support alternate configurations or provide
  435. enough of the right types of endpoints, the gadget driver might
  436. not be able work with that controller, or might need to implement
  437. a less common variant of a device class protocol.
  438. # this first set of drivers all depend on bulk-capable hardware.
  439. config USB_ZERO
  440. tristate "Gadget Zero (DEVELOPMENT)"
  441. select USB_LIBCOMPOSITE
  442. help
  443. Gadget Zero is a two-configuration device. It either sinks and
  444. sources bulk data; or it loops back a configurable number of
  445. transfers. It also implements control requests, for "chapter 9"
  446. conformance. The driver needs only two bulk-capable endpoints, so
  447. it can work on top of most device-side usb controllers. It's
  448. useful for testing, and is also a working example showing how
  449. USB "gadget drivers" can be written.
  450. Make this be the first driver you try using on top of any new
  451. USB peripheral controller driver. Then you can use host-side
  452. test software, like the "usbtest" driver, to put your hardware
  453. and its driver through a basic set of functional tests.
  454. Gadget Zero also works with the host-side "usb-skeleton" driver,
  455. and with many kinds of host-side test software. You may need
  456. to tweak product and vendor IDs before host software knows about
  457. this device, and arrange to select an appropriate configuration.
  458. Say "y" to link the driver statically, or "m" to build a
  459. dynamically linked module called "g_zero".
  460. config USB_ZERO_HNPTEST
  461. boolean "HNP Test Device"
  462. depends on USB_ZERO && USB_OTG
  463. help
  464. You can configure this device to enumerate using the device
  465. identifiers of the USB-OTG test device. That means that when
  466. this gadget connects to another OTG device, with this one using
  467. the "B-Peripheral" role, that device will use HNP to let this
  468. one serve as the USB host instead (in the "B-Host" role).
  469. config USB_AUDIO
  470. tristate "Audio Gadget"
  471. depends on SND
  472. select USB_LIBCOMPOSITE
  473. select SND_PCM
  474. help
  475. This Gadget Audio driver is compatible with USB Audio Class
  476. specification 2.0. It implements 1 AudioControl interface,
  477. 1 AudioStreaming Interface each for USB-OUT and USB-IN.
  478. Number of channels, sample rate and sample size can be
  479. specified as module parameters.
  480. This driver doesn't expect any real Audio codec to be present
  481. on the device - the audio streams are simply sinked to and
  482. sourced from a virtual ALSA sound card created. The user-space
  483. application may choose to do whatever it wants with the data
  484. received from the USB Host and choose to provide whatever it
  485. wants as audio data to the USB Host.
  486. Say "y" to link the driver statically, or "m" to build a
  487. dynamically linked module called "g_audio".
  488. config GADGET_UAC1
  489. bool "UAC 1.0 (Legacy)"
  490. depends on USB_AUDIO
  491. help
  492. If you instead want older UAC Spec-1.0 driver that also has audio
  493. paths hardwired to the Audio codec chip on-board and doesn't work
  494. without one.
  495. config USB_ETH
  496. tristate "Ethernet Gadget (with CDC Ethernet support)"
  497. depends on NET
  498. select USB_LIBCOMPOSITE
  499. select CRC32
  500. help
  501. This driver implements Ethernet style communication, in one of
  502. several ways:
  503. - The "Communication Device Class" (CDC) Ethernet Control Model.
  504. That protocol is often avoided with pure Ethernet adapters, in
  505. favor of simpler vendor-specific hardware, but is widely
  506. supported by firmware for smart network devices.
  507. - On hardware can't implement that protocol, a simple CDC subset
  508. is used, placing fewer demands on USB.
  509. - CDC Ethernet Emulation Model (EEM) is a newer standard that has
  510. a simpler interface that can be used by more USB hardware.
  511. RNDIS support is an additional option, more demanding than than
  512. subset.
  513. Within the USB device, this gadget driver exposes a network device
  514. "usbX", where X depends on what other networking devices you have.
  515. Treat it like a two-node Ethernet link: host, and gadget.
  516. The Linux-USB host-side "usbnet" driver interoperates with this
  517. driver, so that deep I/O queues can be supported. On 2.4 kernels,
  518. use "CDCEther" instead, if you're using the CDC option. That CDC
  519. mode should also interoperate with standard CDC Ethernet class
  520. drivers on other host operating systems.
  521. Say "y" to link the driver statically, or "m" to build a
  522. dynamically linked module called "g_ether".
  523. config USB_ETH_RNDIS
  524. bool "RNDIS support"
  525. depends on USB_ETH
  526. select USB_LIBCOMPOSITE
  527. default y
  528. help
  529. Microsoft Windows XP bundles the "Remote NDIS" (RNDIS) protocol,
  530. and Microsoft provides redistributable binary RNDIS drivers for
  531. older versions of Windows.
  532. If you say "y" here, the Ethernet gadget driver will try to provide
  533. a second device configuration, supporting RNDIS to talk to such
  534. Microsoft USB hosts.
  535. To make MS-Windows work with this, use Documentation/usb/linux.inf
  536. as the "driver info file". For versions of MS-Windows older than
  537. XP, you'll need to download drivers from Microsoft's website; a URL
  538. is given in comments found in that info file.
  539. config USB_ETH_EEM
  540. bool "Ethernet Emulation Model (EEM) support"
  541. depends on USB_ETH
  542. select USB_LIBCOMPOSITE
  543. default n
  544. help
  545. CDC EEM is a newer USB standard that is somewhat simpler than CDC ECM
  546. and therefore can be supported by more hardware. Technically ECM and
  547. EEM are designed for different applications. The ECM model extends
  548. the network interface to the target (e.g. a USB cable modem), and the
  549. EEM model is for mobile devices to communicate with hosts using
  550. ethernet over USB. For Linux gadgets, however, the interface with
  551. the host is the same (a usbX device), so the differences are minimal.
  552. If you say "y" here, the Ethernet gadget driver will use the EEM
  553. protocol rather than ECM. If unsure, say "n".
  554. config USB_G_NCM
  555. tristate "Network Control Model (NCM) support"
  556. depends on NET
  557. select USB_LIBCOMPOSITE
  558. select CRC32
  559. help
  560. This driver implements USB CDC NCM subclass standard. NCM is
  561. an advanced protocol for Ethernet encapsulation, allows grouping
  562. of several ethernet frames into one USB transfer and different
  563. alignment possibilities.
  564. Say "y" to link the driver statically, or "m" to build a
  565. dynamically linked module called "g_ncm".
  566. config USB_GADGETFS
  567. tristate "Gadget Filesystem"
  568. help
  569. This driver provides a filesystem based API that lets user mode
  570. programs implement a single-configuration USB device, including
  571. endpoint I/O and control requests that don't relate to enumeration.
  572. All endpoints, transfer speeds, and transfer types supported by
  573. the hardware are available, through read() and write() calls.
  574. Say "y" to link the driver statically, or "m" to build a
  575. dynamically linked module called "gadgetfs".
  576. config USB_FUNCTIONFS
  577. tristate "Function Filesystem"
  578. select USB_LIBCOMPOSITE
  579. select USB_FUNCTIONFS_GENERIC if !(USB_FUNCTIONFS_ETH || USB_FUNCTIONFS_RNDIS)
  580. help
  581. The Function Filesystem (FunctionFS) lets one create USB
  582. composite functions in user space in the same way GadgetFS
  583. lets one create USB gadgets in user space. This allows creation
  584. of composite gadgets such that some of the functions are
  585. implemented in kernel space (for instance Ethernet, serial or
  586. mass storage) and other are implemented in user space.
  587. If you say "y" or "m" here you will be able what kind of
  588. configurations the gadget will provide.
  589. Say "y" to link the driver statically, or "m" to build
  590. a dynamically linked module called "g_ffs".
  591. config USB_FUNCTIONFS_ETH
  592. bool "Include configuration with CDC ECM (Ethernet)"
  593. depends on USB_FUNCTIONFS && NET
  594. help
  595. Include a configuration with CDC ECM function (Ethernet) and the
  596. Function Filesystem.
  597. config USB_FUNCTIONFS_RNDIS
  598. bool "Include configuration with RNDIS (Ethernet)"
  599. depends on USB_FUNCTIONFS && NET
  600. help
  601. Include a configuration with RNDIS function (Ethernet) and the Filesystem.
  602. config USB_FUNCTIONFS_GENERIC
  603. bool "Include 'pure' configuration"
  604. depends on USB_FUNCTIONFS
  605. help
  606. Include a configuration with the Function Filesystem alone with
  607. no Ethernet interface.
  608. config USB_MASS_STORAGE
  609. tristate "Mass Storage Gadget"
  610. depends on BLOCK
  611. select USB_LIBCOMPOSITE
  612. help
  613. The Mass Storage Gadget acts as a USB Mass Storage disk drive.
  614. As its storage repository it can use a regular file or a block
  615. device (in much the same way as the "loop" device driver),
  616. specified as a module parameter or sysfs option.
  617. This driver is a replacement for now removed File-backed
  618. Storage Gadget (g_file_storage).
  619. Say "y" to link the driver statically, or "m" to build
  620. a dynamically linked module called "g_mass_storage".
  621. config USB_GADGET_TARGET
  622. tristate "USB Gadget Target Fabric Module"
  623. depends on TARGET_CORE
  624. select USB_LIBCOMPOSITE
  625. help
  626. This fabric is an USB gadget. Two USB protocols are supported that is
  627. BBB or BOT (Bulk Only Transport) and UAS (USB Attached SCSI). BOT is
  628. advertised on alternative interface 0 (primary) and UAS is on
  629. alternative interface 1. Both protocols can work on USB2.0 and USB3.0.
  630. UAS utilizes the USB 3.0 feature called streams support.
  631. config USB_G_SERIAL
  632. tristate "Serial Gadget (with CDC ACM and CDC OBEX support)"
  633. select USB_LIBCOMPOSITE
  634. help
  635. The Serial Gadget talks to the Linux-USB generic serial driver.
  636. This driver supports a CDC-ACM module option, which can be used
  637. to interoperate with MS-Windows hosts or with the Linux-USB
  638. "cdc-acm" driver.
  639. This driver also supports a CDC-OBEX option. You will need a
  640. user space OBEX server talking to /dev/ttyGS*, since the kernel
  641. itself doesn't implement the OBEX protocol.
  642. Say "y" to link the driver statically, or "m" to build a
  643. dynamically linked module called "g_serial".
  644. For more information, see Documentation/usb/gadget_serial.txt
  645. which includes instructions and a "driver info file" needed to
  646. make MS-Windows work with CDC ACM.
  647. config USB_MIDI_GADGET
  648. tristate "MIDI Gadget"
  649. depends on SND
  650. select USB_LIBCOMPOSITE
  651. select SND_RAWMIDI
  652. help
  653. The MIDI Gadget acts as a USB Audio device, with one MIDI
  654. input and one MIDI output. These MIDI jacks appear as
  655. a sound "card" in the ALSA sound system. Other MIDI
  656. connections can then be made on the gadget system, using
  657. ALSA's aconnect utility etc.
  658. Say "y" to link the driver statically, or "m" to build a
  659. dynamically linked module called "g_midi".
  660. config USB_G_PRINTER
  661. tristate "Printer Gadget"
  662. select USB_LIBCOMPOSITE
  663. help
  664. The Printer Gadget channels data between the USB host and a
  665. userspace program driving the print engine. The user space
  666. program reads and writes the device file /dev/g_printer to
  667. receive or send printer data. It can use ioctl calls to
  668. the device file to get or set printer status.
  669. Say "y" to link the driver statically, or "m" to build a
  670. dynamically linked module called "g_printer".
  671. For more information, see Documentation/usb/gadget_printer.txt
  672. which includes sample code for accessing the device file.
  673. config USB_CDC_COMPOSITE
  674. tristate "CDC Composite Device (Ethernet and ACM)"
  675. depends on NET
  676. select USB_LIBCOMPOSITE
  677. help
  678. This driver provides two functions in one configuration:
  679. a CDC Ethernet (ECM) link, and a CDC ACM (serial port) link.
  680. This driver requires four bulk and two interrupt endpoints,
  681. plus the ability to handle altsettings. Not all peripheral
  682. controllers are that capable.
  683. Say "y" to link the driver statically, or "m" to build a
  684. dynamically linked module.
  685. config USB_G_NOKIA
  686. tristate "Nokia composite gadget"
  687. depends on PHONET
  688. select USB_LIBCOMPOSITE
  689. help
  690. The Nokia composite gadget provides support for acm, obex
  691. and phonet in only one composite gadget driver.
  692. It's only really useful for N900 hardware. If you're building
  693. a kernel for N900, say Y or M here. If unsure, say N.
  694. config USB_G_ACM_MS
  695. tristate "CDC Composite Device (ACM and mass storage)"
  696. depends on BLOCK
  697. select USB_LIBCOMPOSITE
  698. help
  699. This driver provides two functions in one configuration:
  700. a mass storage, and a CDC ACM (serial port) link.
  701. Say "y" to link the driver statically, or "m" to build a
  702. dynamically linked module called "g_acm_ms".
  703. config USB_G_MULTI
  704. tristate "Multifunction Composite Gadget"
  705. depends on BLOCK && NET
  706. select USB_G_MULTI_CDC if !USB_G_MULTI_RNDIS
  707. select USB_LIBCOMPOSITE
  708. help
  709. The Multifunction Composite Gadget provides Ethernet (RNDIS
  710. and/or CDC Ethernet), mass storage and ACM serial link
  711. interfaces.
  712. You will be asked to choose which of the two configurations is
  713. to be available in the gadget. At least one configuration must
  714. be chosen to make the gadget usable. Selecting more than one
  715. configuration will prevent Windows from automatically detecting
  716. the gadget as a composite gadget, so an INF file will be needed to
  717. use the gadget.
  718. Say "y" to link the driver statically, or "m" to build a
  719. dynamically linked module called "g_multi".
  720. config USB_G_MULTI_RNDIS
  721. bool "RNDIS + CDC Serial + Storage configuration"
  722. depends on USB_G_MULTI
  723. default y
  724. help
  725. This option enables a configuration with RNDIS, CDC Serial and
  726. Mass Storage functions available in the Multifunction Composite
  727. Gadget. This is the configuration dedicated for Windows since RNDIS
  728. is Microsoft's protocol.
  729. If unsure, say "y".
  730. config USB_G_MULTI_CDC
  731. bool "CDC Ethernet + CDC Serial + Storage configuration"
  732. depends on USB_G_MULTI
  733. default n
  734. help
  735. This option enables a configuration with CDC Ethernet (ECM), CDC
  736. Serial and Mass Storage functions available in the Multifunction
  737. Composite Gadget.
  738. If unsure, say "y".
  739. config USB_G_HID
  740. tristate "HID Gadget"
  741. select USB_LIBCOMPOSITE
  742. help
  743. The HID gadget driver provides generic emulation of USB
  744. Human Interface Devices (HID).
  745. For more information, see Documentation/usb/gadget_hid.txt which
  746. includes sample code for accessing the device files.
  747. Say "y" to link the driver statically, or "m" to build a
  748. dynamically linked module called "g_hid".
  749. # Standalone / single function gadgets
  750. config USB_G_DBGP
  751. tristate "EHCI Debug Device Gadget"
  752. select USB_LIBCOMPOSITE
  753. help
  754. This gadget emulates an EHCI Debug device. This is useful when you want
  755. to interact with an EHCI Debug Port.
  756. Say "y" to link the driver statically, or "m" to build a
  757. dynamically linked module called "g_dbgp".
  758. if USB_G_DBGP
  759. choice
  760. prompt "EHCI Debug Device mode"
  761. default USB_G_DBGP_SERIAL
  762. config USB_G_DBGP_PRINTK
  763. depends on USB_G_DBGP
  764. bool "printk"
  765. help
  766. Directly printk() received data. No interaction.
  767. config USB_G_DBGP_SERIAL
  768. depends on USB_G_DBGP
  769. bool "serial"
  770. help
  771. Userland can interact using /dev/ttyGSxxx.
  772. endchoice
  773. endif
  774. # put drivers that need isochronous transfer support (for audio
  775. # or video class gadget drivers), or specific hardware, here.
  776. config USB_G_WEBCAM
  777. tristate "USB Webcam Gadget"
  778. depends on VIDEO_DEV
  779. select USB_LIBCOMPOSITE
  780. help
  781. The Webcam Gadget acts as a composite USB Audio and Video Class
  782. device. It provides a userspace API to process UVC control requests
  783. and stream video data to the host.
  784. Say "y" to link the driver statically, or "m" to build a
  785. dynamically linked module called "g_webcam".
  786. endchoice
  787. endif # USB_GADGET