Kconfig 24 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662663664665666667668669670671672673674675676677678679680681682683684685686687688689690691692693694695696697698699700701702703704705706707708709710711712713714715716717718719720721722723
  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
  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
  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
  138. select USB_GADGET_DUALSPEED
  139. help
  140. Some of Freescale PowerPC processors have a High Speed
  141. Dual-Role(DR) USB controller, which supports device mode.
  142. The number of programmable endpoints is different through
  143. SOC revisions.
  144. Say "y" to link the driver statically, or "m" to build a
  145. dynamically linked module called "fsl_usb2_udc" and force
  146. all gadget drivers to also be dynamically linked.
  147. config USB_FSL_USB2
  148. tristate
  149. depends on USB_GADGET_FSL_USB2
  150. default USB_GADGET
  151. select USB_GADGET_SELECTED
  152. config USB_GADGET_LH7A40X
  153. boolean "LH7A40X"
  154. depends on ARCH_LH7A40X
  155. help
  156. This driver provides USB Device Controller driver for LH7A40x
  157. config USB_LH7A40X
  158. tristate
  159. depends on USB_GADGET_LH7A40X
  160. default USB_GADGET
  161. select USB_GADGET_SELECTED
  162. config USB_GADGET_OMAP
  163. boolean "OMAP USB Device Controller"
  164. depends on ARCH_OMAP
  165. select ISP1301_OMAP if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_H4_OTG
  166. select USB_OTG_UTILS if ARCH_OMAP
  167. help
  168. Many Texas Instruments OMAP processors have flexible full
  169. speed USB device controllers, with support for up to 30
  170. endpoints (plus endpoint zero). This driver supports the
  171. controller in the OMAP 1611, and should work with controllers
  172. in other OMAP processors too, given minor tweaks.
  173. Say "y" to link the driver statically, or "m" to build a
  174. dynamically linked module called "omap_udc" and force all
  175. gadget drivers to also be dynamically linked.
  176. config USB_OMAP
  177. tristate
  178. depends on USB_GADGET_OMAP
  179. default USB_GADGET
  180. select USB_GADGET_SELECTED
  181. config USB_OTG
  182. boolean "OTG Support"
  183. depends on USB_GADGET_OMAP && ARCH_OMAP_OTG && USB_OHCI_HCD
  184. help
  185. The most notable feature of USB OTG is support for a
  186. "Dual-Role" device, which can act as either a device
  187. or a host. The initial role choice can be changed
  188. later, when two dual-role devices talk to each other.
  189. Select this only if your OMAP board has a Mini-AB connector.
  190. config USB_GADGET_PXA25X
  191. boolean "PXA 25x or IXP 4xx"
  192. depends on (ARCH_PXA && PXA25x) || ARCH_IXP4XX
  193. help
  194. Intel's PXA 25x series XScale ARM-5TE processors include
  195. an integrated full speed USB 1.1 device controller. The
  196. controller in the IXP 4xx series is register-compatible.
  197. It has fifteen fixed-function endpoints, as well as endpoint
  198. zero (for control transfers).
  199. Say "y" to link the driver statically, or "m" to build a
  200. dynamically linked module called "pxa25x_udc" and force all
  201. gadget drivers to also be dynamically linked.
  202. config USB_PXA25X
  203. tristate
  204. depends on USB_GADGET_PXA25X
  205. default USB_GADGET
  206. select USB_GADGET_SELECTED
  207. # if there's only one gadget driver, using only two bulk endpoints,
  208. # don't waste memory for the other endpoints
  209. config USB_PXA25X_SMALL
  210. depends on USB_GADGET_PXA25X
  211. bool
  212. default n if USB_ETH_RNDIS
  213. default y if USB_ZERO
  214. default y if USB_ETH
  215. default y if USB_G_SERIAL
  216. config USB_GADGET_PXA27X
  217. boolean "PXA 27x"
  218. depends on ARCH_PXA && PXA27x
  219. help
  220. Intel's PXA 27x series XScale ARM v5TE processors include
  221. an integrated full speed USB 1.1 device controller.
  222. It has up to 23 endpoints, as well as endpoint zero (for
  223. control transfers).
  224. Say "y" to link the driver statically, or "m" to build a
  225. dynamically linked module called "pxa27x_udc" and force all
  226. gadget drivers to also be dynamically linked.
  227. config USB_PXA27X
  228. tristate
  229. depends on USB_GADGET_PXA27X
  230. default USB_GADGET
  231. select USB_GADGET_SELECTED
  232. config USB_GADGET_S3C2410
  233. boolean "S3C2410 USB Device Controller"
  234. depends on ARCH_S3C2410
  235. help
  236. Samsung's S3C2410 is an ARM-4 processor with an integrated
  237. full speed USB 1.1 device controller. It has 4 configurable
  238. endpoints, as well as endpoint zero (for control transfers).
  239. This driver has been tested on the S3C2410, S3C2412, and
  240. S3C2440 processors.
  241. config USB_S3C2410
  242. tristate
  243. depends on USB_GADGET_S3C2410
  244. default USB_GADGET
  245. select USB_GADGET_SELECTED
  246. config USB_S3C2410_DEBUG
  247. boolean "S3C2410 udc debug messages"
  248. depends on USB_GADGET_S3C2410
  249. #
  250. # Controllers available in both integrated and discrete versions
  251. #
  252. # musb builds in ../musb along with host support
  253. config USB_GADGET_MUSB_HDRC
  254. boolean "Inventra HDRC USB Peripheral (TI, ADI, ...)"
  255. depends on USB_MUSB_HDRC && (USB_MUSB_PERIPHERAL || USB_MUSB_OTG)
  256. select USB_GADGET_DUALSPEED
  257. select USB_GADGET_SELECTED
  258. help
  259. This OTG-capable silicon IP is used in dual designs including
  260. the TI DaVinci, OMAP 243x, OMAP 343x, TUSB 6010, and ADI Blackfin
  261. config USB_GADGET_IMX
  262. boolean "Freescale IMX USB Peripheral Controller"
  263. depends on ARCH_MX1
  264. help
  265. Freescale's IMX series include an integrated full speed
  266. USB 1.1 device controller. The controller in the IMX series
  267. is register-compatible.
  268. It has Six fixed-function endpoints, as well as endpoint
  269. zero (for control transfers).
  270. Say "y" to link the driver statically, or "m" to build a
  271. dynamically linked module called "imx_udc" and force all
  272. gadget drivers to also be dynamically linked.
  273. config USB_IMX
  274. tristate
  275. depends on USB_GADGET_IMX
  276. default USB_GADGET
  277. select USB_GADGET_SELECTED
  278. config USB_GADGET_M66592
  279. boolean "Renesas M66592 USB Peripheral Controller"
  280. select USB_GADGET_DUALSPEED
  281. help
  282. M66592 is a discrete USB peripheral controller chip that
  283. supports both full and high speed USB 2.0 data transfers.
  284. It has seven configurable endpoints, and endpoint zero.
  285. Say "y" to link the driver statically, or "m" to build a
  286. dynamically linked module called "m66592_udc" and force all
  287. gadget drivers to also be dynamically linked.
  288. config USB_M66592
  289. tristate
  290. depends on USB_GADGET_M66592
  291. default USB_GADGET
  292. select USB_GADGET_SELECTED
  293. config SUPERH_BUILT_IN_M66592
  294. boolean "Enable SuperH built-in USB like the M66592"
  295. depends on USB_GADGET_M66592 && CPU_SUBTYPE_SH7722
  296. help
  297. SH7722 has USB like the M66592.
  298. The transfer rate is very slow when use "Ethernet Gadget".
  299. However, this problem is improved if change a value of
  300. NET_IP_ALIGN to 4.
  301. #
  302. # Controllers available only in discrete form (and all PCI controllers)
  303. #
  304. config USB_GADGET_AMD5536UDC
  305. boolean "AMD5536 UDC"
  306. depends on PCI
  307. select USB_GADGET_DUALSPEED
  308. help
  309. The AMD5536 UDC is part of the AMD Geode CS5536, an x86 southbridge.
  310. It is a USB Highspeed DMA capable USB device controller. Beside ep0
  311. it provides 4 IN and 4 OUT endpoints (bulk or interrupt type).
  312. The UDC port supports OTG operation, and may be used as a host port
  313. if it's not being used to implement peripheral or OTG roles.
  314. Say "y" to link the driver statically, or "m" to build a
  315. dynamically linked module called "amd5536udc" and force all
  316. gadget drivers to also be dynamically linked.
  317. config USB_AMD5536UDC
  318. tristate
  319. depends on USB_GADGET_AMD5536UDC
  320. default USB_GADGET
  321. select USB_GADGET_SELECTED
  322. config USB_GADGET_FSL_QE
  323. boolean "Freescale QE/CPM USB Device Controller"
  324. depends on FSL_SOC && (QUICC_ENGINE || CPM)
  325. help
  326. Some of Freescale PowerPC processors have a Full Speed
  327. QE/CPM2 USB controller, which support device mode with 4
  328. programmable endpoints. This driver supports the
  329. controller in the MPC8360 and MPC8272, and should work with
  330. controllers having QE or CPM2, given minor tweaks.
  331. Set CONFIG_USB_GADGET to "m" to build this driver as a
  332. dynmically linked module called "fsl_qe_udc".
  333. config USB_FSL_QE
  334. tristate
  335. depends on USB_GADGET_FSL_QE
  336. default USB_GADGET
  337. select USB_GADGET_SELECTED
  338. config USB_GADGET_CI13XXX
  339. boolean "MIPS USB CI13xxx"
  340. depends on PCI
  341. select USB_GADGET_DUALSPEED
  342. help
  343. MIPS USB IP core family device controller
  344. Currently it only supports IP part number CI13412
  345. Say "y" to link the driver statically, or "m" to build a
  346. dynamically linked module called "ci13xxx_udc" and force all
  347. gadget drivers to also be dynamically linked.
  348. config USB_CI13XXX
  349. tristate
  350. depends on USB_GADGET_CI13XXX
  351. default USB_GADGET
  352. select USB_GADGET_SELECTED
  353. config USB_GADGET_NET2280
  354. boolean "NetChip 228x"
  355. depends on PCI
  356. select USB_GADGET_DUALSPEED
  357. help
  358. NetChip 2280 / 2282 is a PCI based USB peripheral controller which
  359. supports both full and high speed USB 2.0 data transfers.
  360. It has six configurable endpoints, as well as endpoint zero
  361. (for control transfers) and several endpoints with dedicated
  362. functions.
  363. Say "y" to link the driver statically, or "m" to build a
  364. dynamically linked module called "net2280" and force all
  365. gadget drivers to also be dynamically linked.
  366. config USB_NET2280
  367. tristate
  368. depends on USB_GADGET_NET2280
  369. default USB_GADGET
  370. select USB_GADGET_SELECTED
  371. config USB_GADGET_GOKU
  372. boolean "Toshiba TC86C001 'Goku-S'"
  373. depends on PCI
  374. help
  375. The Toshiba TC86C001 is a PCI device which includes controllers
  376. for full speed USB devices, IDE, I2C, SIO, plus a USB host (OHCI).
  377. The device controller has three configurable (bulk or interrupt)
  378. endpoints, plus endpoint zero (for control transfers).
  379. Say "y" to link the driver statically, or "m" to build a
  380. dynamically linked module called "goku_udc" and to force all
  381. gadget drivers to also be dynamically linked.
  382. config USB_GOKU
  383. tristate
  384. depends on USB_GADGET_GOKU
  385. default USB_GADGET
  386. select USB_GADGET_SELECTED
  387. #
  388. # LAST -- dummy/emulated controller
  389. #
  390. config USB_GADGET_DUMMY_HCD
  391. boolean "Dummy HCD (DEVELOPMENT)"
  392. depends on USB=y || (USB=m && USB_GADGET=m)
  393. select USB_GADGET_DUALSPEED
  394. help
  395. This host controller driver emulates USB, looping all data transfer
  396. requests back to a USB "gadget driver" in the same host. The host
  397. side is the master; the gadget side is the slave. Gadget drivers
  398. can be high, full, or low speed; and they have access to endpoints
  399. like those from NET2280, PXA2xx, or SA1100 hardware.
  400. This may help in some stages of creating a driver to embed in a
  401. Linux device, since it lets you debug several parts of the gadget
  402. driver without its hardware or drivers being involved.
  403. Since such a gadget side driver needs to interoperate with a host
  404. side Linux-USB device driver, this may help to debug both sides
  405. of a USB protocol stack.
  406. Say "y" to link the driver statically, or "m" to build a
  407. dynamically linked module called "dummy_hcd" and force all
  408. gadget drivers to also be dynamically linked.
  409. config USB_DUMMY_HCD
  410. tristate
  411. depends on USB_GADGET_DUMMY_HCD
  412. default USB_GADGET
  413. select USB_GADGET_SELECTED
  414. # NOTE: Please keep dummy_hcd LAST so that "real hardware" appears
  415. # first and will be selected by default.
  416. endchoice
  417. config USB_GADGET_DUALSPEED
  418. bool
  419. depends on USB_GADGET
  420. default n
  421. help
  422. Means that gadget drivers should include extra descriptors
  423. and code to handle dual-speed controllers.
  424. #
  425. # USB Gadget Drivers
  426. #
  427. choice
  428. tristate "USB Gadget Drivers"
  429. depends on USB_GADGET && USB_GADGET_SELECTED
  430. default USB_ETH
  431. help
  432. A Linux "Gadget Driver" talks to the USB Peripheral Controller
  433. driver through the abstract "gadget" API. Some other operating
  434. systems call these "client" drivers, of which "class drivers"
  435. are a subset (implementing a USB device class specification).
  436. A gadget driver implements one or more USB functions using
  437. the peripheral hardware.
  438. Gadget drivers are hardware-neutral, or "platform independent",
  439. except that they sometimes must understand quirks or limitations
  440. of the particular controllers they work with. For example, when
  441. a controller doesn't support alternate configurations or provide
  442. enough of the right types of endpoints, the gadget driver might
  443. not be able work with that controller, or might need to implement
  444. a less common variant of a device class protocol.
  445. # this first set of drivers all depend on bulk-capable hardware.
  446. config USB_ZERO
  447. tristate "Gadget Zero (DEVELOPMENT)"
  448. help
  449. Gadget Zero is a two-configuration device. It either sinks and
  450. sources bulk data; or it loops back a configurable number of
  451. transfers. It also implements control requests, for "chapter 9"
  452. conformance. The driver needs only two bulk-capable endpoints, so
  453. it can work on top of most device-side usb controllers. It's
  454. useful for testing, and is also a working example showing how
  455. USB "gadget drivers" can be written.
  456. Make this be the first driver you try using on top of any new
  457. USB peripheral controller driver. Then you can use host-side
  458. test software, like the "usbtest" driver, to put your hardware
  459. and its driver through a basic set of functional tests.
  460. Gadget Zero also works with the host-side "usb-skeleton" driver,
  461. and with many kinds of host-side test software. You may need
  462. to tweak product and vendor IDs before host software knows about
  463. this device, and arrange to select an appropriate configuration.
  464. Say "y" to link the driver statically, or "m" to build a
  465. dynamically linked module called "g_zero".
  466. config USB_ZERO_HNPTEST
  467. boolean "HNP Test Device"
  468. depends on USB_ZERO && USB_OTG
  469. help
  470. You can configure this device to enumerate using the device
  471. identifiers of the USB-OTG test device. That means that when
  472. this gadget connects to another OTG device, with this one using
  473. the "B-Peripheral" role, that device will use HNP to let this
  474. one serve as the USB host instead (in the "B-Host" role).
  475. config USB_ETH
  476. tristate "Ethernet Gadget (with CDC Ethernet support)"
  477. depends on NET
  478. help
  479. This driver implements Ethernet style communication, in either
  480. of two ways:
  481. - The "Communication Device Class" (CDC) Ethernet Control Model.
  482. That protocol is often avoided with pure Ethernet adapters, in
  483. favor of simpler vendor-specific hardware, but is widely
  484. supported by firmware for smart network devices.
  485. - On hardware can't implement that protocol, a simple CDC subset
  486. is used, placing fewer demands on USB.
  487. RNDIS support is a third option, more demanding than that subset.
  488. Within the USB device, this gadget driver exposes a network device
  489. "usbX", where X depends on what other networking devices you have.
  490. Treat it like a two-node Ethernet link: host, and gadget.
  491. The Linux-USB host-side "usbnet" driver interoperates with this
  492. driver, so that deep I/O queues can be supported. On 2.4 kernels,
  493. use "CDCEther" instead, if you're using the CDC option. That CDC
  494. mode should also interoperate with standard CDC Ethernet class
  495. drivers on other host operating systems.
  496. Say "y" to link the driver statically, or "m" to build a
  497. dynamically linked module called "g_ether".
  498. config USB_ETH_RNDIS
  499. bool "RNDIS support"
  500. depends on USB_ETH
  501. default y
  502. help
  503. Microsoft Windows XP bundles the "Remote NDIS" (RNDIS) protocol,
  504. and Microsoft provides redistributable binary RNDIS drivers for
  505. older versions of Windows.
  506. If you say "y" here, the Ethernet gadget driver will try to provide
  507. a second device configuration, supporting RNDIS to talk to such
  508. Microsoft USB hosts.
  509. To make MS-Windows work with this, use Documentation/usb/linux.inf
  510. as the "driver info file". For versions of MS-Windows older than
  511. XP, you'll need to download drivers from Microsoft's website; a URL
  512. is given in comments found in that info file.
  513. config USB_GADGETFS
  514. tristate "Gadget Filesystem (EXPERIMENTAL)"
  515. depends on EXPERIMENTAL
  516. help
  517. This driver provides a filesystem based API that lets user mode
  518. programs implement a single-configuration USB device, including
  519. endpoint I/O and control requests that don't relate to enumeration.
  520. All endpoints, transfer speeds, and transfer types supported by
  521. the hardware are available, through read() and write() calls.
  522. Currently, this option is still labelled as EXPERIMENTAL because
  523. of existing race conditions in the underlying in-kernel AIO core.
  524. Say "y" to link the driver statically, or "m" to build a
  525. dynamically linked module called "gadgetfs".
  526. config USB_FILE_STORAGE
  527. tristate "File-backed Storage Gadget"
  528. depends on BLOCK
  529. help
  530. The File-backed Storage Gadget acts as a USB Mass Storage
  531. disk drive. As its storage repository it can use a regular
  532. file or a block device (in much the same way as the "loop"
  533. device driver), specified as a module parameter.
  534. Say "y" to link the driver statically, or "m" to build a
  535. dynamically linked module called "g_file_storage".
  536. config USB_FILE_STORAGE_TEST
  537. bool "File-backed Storage Gadget testing version"
  538. depends on USB_FILE_STORAGE
  539. default n
  540. help
  541. Say "y" to generate the larger testing version of the
  542. File-backed Storage Gadget, useful for probing the
  543. behavior of USB Mass Storage hosts. Not needed for
  544. normal operation.
  545. config USB_G_SERIAL
  546. tristate "Serial Gadget (with CDC ACM and CDC OBEX support)"
  547. help
  548. The Serial Gadget talks to the Linux-USB generic serial driver.
  549. This driver supports a CDC-ACM module option, which can be used
  550. to interoperate with MS-Windows hosts or with the Linux-USB
  551. "cdc-acm" driver.
  552. This driver also supports a CDC-OBEX option. You will need a
  553. user space OBEX server talking to /dev/ttyGS*, since the kernel
  554. itself doesn't implement the OBEX protocol.
  555. Say "y" to link the driver statically, or "m" to build a
  556. dynamically linked module called "g_serial".
  557. For more information, see Documentation/usb/gadget_serial.txt
  558. which includes instructions and a "driver info file" needed to
  559. make MS-Windows work with CDC ACM.
  560. config USB_MIDI_GADGET
  561. tristate "MIDI Gadget (EXPERIMENTAL)"
  562. depends on SND && EXPERIMENTAL
  563. select SND_RAWMIDI
  564. help
  565. The MIDI Gadget acts as a USB Audio device, with one MIDI
  566. input and one MIDI output. These MIDI jacks appear as
  567. a sound "card" in the ALSA sound system. Other MIDI
  568. connections can then be made on the gadget system, using
  569. ALSA's aconnect utility etc.
  570. Say "y" to link the driver statically, or "m" to build a
  571. dynamically linked module called "g_midi".
  572. config USB_G_PRINTER
  573. tristate "Printer Gadget"
  574. help
  575. The Printer Gadget channels data between the USB host and a
  576. userspace program driving the print engine. The user space
  577. program reads and writes the device file /dev/g_printer to
  578. receive or send printer data. It can use ioctl calls to
  579. the device file to get or set printer status.
  580. Say "y" to link the driver statically, or "m" to build a
  581. dynamically linked module called "g_printer".
  582. For more information, see Documentation/usb/gadget_printer.txt
  583. which includes sample code for accessing the device file.
  584. config USB_CDC_COMPOSITE
  585. tristate "CDC Composite Device (Ethernet and ACM)"
  586. depends on NET
  587. help
  588. This driver provides two functions in one configuration:
  589. a CDC Ethernet (ECM) link, and a CDC ACM (serial port) link.
  590. This driver requires four bulk and two interrupt endpoints,
  591. plus the ability to handle altsettings. Not all peripheral
  592. controllers are that capable.
  593. Say "y" to link the driver statically, or "m" to build a
  594. dynamically linked module.
  595. # put drivers that need isochronous transfer support (for audio
  596. # or video class gadget drivers), or specific hardware, here.
  597. # - none yet
  598. endchoice
  599. endif # USB_GADGET