Kconfig 34.0 KB
Newer Older
L
Linus Torvalds 已提交
1 2 3 4 5 6 7 8 9
#
# USB Gadget support on a system involves
#    (a) a peripheral controller, and
#    (b) the gadget driver using it.
#
# NOTE:  Gadget support ** DOES NOT ** depend on host-side CONFIG_USB !!
#
#  - Host systems (like PCs) need CONFIG_USB (with "A" jacks).
#  - Peripherals (like PDAs) need CONFIG_USB_GADGET (with "B" jacks).
M
Matt LaPlante 已提交
10
#  - Some systems have both kinds of controllers.
L
Linus Torvalds 已提交
11 12 13 14 15
#
# With help from a special transceiver and a "Mini-AB" jack, systems with
# both kinds of controller can also support "USB On-the-Go" (CONFIG_USB_OTG).
#

D
Denis Cheng 已提交
16 17
menuconfig USB_GADGET
	tristate "USB Gadget Support"
18
	select NLS
L
Linus Torvalds 已提交
19 20 21 22 23 24 25 26 27 28
	help
	   USB is a master/slave protocol, organized with one master
	   host (such as a PC) controlling up to 127 peripheral devices.
	   The USB hardware is asymmetric, which makes it easier to set up:
	   you can't connect a "to-the-host" connector to a peripheral.

	   Linux can run in the host, or in the peripheral.  In both cases
	   you need a low level bus controller driver, and some software
	   talking to it.  Peripheral controllers are often discrete silicon,
	   or are integrated with the CPU in a microcontroller.  The more
29
	   familiar host side controllers have names like "EHCI", "OHCI",
L
Linus Torvalds 已提交
30 31 32 33 34 35 36 37 38 39 40 41 42 43 44
	   or "UHCI", and are usually integrated into southbridges on PC
	   motherboards.

	   Enable this configuration option if you want to run Linux inside
	   a USB peripheral device.  Configure one hardware driver for your
	   peripheral/device side bus controller, and a "gadget driver" for
	   your peripheral protocol.  (If you use modular gadget drivers,
	   you may configure more than one.)

	   If in doubt, say "N" and don't enable these drivers; most people
	   don't have this kind of hardware (except maybe inside Linux PDAs).

	   For more information, see <http://www.linux-usb.org/gadget> and
	   the kernel DocBook documentation for this API.

D
Denis Cheng 已提交
45 46
if USB_GADGET

47
config USB_GADGET_DEBUG
48
	boolean "Debugging messages (DEVELOPMENT)"
49
	depends on DEBUG_KERNEL
50 51 52 53 54 55 56 57 58 59 60
	help
	   Many controller and gadget drivers will print some debugging
	   messages if you use this option to ask for those messages.

	   Avoid enabling these messages, even if you're actively
	   debugging such a driver.  Many drivers will emit so many
	   messages that the driver timings are affected, which will
	   either create new failure modes or remove the one you're
	   trying to track down.  Never enable these messages for a
	   production build.

L
Linus Torvalds 已提交
61
config USB_GADGET_DEBUG_FILES
62
	boolean "Debugging information files (DEVELOPMENT)"
63
	depends on PROC_FS
L
Linus Torvalds 已提交
64 65 66 67 68 69 70 71
	help
	   Some of the drivers in the "gadget" framework can expose
	   debugging information in files such as /proc/driver/udc
	   (for a peripheral controller).  The information in these
	   files may help when you're troubleshooting or bringing up a
	   driver on a new board.   Enable these files by choosing "Y"
	   here.  If in doubt, or to conserve kernel memory, say "N".

72
config USB_GADGET_DEBUG_FS
73
	boolean "Debugging information files in debugfs (DEVELOPMENT)"
74
	depends on DEBUG_FS
75 76 77 78 79 80 81 82
	help
	   Some of the drivers in the "gadget" framework can expose
	   debugging information in files under /sys/kernel/debug/.
	   The information in these files may help when you're
	   troubleshooting or bringing up a driver on a new board.
	   Enable these files by choosing "Y" here.  If in doubt, or
	   to conserve kernel memory, say "N".

83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
config USB_GADGET_VBUS_DRAW
	int "Maximum VBUS Power usage (2-500 mA)"
	range 2 500
	default 2
	help
	   Some devices need to draw power from USB when they are
	   configured, perhaps to operate circuitry or to recharge
	   batteries.  This is in addition to any local power supply,
	   such as an AC adapter or batteries.

	   Enter the maximum power your device draws through USB, in
	   milliAmperes.  The permitted range of values is 2 - 500 mA;
	   0 mA would be legal, but can make some hosts misbehave.

	   This value will be used except for system-specific gadget
	   drivers that have more specific information.

100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115
config USB_GADGET_STORAGE_NUM_BUFFERS
	int "Number of storage pipeline buffers"
	range 2 4
	default 2
	help
	   Usually 2 buffers are enough to establish a good buffering
	   pipeline. The number may be increased in order to compensate
	   for a bursty VFS behaviour. For instance there may be CPU wake up
	   latencies that makes the VFS to appear bursty in a system with
	   an CPU on-demand governor. Especially if DMA is doing IO to
	   offload the CPU. In this case the CPU will go into power
	   save often and spin up occasionally to move data within VFS.
	   If selecting USB_GADGET_DEBUG_FILES this value may be set by
	   a module parameter as well.
	   If unsure, say 2.

L
Linus Torvalds 已提交
116 117 118
#
# USB Peripheral Controller Support
#
D
David Brownell 已提交
119 120 121 122 123 124 125
# The order here is alphabetical, except that integrated controllers go
# before discrete ones so they will be the initial/default value:
#   - integrated/SOC controllers first
#   - licensed IP used in both SOC and discrete versions
#   - discrete ones (including all PCI-only controllers)
#   - debug/dummy gadget+hcd is last.
#
126
menu "USB Peripheral Controller"
L
Linus Torvalds 已提交
127

D
David Brownell 已提交
128 129 130 131
#
# Integrated controllers
#

132 133
config USB_AT91
	tristate "Atmel AT91 USB Device Port"
134
	depends on ARCH_AT91
135
	help
D
David Brownell 已提交
136 137 138
	   Many Atmel AT91 processors (such as the AT91RM2000) have a
	   full speed USB Device Port with support for five configurable
	   endpoints (plus endpoint zero).
139 140

	   Say "y" to link the driver statically, or "m" to build a
D
David Brownell 已提交
141
	   dynamically linked module called "at91_udc" and force all
142 143
	   gadget drivers to also be dynamically linked.

R
Roland Stigge 已提交
144 145 146 147 148 149 150 151 152 153 154
config USB_LPC32XX
	tristate "LPC32XX USB Peripheral Controller"
	depends on ARCH_LPC32XX
	select USB_ISP1301
	help
	   This option selects the USB device controller in the LPC32xx SoC.

	   Say "y" to link the driver statically, or "m" to build a
	   dynamically linked module called "lpc32xx_udc" and force all
	   gadget drivers to also be dynamically linked.

155 156
config USB_ATMEL_USBA
	tristate "Atmel USBA"
157
	select USB_GADGET_DUALSPEED
158
	depends on AVR32 || ARCH_AT91SAM9RL || ARCH_AT91SAM9G45
159 160
	help
	  USBA is the integrated high-speed USB Device controller on
161
	  the AT32AP700x, some AT91SAM9 and AT91CAP9 processors from Atmel.
162

163 164
config USB_FSL_USB2
	tristate "Freescale Highspeed USB DR Peripheral Controller"
165
	depends on FSL_SOC || ARCH_MXC
166
	select USB_GADGET_DUALSPEED
167
	select USB_FSL_MPH_DR_OF if OF
168
	help
169
	   Some of Freescale PowerPC and i.MX processors have a High Speed
170 171 172 173 174 175 176 177 178
	   Dual-Role(DR) USB controller, which supports device mode.

	   The number of programmable endpoints is different through
	   SOC revisions.

	   Say "y" to link the driver statically, or "m" to build a
	   dynamically linked module called "fsl_usb2_udc" and force
	   all gadget drivers to also be dynamically linked.

179 180
config USB_FUSB300
	tristate "Faraday FUSB300 USB Peripheral Controller"
181
	depends on !PHYS_ADDR_T_64BIT
182 183 184 185
	select USB_GADGET_DUALSPEED
	help
	   Faraday usb device controller FUSB300 driver

186 187
config USB_OMAP
	tristate "OMAP USB Device Controller"
D
David Brownell 已提交
188
	depends on ARCH_OMAP
T
Tony Lindgren 已提交
189
	select ISP1301_OMAP if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_H4_OTG
190
	select USB_OTG_UTILS if ARCH_OMAP
D
David Brownell 已提交
191 192 193 194 195 196
	help
	   Many Texas Instruments OMAP processors have flexible full
	   speed USB device controllers, with support for up to 30
	   endpoints (plus endpoint zero).  This driver supports the
	   controller in the OMAP 1611, and should work with controllers
	   in other OMAP processors too, given minor tweaks.
L
Linus Torvalds 已提交
197 198

	   Say "y" to link the driver statically, or "m" to build a
D
David Brownell 已提交
199
	   dynamically linked module called "omap_udc" and force all
L
Linus Torvalds 已提交
200 201
	   gadget drivers to also be dynamically linked.

202 203
config USB_PXA25X
	tristate "PXA 25x or IXP 4xx"
L
Linus Torvalds 已提交
204
	depends on (ARCH_PXA && PXA25x) || ARCH_IXP4XX
R
Russell King 已提交
205
	select USB_OTG_UTILS
L
Linus Torvalds 已提交
206 207 208 209 210 211 212 213 214
	help
	   Intel's PXA 25x series XScale ARM-5TE processors include
	   an integrated full speed USB 1.1 device controller.  The
	   controller in the IXP 4xx series is register-compatible.

	   It has fifteen fixed-function endpoints, as well as endpoint
	   zero (for control transfers).

	   Say "y" to link the driver statically, or "m" to build a
215
	   dynamically linked module called "pxa25x_udc" and force all
L
Linus Torvalds 已提交
216 217 218 219
	   gadget drivers to also be dynamically linked.

# if there's only one gadget driver, using only two bulk endpoints,
# don't waste memory for the other endpoints
220
config USB_PXA25X_SMALL
221
	depends on USB_PXA25X
L
Linus Torvalds 已提交
222 223 224 225 226 227
	bool
	default n if USB_ETH_RNDIS
	default y if USB_ZERO
	default y if USB_ETH
	default y if USB_G_SERIAL

228 229
config USB_R8A66597
	tristate "Renesas R8A66597 USB Peripheral Controller"
230 231 232 233 234 235 236 237 238 239
	select USB_GADGET_DUALSPEED
	help
	   R8A66597 is a discrete USB host and peripheral controller chip that
	   supports both full and high speed USB 2.0 data transfers.
	   It has nine configurable endpoints, and endpoint zero.

	   Say "y" to link the driver statically, or "m" to build a
	   dynamically linked module called "r8a66597_udc" and force all
	   gadget drivers to also be dynamically linked.

240
config USB_RENESAS_USBHS_UDC
241
	tristate 'Renesas USBHS controller'
242 243
	depends on USB_RENESAS_USBHS
	select USB_GADGET_DUALSPEED
244
	help
245 246 247
	   Renesas USBHS is a discrete USB host and peripheral controller chip
	   that supports both full and high speed USB 2.0 data transfers.
	   It has nine or more configurable endpoints, and endpoint zero.
248

249 250 251
	   Say "y" to link the driver statically, or "m" to build a
	   dynamically linked module called "renesas_usbhs" and force all
	   gadget drivers to also be dynamically linked.
252

253 254
config USB_PXA27X
	tristate "PXA 27x"
255
	depends on ARCH_PXA && (PXA27x || PXA3xx)
256
	select USB_OTG_UTILS
R
Robert Jarzmik 已提交
257 258 259 260 261 262 263 264 265 266 267
	help
	   Intel's PXA 27x series XScale ARM v5TE processors include
	   an integrated full speed USB 1.1 device controller.

	   It has up to 23 endpoints, as well as endpoint zero (for
	   control transfers).

	   Say "y" to link the driver statically, or "m" to build a
	   dynamically linked module called "pxa27x_udc" and force all
	   gadget drivers to also be dynamically linked.

268 269
config USB_S3C_HSOTG
	tristate "S3C HS/OtG USB Device controller"
270
	depends on S3C_DEV_USB_HSOTG
271
	select USB_GADGET_DUALSPEED
272 273 274 275
	help
	  The Samsung S3C64XX USB2.0 high-speed gadget controller
	  integrated into the S3C64XX series SoC.

276
config USB_IMX
277 278
	tristate "Freescale i.MX1 USB Peripheral Controller"
	depends on ARCH_MXC
279
	help
280 281
	   Freescale's i.MX1 includes an integrated full speed
	   USB 1.1 device controller.
282 283 284 285 286 287 288 289

	   It has Six fixed-function endpoints, as well as endpoint
	   zero (for control transfers).

	   Say "y" to link the driver statically, or "m" to build a
	   dynamically linked module called "imx_udc" and force all
	   gadget drivers to also be dynamically linked.

290 291
config USB_S3C2410
	tristate "S3C2410 USB Device Controller"
292
	depends on ARCH_S3C24XX
L
Linus Torvalds 已提交
293
	help
D
David Brownell 已提交
294 295 296
	  Samsung's S3C2410 is an ARM-4 processor with an integrated
	  full speed USB 1.1 device controller.  It has 4 configurable
	  endpoints, as well as endpoint zero (for control transfers).
L
Linus Torvalds 已提交
297

D
David Brownell 已提交
298 299
	  This driver has been tested on the S3C2410, S3C2412, and
	  S3C2440 processors.
L
Linus Torvalds 已提交
300

D
David Brownell 已提交
301 302
config USB_S3C2410_DEBUG
	boolean "S3C2410 udc debug messages"
303
	depends on USB_S3C2410
L
Linus Torvalds 已提交
304

305 306
config USB_S3C_HSUDC
	tristate "S3C2416, S3C2443 and S3C2450 USB Device Controller"
307
	depends on ARCH_S3C24XX
308 309 310 311 312 313 314 315
	select USB_GADGET_DUALSPEED
	help
	  Samsung's S3C2416, S3C2443 and S3C2450 is an ARM9 based SoC
	  integrated with dual speed USB 2.0 device controller. It has
	  8 endpoints, as well as endpoint zero.

	  This driver has been tested on S3C2416 and S3C2450 processors.

316 317
config USB_MV_UDC
	tristate "Marvell USB2.0 Device Controller"
318 319
	select USB_GADGET_DUALSPEED
	help
320 321 322
	  Marvell Socs (including PXA and MMP series) include a high speed
	  USB2.0 OTG controller, which can be configured as high speed or
	  full speed USB peripheral.
323

D
David Brownell 已提交
324 325 326
#
# Controllers available in both integrated and discrete versions
#
L
Linus Torvalds 已提交
327

D
David Brownell 已提交
328
# musb builds in ../musb along with host support
F
Felipe Balbi 已提交
329
config USB_GADGET_MUSB_HDRC
330
	tristate "Inventra HDRC USB Peripheral (TI, ADI, ...)"
R
Rabin Vincent 已提交
331
	depends on USB_MUSB_HDRC
F
Felipe Balbi 已提交
332 333 334
	select USB_GADGET_DUALSPEED
	help
	  This OTG-capable silicon IP is used in dual designs including
335
	  the TI DaVinci, OMAP 243x, OMAP 343x, TUSB 6010, and ADI Blackfin
F
Felipe Balbi 已提交
336

337 338
config USB_M66592
	tristate "Renesas M66592 USB Peripheral Controller"
D
David Brownell 已提交
339
	select USB_GADGET_DUALSPEED
L
Linus Torvalds 已提交
340
	help
D
David Brownell 已提交
341 342 343
	   M66592 is a discrete USB peripheral controller chip that
	   supports both full and high speed USB 2.0 data transfers.
	   It has seven configurable endpoints, and endpoint zero.
L
Linus Torvalds 已提交
344 345

	   Say "y" to link the driver statically, or "m" to build a
D
David Brownell 已提交
346
	   dynamically linked module called "m66592_udc" and force all
L
Linus Torvalds 已提交
347 348
	   gadget drivers to also be dynamically linked.

D
David Brownell 已提交
349 350 351 352
#
# Controllers available only in discrete form (and all PCI controllers)
#

353 354
config USB_AMD5536UDC
	tristate "AMD5536 UDC"
D
David Brownell 已提交
355 356
	depends on PCI
	select USB_GADGET_DUALSPEED
357
	help
D
David Brownell 已提交
358 359 360 361 362
	   The AMD5536 UDC is part of the AMD Geode CS5536, an x86 southbridge.
	   It is a USB Highspeed DMA capable USB device controller. Beside ep0
	   it provides 4 IN and 4 OUT endpoints (bulk or interrupt type).
	   The UDC port supports OTG operation, and may be used as a host port
	   if it's not being used to implement peripheral or OTG roles.
363

D
David Brownell 已提交
364 365 366
	   Say "y" to link the driver statically, or "m" to build a
	   dynamically linked module called "amd5536udc" and force all
	   gadget drivers to also be dynamically linked.
367

368 369
config USB_FSL_QE
	tristate "Freescale QE/CPM USB Device Controller"
370 371 372 373 374 375 376 377 378
	depends on FSL_SOC && (QUICC_ENGINE || CPM)
	help
	   Some of Freescale PowerPC processors have a Full Speed
	   QE/CPM2 USB controller, which support device mode with 4
	   programmable endpoints. This driver supports the
	   controller in the MPC8360 and MPC8272, and should work with
	   controllers having QE or CPM2, given minor tweaks.

	   Set CONFIG_USB_GADGET to "m" to build this driver as a
379
	   dynamically linked module called "fsl_qe_udc".
380

381 382
config USB_NET2272
	tristate "PLX NET2272"
383 384 385 386 387 388 389 390 391 392 393
	select USB_GADGET_DUALSPEED
	help
	  PLX NET2272 is a USB peripheral controller which supports
	  both full and high speed USB 2.0 data transfers.

	  It has three configurable endpoints, as well as endpoint zero
	  (for control transfer).
	  Say "y" to link the driver statically, or "m" to build a
	  dynamically linked module called "net2272" and force all
	  gadget drivers to also be dynamically linked.

394
config USB_NET2272_DMA
395
	boolean "Support external DMA controller"
396
	depends on USB_NET2272
397 398 399 400 401 402 403
	help
	  The NET2272 part can optionally support an external DMA
	  controller, but your board has to have support in the
	  driver itself.

	  If unsure, say "N" here.  The driver works fine in PIO mode.

404 405
config USB_NET2280
	tristate "NetChip 228x"
D
David Brownell 已提交
406 407 408 409 410
	depends on PCI
	select USB_GADGET_DUALSPEED
	help
	   NetChip 2280 / 2282 is a PCI based USB peripheral controller which
	   supports both full and high speed USB 2.0 data transfers.
411

D
David Brownell 已提交
412 413 414 415 416 417 418 419
	   It has six configurable endpoints, as well as endpoint zero
	   (for control transfers) and several endpoints with dedicated
	   functions.

	   Say "y" to link the driver statically, or "m" to build a
	   dynamically linked module called "net2280" and force all
	   gadget drivers to also be dynamically linked.

420 421
config USB_GOKU
	tristate "Toshiba TC86C001 'Goku-S'"
D
David Brownell 已提交
422
	depends on PCI
423
	help
D
David Brownell 已提交
424 425 426 427 428
	   The Toshiba TC86C001 is a PCI device which includes controllers
	   for full speed USB devices, IDE, I2C, SIO, plus a USB host (OHCI).

	   The device controller has three configurable (bulk or interrupt)
	   endpoints, plus endpoint zero (for control transfers).
429 430

	   Say "y" to link the driver statically, or "m" to build a
D
David Brownell 已提交
431
	   dynamically linked module called "goku_udc" and to force all
432 433
	   gadget drivers to also be dynamically linked.

434
config USB_EG20T
435
	tristate "Intel EG20T PCH/LAPIS Semiconductor IOH(ML7213/ML7831) UDC"
436 437 438 439 440 441 442 443 444 445 446 447 448 449 450
	depends on PCI
	select USB_GADGET_DUALSPEED
	help
	  This is a USB device driver for EG20T PCH.
	  EG20T PCH is the platform controller hub that is used in Intel's
	  general embedded platform. EG20T PCH has USB device interface.
	  Using this interface, it is able to access system devices connected
	  to USB device.
	  This driver enables USB device function.
	  USB device is a USB peripheral controller which
	  supports both full and high speed USB 2.0 data transfers.
	  This driver supports both control transfer and bulk transfer modes.
	  This driver dose not support interrupt transfer or isochronous
	  transfer modes.

451
	  This driver also can be used for LAPIS Semiconductor's ML7213 which is
452
	  for IVI(In-Vehicle Infotainment) use.
453 454 455
	  ML7831 is for general purpose use.
	  ML7213/ML7831 is companion chip for Intel Atom E6xx series.
	  ML7213/ML7831 is completely compatible for Intel EG20T PCH.
456

D
David Brownell 已提交
457 458 459
#
# LAST -- dummy/emulated controller
#
L
Linus Torvalds 已提交
460

461 462
config USB_DUMMY_HCD
	tristate "Dummy HCD (DEVELOPMENT)"
463
	depends on USB=y || (USB=m && USB_GADGET=m)
L
Linus Torvalds 已提交
464
	select USB_GADGET_DUALSPEED
465
	select USB_GADGET_SUPERSPEED
L
Linus Torvalds 已提交
466 467 468 469 470 471
	help
	  This host controller driver emulates USB, looping all data transfer
	  requests back to a USB "gadget driver" in the same host.  The host
	  side is the master; the gadget side is the slave.  Gadget drivers
	  can be high, full, or low speed; and they have access to endpoints
	  like those from NET2280, PXA2xx, or SA1100 hardware.
472

L
Linus Torvalds 已提交
473 474 475
	  This may help in some stages of creating a driver to embed in a
	  Linux device, since it lets you debug several parts of the gadget
	  driver without its hardware or drivers being involved.
476

L
Linus Torvalds 已提交
477 478 479 480 481 482 483 484 485 486 487
	  Since such a gadget side driver needs to interoperate with a host
	  side Linux-USB device driver, this may help to debug both sides
	  of a USB protocol stack.

	  Say "y" to link the driver statically, or "m" to build a
	  dynamically linked module called "dummy_hcd" and force all
	  gadget drivers to also be dynamically linked.

# NOTE:  Please keep dummy_hcd LAST so that "real hardware" appears
# first and will be selected by default.

488
endmenu
L
Linus Torvalds 已提交
489

490
# Selected by UDC drivers that support high-speed operation.
L
Linus Torvalds 已提交
491 492 493
config USB_GADGET_DUALSPEED
	bool

494 495 496 497 498
# Selected by UDC drivers that support super-speed opperation
config USB_GADGET_SUPERSPEED
	bool
	depends on USB_GADGET_DUALSPEED

L
Linus Torvalds 已提交
499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556
#
# USB Gadget Drivers
#
choice
	tristate "USB Gadget Drivers"
	default USB_ETH
	help
	  A Linux "Gadget Driver" talks to the USB Peripheral Controller
	  driver through the abstract "gadget" API.  Some other operating
	  systems call these "client" drivers, of which "class drivers"
	  are a subset (implementing a USB device class specification).
	  A gadget driver implements one or more USB functions using
	  the peripheral hardware.

	  Gadget drivers are hardware-neutral, or "platform independent",
	  except that they sometimes must understand quirks or limitations
	  of the particular controllers they work with.  For example, when
	  a controller doesn't support alternate configurations or provide
	  enough of the right types of endpoints, the gadget driver might
	  not be able work with that controller, or might need to implement
	  a less common variant of a device class protocol.

# this first set of drivers all depend on bulk-capable hardware.

config USB_ZERO
	tristate "Gadget Zero (DEVELOPMENT)"
	help
	  Gadget Zero is a two-configuration device.  It either sinks and
	  sources bulk data; or it loops back a configurable number of
	  transfers.  It also implements control requests, for "chapter 9"
	  conformance.  The driver needs only two bulk-capable endpoints, so
	  it can work on top of most device-side usb controllers.  It's
	  useful for testing, and is also a working example showing how
	  USB "gadget drivers" can be written.

	  Make this be the first driver you try using on top of any new
	  USB peripheral controller driver.  Then you can use host-side
	  test software, like the "usbtest" driver, to put your hardware
	  and its driver through a basic set of functional tests.

	  Gadget Zero also works with the host-side "usb-skeleton" driver,
	  and with many kinds of host-side test software.  You may need
	  to tweak product and vendor IDs before host software knows about
	  this device, and arrange to select an appropriate configuration.

	  Say "y" to link the driver statically, or "m" to build a
	  dynamically linked module called "g_zero".

config USB_ZERO_HNPTEST
	boolean "HNP Test Device"
	depends on USB_ZERO && USB_OTG
	help
	  You can configure this device to enumerate using the device
	  identifiers of the USB-OTG test device.  That means that when
	  this gadget connects to another OTG device, with this one using
	  the "B-Peripheral" role, that device will use HNP to let this
	  one serve as the USB host instead (in the "B-Host" role).

557 558 559
config USB_AUDIO
	tristate "Audio Gadget (EXPERIMENTAL)"
	depends on SND
R
Randy Dunlap 已提交
560
	select SND_PCM
561
	help
562 563 564 565 566 567 568 569 570 571 572
	  This Gadget Audio driver is compatible with USB Audio Class
	  specification 2.0. It implements 1 AudioControl interface,
	  1 AudioStreaming Interface each for USB-OUT and USB-IN.
	  Number of channels, sample rate and sample size can be
	  specified as module parameters.
	  This driver doesn't expect any real Audio codec to be present
	  on the device - the audio streams are simply sinked to and
	  sourced from a virtual ALSA sound card created. The user-space
	  application may choose to do whatever it wants with the data
	  received from the USB Host and choose to provide whatever it
	  wants as audio data to the USB Host.
573 574 575 576

	  Say "y" to link the driver statically, or "m" to build a
	  dynamically linked module called "g_audio".

577 578 579 580 581 582 583 584
config GADGET_UAC1
	bool "UAC 1.0 (Legacy)"
	depends on USB_AUDIO
	help
	  If you instead want older UAC Spec-1.0 driver that also has audio
	  paths hardwired to the Audio codec chip on-board and doesn't work
	  without one.

L
Linus Torvalds 已提交
585 586 587
config USB_ETH
	tristate "Ethernet Gadget (with CDC Ethernet support)"
	depends on NET
588
	select CRC32
L
Linus Torvalds 已提交
589
	help
590 591
	  This driver implements Ethernet style communication, in one of
	  several ways:
L
Linus Torvalds 已提交
592 593 594 595 596 597 598 599 600
	  
	   - The "Communication Device Class" (CDC) Ethernet Control Model.
	     That protocol is often avoided with pure Ethernet adapters, in
	     favor of simpler vendor-specific hardware, but is widely
	     supported by firmware for smart network devices.

	   - On hardware can't implement that protocol, a simple CDC subset
	     is used, placing fewer demands on USB.

601 602 603 604 605
	   - CDC Ethernet Emulation Model (EEM) is a newer standard that has
	     a simpler interface that can be used by more USB hardware.

	  RNDIS support is an additional option, more demanding than than
	  subset.
L
Linus Torvalds 已提交
606 607 608 609 610 611 612 613 614 615 616 617 618 619 620

	  Within the USB device, this gadget driver exposes a network device
	  "usbX", where X depends on what other networking devices you have.
	  Treat it like a two-node Ethernet link:  host, and gadget.

	  The Linux-USB host-side "usbnet" driver interoperates with this
	  driver, so that deep I/O queues can be supported.  On 2.4 kernels,
	  use "CDCEther" instead, if you're using the CDC option. That CDC
	  mode should also interoperate with standard CDC Ethernet class
	  drivers on other host operating systems.

	  Say "y" to link the driver statically, or "m" to build a
	  dynamically linked module called "g_ether".

config USB_ETH_RNDIS
621 622
	bool "RNDIS support"
	depends on USB_ETH
L
Linus Torvalds 已提交
623 624 625 626 627 628 629 630 631 632 633 634 635 636 637
	default y
	help
	   Microsoft Windows XP bundles the "Remote NDIS" (RNDIS) protocol,
	   and Microsoft provides redistributable binary RNDIS drivers for
	   older versions of Windows.

	   If you say "y" here, the Ethernet gadget driver will try to provide
	   a second device configuration, supporting RNDIS to talk to such
	   Microsoft USB hosts.
	   
	   To make MS-Windows work with this, use Documentation/usb/linux.inf
	   as the "driver info file".  For versions of MS-Windows older than
	   XP, you'll need to download drivers from Microsoft's website; a URL
	   is given in comments found in that info file.

638 639 640 641 642 643 644 645 646 647 648 649 650 651 652 653
config USB_ETH_EEM
       bool "Ethernet Emulation Model (EEM) support"
       depends on USB_ETH
       default n
       help
         CDC EEM is a newer USB standard that is somewhat simpler than CDC ECM
         and therefore can be supported by more hardware.  Technically ECM and
         EEM are designed for different applications.  The ECM model extends
         the network interface to the target (e.g. a USB cable modem), and the
         EEM model is for mobile devices to communicate with hosts using
         ethernet over USB.  For Linux gadgets, however, the interface with
         the host is the same (a usbX device), so the differences are minimal.

         If you say "y" here, the Ethernet gadget driver will use the EEM
         protocol rather than ECM.  If unsure, say "n".

Y
Yauheni Kaliuta 已提交
654 655 656 657 658 659 660
config USB_G_NCM
	tristate "Network Control Model (NCM) support"
	depends on NET
	select CRC32
	help
	  This driver implements USB CDC NCM subclass standard. NCM is
	  an advanced protocol for Ethernet encapsulation, allows grouping
661
	  of several ethernet frames into one USB transfer and different
Y
Yauheni Kaliuta 已提交
662 663 664 665 666
	  alignment possibilities.

	  Say "y" to link the driver statically, or "m" to build a
	  dynamically linked module called "g_ncm".

L
Linus Torvalds 已提交
667 668 669 670 671 672 673 674 675 676
config USB_GADGETFS
	tristate "Gadget Filesystem (EXPERIMENTAL)"
	depends on EXPERIMENTAL
	help
	  This driver provides a filesystem based API that lets user mode
	  programs implement a single-configuration USB device, including
	  endpoint I/O and control requests that don't relate to enumeration.
	  All endpoints, transfer speeds, and transfer types supported by
	  the hardware are available, through read() and write() calls.

677 678 679
	  Currently, this option is still labelled as EXPERIMENTAL because
	  of existing race conditions in the underlying in-kernel AIO core.

L
Linus Torvalds 已提交
680 681 682
	  Say "y" to link the driver statically, or "m" to build a
	  dynamically linked module called "gadgetfs".

683 684 685
config USB_FUNCTIONFS
	tristate "Function Filesystem (EXPERIMENTAL)"
	depends on EXPERIMENTAL
686
	select USB_FUNCTIONFS_GENERIC if !(USB_FUNCTIONFS_ETH || USB_FUNCTIONFS_RNDIS)
687
	help
688 689
	  The Function Filesystem (FunctionFS) lets one create USB
	  composite functions in user space in the same way GadgetFS
690 691 692 693 694
	  lets one create USB gadgets in user space.  This allows creation
	  of composite gadgets such that some of the functions are
	  implemented in kernel space (for instance Ethernet, serial or
	  mass storage) and other are implemented in user space.

695 696 697
	  If you say "y" or "m" here you will be able what kind of
	  configurations the gadget will provide.

698 699 700 701
	  Say "y" to link the driver statically, or "m" to build
	  a dynamically linked module called "g_ffs".

config USB_FUNCTIONFS_ETH
702
	bool "Include configuration with CDC ECM (Ethernet)"
703
	depends on USB_FUNCTIONFS && NET
704
	help
705 706
	  Include a configuration with CDC ECM function (Ethernet) and the
	  Function Filesystem.
707 708

config USB_FUNCTIONFS_RNDIS
709
	bool "Include configuration with RNDIS (Ethernet)"
710
	depends on USB_FUNCTIONFS && NET
711
	help
712
	  Include a configuration with RNDIS function (Ethernet) and the Filesystem.
713 714 715

config USB_FUNCTIONFS_GENERIC
	bool "Include 'pure' configuration"
716
	depends on USB_FUNCTIONFS
717
	help
718 719
	  Include a configuration with the Function Filesystem alone with
	  no Ethernet interface.
720

L
Linus Torvalds 已提交
721
config USB_FILE_STORAGE
A
Alan Stern 已提交
722
	tristate "File-backed Storage Gadget (DEPRECATED)"
R
Randy Dunlap 已提交
723
	depends on BLOCK
L
Linus Torvalds 已提交
724 725 726 727 728 729 730 731 732
	help
	  The File-backed Storage Gadget acts as a USB Mass Storage
	  disk drive.  As its storage repository it can use a regular
	  file or a block device (in much the same way as the "loop"
	  device driver), specified as a module parameter.

	  Say "y" to link the driver statically, or "m" to build a
	  dynamically linked module called "g_file_storage".

A
Alan Stern 已提交
733 734 735
	  NOTE: This driver is deprecated.  Its replacement is the
	  Mass Storage Gadget.

L
Linus Torvalds 已提交
736 737 738 739 740 741 742 743 744 745
config USB_FILE_STORAGE_TEST
	bool "File-backed Storage Gadget testing version"
	depends on USB_FILE_STORAGE
	default n
	help
	  Say "y" to generate the larger testing version of the
	  File-backed Storage Gadget, useful for probing the
	  behavior of USB Mass Storage hosts.  Not needed for
	  normal operation.

746 747 748 749 750 751 752 753 754
config USB_MASS_STORAGE
	tristate "Mass Storage Gadget"
	depends on BLOCK
	help
	  The Mass Storage Gadget acts as a USB Mass Storage disk drive.
	  As its storage repository it can use a regular file or a block
	  device (in much the same way as the "loop" device driver),
	  specified as a module parameter or sysfs option.

A
Alan Stern 已提交
755 756
	  This driver is an updated replacement for the deprecated
	  File-backed Storage Gadget (g_file_storage).
757 758

	  Say "y" to link the driver statically, or "m" to build
A
Alan Stern 已提交
759
	  a dynamically linked module called "g_mass_storage".
760

761 762 763 764 765 766 767 768 769 770
config USB_GADGET_TARGET
	tristate "USB Gadget Target Fabric Module"
	depends on TARGET_CORE
	help
	  This fabric is an USB gadget. Two USB protocols are supported that is
	  BBB or BOT (Bulk Only Transport) and UAS (USB Attached SCSI). BOT is
	  advertised on alternative interface 0 (primary) and UAS is on
	  alternative interface 1. Both protocols can work on USB2.0 and USB3.0.
	  UAS utilizes the USB 3.0 feature called streams support.

L
Linus Torvalds 已提交
771
config USB_G_SERIAL
F
Felipe Balbi 已提交
772
	tristate "Serial Gadget (with CDC ACM and CDC OBEX support)"
L
Linus Torvalds 已提交
773 774 775 776 777 778
	help
	  The Serial Gadget talks to the Linux-USB generic serial driver.
	  This driver supports a CDC-ACM module option, which can be used
	  to interoperate with MS-Windows hosts or with the Linux-USB
	  "cdc-acm" driver.

F
Felipe Balbi 已提交
779 780 781 782
	  This driver also supports a CDC-OBEX option.  You will need a
	  user space OBEX server talking to /dev/ttyGS*, since the kernel
	  itself doesn't implement the OBEX protocol.

L
Linus Torvalds 已提交
783 784 785 786 787
	  Say "y" to link the driver statically, or "m" to build a
	  dynamically linked module called "g_serial".

	  For more information, see Documentation/usb/gadget_serial.txt
	  which includes instructions and a "driver info file" needed to
F
Felipe Balbi 已提交
788
	  make MS-Windows work with CDC ACM.
L
Linus Torvalds 已提交
789

790 791 792 793 794 795 796 797 798 799 800 801 802 803
config USB_MIDI_GADGET
	tristate "MIDI Gadget (EXPERIMENTAL)"
	depends on SND && EXPERIMENTAL
	select SND_RAWMIDI
	help
	  The MIDI Gadget acts as a USB Audio device, with one MIDI
	  input and one MIDI output. These MIDI jacks appear as
	  a sound "card" in the ALSA sound system. Other MIDI
	  connections can then be made on the gadget system, using
	  ALSA's aconnect utility etc.

	  Say "y" to link the driver statically, or "m" to build a
	  dynamically linked module called "g_midi".

C
Craig W. Nadler 已提交
804 805 806 807 808 809 810 811 812 813 814 815 816 817
config USB_G_PRINTER
	tristate "Printer Gadget"
	help
	  The Printer Gadget channels data between the USB host and a
	  userspace program driving the print engine. The user space
	  program reads and writes the device file /dev/g_printer to
	  receive or send printer data. It can use ioctl calls to
	  the device file to get or set printer status.

	  Say "y" to link the driver statically, or "m" to build a
	  dynamically linked module called "g_printer".

	  For more information, see Documentation/usb/gadget_printer.txt
	  which includes sample code for accessing the device file.
L
Linus Torvalds 已提交
818

819 820
config USB_CDC_COMPOSITE
	tristate "CDC Composite Device (Ethernet and ACM)"
R
Randy Dunlap 已提交
821
	depends on NET
822 823 824 825 826 827 828 829 830 831 832
	help
	  This driver provides two functions in one configuration:
	  a CDC Ethernet (ECM) link, and a CDC ACM (serial port) link.

	  This driver requires four bulk and two interrupt endpoints,
	  plus the ability to handle altsettings.  Not all peripheral
	  controllers are that capable.

	  Say "y" to link the driver statically, or "m" to build a
	  dynamically linked module.

833 834 835 836 837 838 839 840 841 842
config USB_G_NOKIA
	tristate "Nokia composite gadget"
	depends on PHONET
	help
	  The Nokia composite gadget provides support for acm, obex
	  and phonet in only one composite gadget driver.

	  It's only really useful for N900 hardware. If you're building
	  a kernel for N900, say Y or M here. If unsure, say N.

843 844 845 846 847 848 849 850 851 852
config USB_G_ACM_MS
	tristate "CDC Composite Device (ACM and mass storage)"
	depends on BLOCK
	help
	  This driver provides two functions in one configuration:
	  a mass storage, and a CDC ACM (serial port) link.

	  Say "y" to link the driver statically, or "m" to build a
	  dynamically linked module called "g_acm_ms".

853 854
config USB_G_MULTI
	tristate "Multifunction Composite Gadget (EXPERIMENTAL)"
855
	depends on BLOCK && NET
856
	select USB_G_MULTI_CDC if !USB_G_MULTI_RNDIS
857 858 859 860 861
	help
	  The Multifunction Composite Gadget provides Ethernet (RNDIS
	  and/or CDC Ethernet), mass storage and ACM serial link
	  interfaces.

862
	  You will be asked to choose which of the two configurations is
863
	  to be available in the gadget.  At least one configuration must
864
	  be chosen to make the gadget usable.  Selecting more than one
865
	  configuration will prevent Windows from automatically detecting
866
	  the gadget as a composite gadget, so an INF file will be needed to
867 868 869 870 871 872 873 874 875 876 877 878
	  use the gadget.

	  Say "y" to link the driver statically, or "m" to build a
	  dynamically linked module called "g_multi".

config USB_G_MULTI_RNDIS
	bool "RNDIS + CDC Serial + Storage configuration"
	depends on USB_G_MULTI
	default y
	help
	  This option enables a configuration with RNDIS, CDC Serial and
	  Mass Storage functions available in the Multifunction Composite
879 880
	  Gadget.  This is the configuration dedicated for Windows since RNDIS
	  is Microsoft's protocol.
881 882 883 884 885 886 887 888 889 890

	  If unsure, say "y".

config USB_G_MULTI_CDC
	bool "CDC Ethernet + CDC Serial + Storage configuration"
	depends on USB_G_MULTI
	default n
	help
	  This option enables a configuration with CDC Ethernet (ECM), CDC
	  Serial and Mass Storage functions available in the Multifunction
891
	  Composite Gadget.
892 893 894

	  If unsure, say "y".

895 896 897 898 899 900 901 902 903 904 905
config USB_G_HID
	tristate "HID Gadget"
	help
	  The HID gadget driver provides generic emulation of USB
	  Human Interface Devices (HID).

	  For more information, see Documentation/usb/gadget_hid.txt which
	  includes sample code for accessing the device files.

	  Say "y" to link the driver statically, or "m" to build a
	  dynamically linked module called "g_hid".
906

907 908 909 910 911 912 913 914 915 916 917 918 919 920 921 922 923 924 925 926 927 928 929 930 931 932 933 934
config USB_G_DBGP
	tristate "EHCI Debug Device Gadget"
	help
	  This gadget emulates an EHCI Debug device. This is useful when you want
	  to interact with an EHCI Debug Port.

	  Say "y" to link the driver statically, or "m" to build a
	  dynamically linked module called "g_dbgp".

if USB_G_DBGP
choice
	prompt "EHCI Debug Device mode"
	default USB_G_DBGP_SERIAL

config USB_G_DBGP_PRINTK
	depends on USB_G_DBGP
	bool "printk"
	help
	  Directly printk() received data. No interaction.

config USB_G_DBGP_SERIAL
	depends on USB_G_DBGP
	bool "serial"
	help
	  Userland can interact using /dev/ttyGSxxx.
endchoice
endif

L
Linus Torvalds 已提交
935 936
# put drivers that need isochronous transfer support (for audio
# or video class gadget drivers), or specific hardware, here.
L
Laurent Pinchart 已提交
937 938
config USB_G_WEBCAM
	tristate "USB Webcam Gadget"
939
	depends on VIDEO_DEV
L
Laurent Pinchart 已提交
940 941 942 943
	help
	  The Webcam Gadget acts as a composite USB Audio and Video Class
	  device. It provides a userspace API to process UVC control requests
	  and stream video data to the host.
L
Linus Torvalds 已提交
944

L
Laurent Pinchart 已提交
945 946
	  Say "y" to link the driver statically, or "m" to build a
	  dynamically linked module called "g_webcam".
L
Linus Torvalds 已提交
947 948 949

endchoice

D
Denis Cheng 已提交
950
endif # USB_GADGET