Kconfig 35 KB

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