Kconfig 34 KB

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