Kconfig 34 KB

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