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 16menuconfig USB_GADGET 17 tristate "USB Gadget Support" 18 select NLS 19 help 20 USB is a master/slave protocol, organized with one master 21 host (such as a PC) controlling up to 127 peripheral devices. 22 The USB hardware is asymmetric, which makes it easier to set up: 23 you can't connect a "to-the-host" connector to a peripheral. 24 25 Linux can run in the host, or in the peripheral. In both cases 26 you need a low level bus controller driver, and some software 27 talking to it. Peripheral controllers are often discrete silicon, 28 or are integrated with the CPU in a microcontroller. The more 29 familiar host side controllers have names like "EHCI", "OHCI", 30 or "UHCI", and are usually integrated into southbridges on PC 31 motherboards. 32 33 Enable this configuration option if you want to run Linux inside 34 a USB peripheral device. Configure one hardware driver for your 35 peripheral/device side bus controller, and a "gadget driver" for 36 your peripheral protocol. (If you use modular gadget drivers, 37 you may configure more than one.) 38 39 If in doubt, say "N" and don't enable these drivers; most people 40 don't have this kind of hardware (except maybe inside Linux PDAs). 41 42 For more information, see <http://www.linux-usb.org/gadget> and 43 the kernel DocBook documentation for this API. 44 45if USB_GADGET 46 47config USB_GADGET_DEBUG 48 boolean "Debugging messages (DEVELOPMENT)" 49 depends on DEBUG_KERNEL 50 help 51 Many controller and gadget drivers will print some debugging 52 messages if you use this option to ask for those messages. 53 54 Avoid enabling these messages, even if you're actively 55 debugging such a driver. Many drivers will emit so many 56 messages that the driver timings are affected, which will 57 either create new failure modes or remove the one you're 58 trying to track down. Never enable these messages for a 59 production build. 60 61config USB_GADGET_DEBUG_FILES 62 boolean "Debugging information files (DEVELOPMENT)" 63 depends on PROC_FS 64 help 65 Some of the drivers in the "gadget" framework can expose 66 debugging information in files such as /proc/driver/udc 67 (for a peripheral controller). The information in these 68 files may help when you're troubleshooting or bringing up a 69 driver on a new board. Enable these files by choosing "Y" 70 here. If in doubt, or to conserve kernel memory, say "N". 71 72config USB_GADGET_DEBUG_FS 73 boolean "Debugging information files in debugfs (DEVELOPMENT)" 74 depends on DEBUG_FS 75 help 76 Some of the drivers in the "gadget" framework can expose 77 debugging information in files under /sys/kernel/debug/. 78 The information in these files may help when you're 79 troubleshooting or bringing up a driver on a new board. 80 Enable these files by choosing "Y" here. If in doubt, or 81 to conserve kernel memory, say "N". 82 83config USB_GADGET_VBUS_DRAW 84 int "Maximum VBUS Power usage (2-500 mA)" 85 range 2 500 86 default 2 87 help 88 Some devices need to draw power from USB when they are 89 configured, perhaps to operate circuitry or to recharge 90 batteries. This is in addition to any local power supply, 91 such as an AC adapter or batteries. 92 93 Enter the maximum power your device draws through USB, in 94 milliAmperes. The permitted range of values is 2 - 500 mA; 95 0 mA would be legal, but can make some hosts misbehave. 96 97 This value will be used except for system-specific gadget 98 drivers that have more specific information. 99 100config USB_GADGET_STORAGE_NUM_BUFFERS 101 int "Number of storage pipeline buffers" 102 range 2 4 103 default 2 104 help 105 Usually 2 buffers are enough to establish a good buffering 106 pipeline. The number may be increased in order to compensate 107 for a bursty VFS behaviour. For instance there may be CPU wake up 108 latencies that makes the VFS to appear bursty in a system with 109 an CPU on-demand governor. Especially if DMA is doing IO to 110 offload the CPU. In this case the CPU will go into power 111 save often and spin up occasionally to move data within VFS. 112 If selecting USB_GADGET_DEBUG_FILES this value may be set by 113 a module parameter as well. 114 If unsure, say 2. 115 116# 117# USB Peripheral Controller Support 118# 119# The order here is alphabetical, except that integrated controllers go 120# before discrete ones so they will be the initial/default value: 121# - integrated/SOC controllers first 122# - licensed IP used in both SOC and discrete versions 123# - discrete ones (including all PCI-only controllers) 124# - debug/dummy gadget+hcd is last. 125# 126menu "USB Peripheral Controller" 127 128# 129# Integrated controllers 130# 131 132config USB_AT91 133 tristate "Atmel AT91 USB Device Port" 134 depends on ARCH_AT91 135 help 136 Many Atmel AT91 processors (such as the AT91RM2000) have a 137 full speed USB Device Port with support for five configurable 138 endpoints (plus endpoint zero). 139 140 Say "y" to link the driver statically, or "m" to build a 141 dynamically linked module called "at91_udc" and force all 142 gadget drivers to also be dynamically linked. 143 144config USB_LPC32XX 145 tristate "LPC32XX USB Peripheral Controller" 146 depends on ARCH_LPC32XX 147 select USB_ISP1301 148 help 149 This option selects the USB device controller in the LPC32xx SoC. 150 151 Say "y" to link the driver statically, or "m" to build a 152 dynamically linked module called "lpc32xx_udc" and force all 153 gadget drivers to also be dynamically linked. 154 155config USB_ATMEL_USBA 156 tristate "Atmel USBA" 157 depends on AVR32 || ARCH_AT91SAM9RL || ARCH_AT91SAM9G45 158 help 159 USBA is the integrated high-speed USB Device controller on 160 the AT32AP700x, some AT91SAM9 and AT91CAP9 processors from Atmel. 161 162config USB_BCM63XX_UDC 163 tristate "Broadcom BCM63xx Peripheral Controller" 164 depends on BCM63XX 165 help 166 Many Broadcom BCM63xx chipsets (such as the BCM6328) have a 167 high speed USB Device Port with support for four fixed endpoints 168 (plus endpoint zero). 169 170 Say "y" to link the driver statically, or "m" to build a 171 dynamically linked module called "bcm63xx_udc". 172 173config USB_FSL_USB2 174 tristate "Freescale Highspeed USB DR Peripheral Controller" 175 depends on FSL_SOC || ARCH_MXC 176 select USB_FSL_MPH_DR_OF if OF 177 help 178 Some of Freescale PowerPC and i.MX processors have a High Speed 179 Dual-Role(DR) USB controller, which supports device mode. 180 181 The number of programmable endpoints is different through 182 SOC revisions. 183 184 Say "y" to link the driver statically, or "m" to build a 185 dynamically linked module called "fsl_usb2_udc" and force 186 all gadget drivers to also be dynamically linked. 187 188config USB_FUSB300 189 tristate "Faraday FUSB300 USB Peripheral Controller" 190 depends on !PHYS_ADDR_T_64BIT 191 help 192 Faraday usb device controller FUSB300 driver 193 194config USB_OMAP 195 tristate "OMAP USB Device Controller" 196 depends on ARCH_OMAP1 197 select ISP1301_OMAP if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_H4_OTG 198 help 199 Many Texas Instruments OMAP processors have flexible full 200 speed USB device controllers, with support for up to 30 201 endpoints (plus endpoint zero). This driver supports the 202 controller in the OMAP 1611, and should work with controllers 203 in other OMAP processors too, given minor tweaks. 204 205 Say "y" to link the driver statically, or "m" to build a 206 dynamically linked module called "omap_udc" and force all 207 gadget drivers to also be dynamically linked. 208 209config USB_PXA25X 210 tristate "PXA 25x or IXP 4xx" 211 depends on (ARCH_PXA && PXA25x) || ARCH_IXP4XX 212 help 213 Intel's PXA 25x series XScale ARM-5TE processors include 214 an integrated full speed USB 1.1 device controller. The 215 controller in the IXP 4xx series is register-compatible. 216 217 It has fifteen fixed-function endpoints, as well as endpoint 218 zero (for control transfers). 219 220 Say "y" to link the driver statically, or "m" to build a 221 dynamically linked module called "pxa25x_udc" and force all 222 gadget drivers to also be dynamically linked. 223 224# if there's only one gadget driver, using only two bulk endpoints, 225# don't waste memory for the other endpoints 226config USB_PXA25X_SMALL 227 depends on USB_PXA25X 228 bool 229 default n if USB_ETH_RNDIS 230 default y if USB_ZERO 231 default y if USB_ETH 232 default y if USB_G_SERIAL 233 234config USB_R8A66597 235 tristate "Renesas R8A66597 USB Peripheral Controller" 236 help 237 R8A66597 is a discrete USB host and peripheral controller chip that 238 supports both full and high speed USB 2.0 data transfers. 239 It has nine configurable endpoints, and endpoint zero. 240 241 Say "y" to link the driver statically, or "m" to build a 242 dynamically linked module called "r8a66597_udc" and force all 243 gadget drivers to also be dynamically linked. 244 245config USB_RENESAS_USBHS_UDC 246 tristate 'Renesas USBHS controller' 247 depends on USB_RENESAS_USBHS 248 help 249 Renesas USBHS is a discrete USB host and peripheral controller chip 250 that supports both full and high speed USB 2.0 data transfers. 251 It has nine or more configurable endpoints, and endpoint zero. 252 253 Say "y" to link the driver statically, or "m" to build a 254 dynamically linked module called "renesas_usbhs" and force all 255 gadget drivers to also be dynamically linked. 256 257config USB_PXA27X 258 tristate "PXA 27x" 259 help 260 Intel's PXA 27x series XScale ARM v5TE processors include 261 an integrated full speed USB 1.1 device controller. 262 263 It has up to 23 endpoints, as well as endpoint zero (for 264 control transfers). 265 266 Say "y" to link the driver statically, or "m" to build a 267 dynamically linked module called "pxa27x_udc" and force all 268 gadget drivers to also be dynamically linked. 269 270config USB_S3C_HSOTG 271 tristate "S3C HS/OtG USB Device controller" 272 depends on S3C_DEV_USB_HSOTG 273 help 274 The Samsung S3C64XX USB2.0 high-speed gadget controller 275 integrated into the S3C64XX series SoC. 276 277config USB_IMX 278 tristate "Freescale i.MX1 USB Peripheral Controller" 279 depends on ARCH_MXC 280 depends on BROKEN 281 help 282 Freescale's i.MX1 includes an integrated full speed 283 USB 1.1 device controller. 284 285 It has Six fixed-function endpoints, as well as endpoint 286 zero (for control transfers). 287 288 Say "y" to link the driver statically, or "m" to build a 289 dynamically linked module called "imx_udc" and force all 290 gadget drivers to also be dynamically linked. 291 292config USB_S3C2410 293 tristate "S3C2410 USB Device Controller" 294 depends on ARCH_S3C24XX 295 help 296 Samsung's S3C2410 is an ARM-4 processor with an integrated 297 full speed USB 1.1 device controller. It has 4 configurable 298 endpoints, as well as endpoint zero (for control transfers). 299 300 This driver has been tested on the S3C2410, S3C2412, and 301 S3C2440 processors. 302 303config USB_S3C2410_DEBUG 304 boolean "S3C2410 udc debug messages" 305 depends on USB_S3C2410 306 307config USB_S3C_HSUDC 308 tristate "S3C2416, S3C2443 and S3C2450 USB Device Controller" 309 depends on ARCH_S3C24XX 310 help 311 Samsung's S3C2416, S3C2443 and S3C2450 is an ARM9 based SoC 312 integrated with dual speed USB 2.0 device controller. It has 313 8 endpoints, as well as endpoint zero. 314 315 This driver has been tested on S3C2416 and S3C2450 processors. 316 317config USB_MV_UDC 318 tristate "Marvell USB2.0 Device Controller" 319 depends on GENERIC_HARDIRQS 320 help 321 Marvell Socs (including PXA and MMP series) include a high speed 322 USB2.0 OTG controller, which can be configured as high speed or 323 full speed USB peripheral. 324 325config USB_MV_U3D 326 tristate "MARVELL PXA2128 USB 3.0 controller" 327 help 328 MARVELL PXA2128 Processor series include a super speed USB3.0 device 329 controller, which support super speed USB peripheral. 330 331# 332# Controllers available in both integrated and discrete versions 333# 334 335# musb builds in ../musb along with host support 336config USB_GADGET_MUSB_HDRC 337 tristate "Inventra HDRC USB Peripheral (TI, ADI, ...)" 338 depends on USB_MUSB_HDRC 339 help 340 This OTG-capable silicon IP is used in dual designs including 341 the TI DaVinci, OMAP 243x, OMAP 343x, TUSB 6010, and ADI Blackfin 342 343config USB_M66592 344 tristate "Renesas M66592 USB Peripheral Controller" 345 help 346 M66592 is a discrete USB peripheral controller chip that 347 supports both full and high speed USB 2.0 data transfers. 348 It has seven configurable endpoints, and endpoint zero. 349 350 Say "y" to link the driver statically, or "m" to build a 351 dynamically linked module called "m66592_udc" and force all 352 gadget drivers to also be dynamically linked. 353 354# 355# Controllers available only in discrete form (and all PCI controllers) 356# 357 358config USB_AMD5536UDC 359 tristate "AMD5536 UDC" 360 depends on PCI 361 help 362 The AMD5536 UDC is part of the AMD Geode CS5536, an x86 southbridge. 363 It is a USB Highspeed DMA capable USB device controller. Beside ep0 364 it provides 4 IN and 4 OUT endpoints (bulk or interrupt type). 365 The UDC port supports OTG operation, and may be used as a host port 366 if it's not being used to implement peripheral or OTG roles. 367 368 Say "y" to link the driver statically, or "m" to build a 369 dynamically linked module called "amd5536udc" and force all 370 gadget drivers to also be dynamically linked. 371 372config USB_FSL_QE 373 tristate "Freescale QE/CPM USB Device Controller" 374 depends on FSL_SOC && (QUICC_ENGINE || CPM) 375 help 376 Some of Freescale PowerPC processors have a Full Speed 377 QE/CPM2 USB controller, which support device mode with 4 378 programmable endpoints. This driver supports the 379 controller in the MPC8360 and MPC8272, and should work with 380 controllers having QE or CPM2, given minor tweaks. 381 382 Set CONFIG_USB_GADGET to "m" to build this driver as a 383 dynamically linked module called "fsl_qe_udc". 384 385config USB_NET2272 386 tristate "PLX NET2272" 387 help 388 PLX NET2272 is a USB peripheral controller which supports 389 both full and high speed USB 2.0 data transfers. 390 391 It has three configurable endpoints, as well as endpoint zero 392 (for control transfer). 393 Say "y" to link the driver statically, or "m" to build a 394 dynamically linked module called "net2272" and force all 395 gadget drivers to also be dynamically linked. 396 397config USB_NET2272_DMA 398 boolean "Support external DMA controller" 399 depends on USB_NET2272 400 help 401 The NET2272 part can optionally support an external DMA 402 controller, but your board has to have support in the 403 driver itself. 404 405 If unsure, say "N" here. The driver works fine in PIO mode. 406 407config USB_NET2280 408 tristate "NetChip 228x" 409 depends on PCI 410 help 411 NetChip 2280 / 2282 is a PCI based USB peripheral controller which 412 supports both full and high speed USB 2.0 data transfers. 413 414 It has six configurable endpoints, as well as endpoint zero 415 (for control transfers) and several endpoints with dedicated 416 functions. 417 418 Say "y" to link the driver statically, or "m" to build a 419 dynamically linked module called "net2280" and force all 420 gadget drivers to also be dynamically linked. 421 422config USB_GOKU 423 tristate "Toshiba TC86C001 'Goku-S'" 424 depends on PCI 425 help 426 The Toshiba TC86C001 is a PCI device which includes controllers 427 for full speed USB devices, IDE, I2C, SIO, plus a USB host (OHCI). 428 429 The device controller has three configurable (bulk or interrupt) 430 endpoints, plus endpoint zero (for control transfers). 431 432 Say "y" to link the driver statically, or "m" to build a 433 dynamically linked module called "goku_udc" and to force all 434 gadget drivers to also be dynamically linked. 435 436config USB_EG20T 437 tristate "Intel EG20T PCH/LAPIS Semiconductor IOH(ML7213/ML7831) UDC" 438 depends on PCI && GENERIC_HARDIRQS 439 help 440 This is a USB device driver for EG20T PCH. 441 EG20T PCH is the platform controller hub that is used in Intel's 442 general embedded platform. EG20T PCH has USB device interface. 443 Using this interface, it is able to access system devices connected 444 to USB device. 445 This driver enables USB device function. 446 USB device is a USB peripheral controller which 447 supports both full and high speed USB 2.0 data transfers. 448 This driver supports both control transfer and bulk transfer modes. 449 This driver dose not support interrupt transfer or isochronous 450 transfer modes. 451 452 This driver also can be used for LAPIS Semiconductor's ML7213 which is 453 for IVI(In-Vehicle Infotainment) use. 454 ML7831 is for general purpose use. 455 ML7213/ML7831 is companion chip for Intel Atom E6xx series. 456 ML7213/ML7831 is completely compatible for Intel EG20T PCH. 457 458# 459# LAST -- dummy/emulated controller 460# 461 462config USB_DUMMY_HCD 463 tristate "Dummy HCD (DEVELOPMENT)" 464 depends on USB=y || (USB=m && USB_GADGET=m) 465 help 466 This host controller driver emulates USB, looping all data transfer 467 requests back to a USB "gadget driver" in the same host. The host 468 side is the master; the gadget side is the slave. Gadget drivers 469 can be high, full, or low speed; and they have access to endpoints 470 like those from NET2280, PXA2xx, or SA1100 hardware. 471 472 This may help in some stages of creating a driver to embed in a 473 Linux device, since it lets you debug several parts of the gadget 474 driver without its hardware or drivers being involved. 475 476 Since such a gadget side driver needs to interoperate with a host 477 side Linux-USB device driver, this may help to debug both sides 478 of a USB protocol stack. 479 480 Say "y" to link the driver statically, or "m" to build a 481 dynamically linked module called "dummy_hcd" and force all 482 gadget drivers to also be dynamically linked. 483 484# NOTE: Please keep dummy_hcd LAST so that "real hardware" appears 485# first and will be selected by default. 486 487endmenu 488 489# 490# USB Gadget Drivers 491# 492 493# composite based drivers 494config USB_LIBCOMPOSITE 495 tristate 496 depends on USB_GADGET 497 498config USB_F_ACM 499 tristate 500 501config USB_F_SS_LB 502 tristate 503 504config USB_U_SERIAL 505 tristate 506 507choice 508 tristate "USB Gadget Drivers" 509 default USB_ETH 510 help 511 A Linux "Gadget Driver" talks to the USB Peripheral Controller 512 driver through the abstract "gadget" API. Some other operating 513 systems call these "client" drivers, of which "class drivers" 514 are a subset (implementing a USB device class specification). 515 A gadget driver implements one or more USB functions using 516 the peripheral hardware. 517 518 Gadget drivers are hardware-neutral, or "platform independent", 519 except that they sometimes must understand quirks or limitations 520 of the particular controllers they work with. For example, when 521 a controller doesn't support alternate configurations or provide 522 enough of the right types of endpoints, the gadget driver might 523 not be able work with that controller, or might need to implement 524 a less common variant of a device class protocol. 525 526# this first set of drivers all depend on bulk-capable hardware. 527 528config USB_ZERO 529 tristate "Gadget Zero (DEVELOPMENT)" 530 select USB_LIBCOMPOSITE 531 select USB_F_SS_LB 532 help 533 Gadget Zero is a two-configuration device. It either sinks and 534 sources bulk data; or it loops back a configurable number of 535 transfers. It also implements control requests, for "chapter 9" 536 conformance. The driver needs only two bulk-capable endpoints, so 537 it can work on top of most device-side usb controllers. It's 538 useful for testing, and is also a working example showing how 539 USB "gadget drivers" can be written. 540 541 Make this be the first driver you try using on top of any new 542 USB peripheral controller driver. Then you can use host-side 543 test software, like the "usbtest" driver, to put your hardware 544 and its driver through a basic set of functional tests. 545 546 Gadget Zero also works with the host-side "usb-skeleton" driver, 547 and with many kinds of host-side test software. You may need 548 to tweak product and vendor IDs before host software knows about 549 this device, and arrange to select an appropriate configuration. 550 551 Say "y" to link the driver statically, or "m" to build a 552 dynamically linked module called "g_zero". 553 554config USB_ZERO_HNPTEST 555 boolean "HNP Test Device" 556 depends on USB_ZERO && USB_OTG 557 help 558 You can configure this device to enumerate using the device 559 identifiers of the USB-OTG test device. That means that when 560 this gadget connects to another OTG device, with this one using 561 the "B-Peripheral" role, that device will use HNP to let this 562 one serve as the USB host instead (in the "B-Host" role). 563 564config USB_AUDIO 565 tristate "Audio Gadget" 566 depends on SND 567 select USB_LIBCOMPOSITE 568 select SND_PCM 569 help 570 This Gadget Audio driver is compatible with USB Audio Class 571 specification 2.0. It implements 1 AudioControl interface, 572 1 AudioStreaming Interface each for USB-OUT and USB-IN. 573 Number of channels, sample rate and sample size can be 574 specified as module parameters. 575 This driver doesn't expect any real Audio codec to be present 576 on the device - the audio streams are simply sinked to and 577 sourced from a virtual ALSA sound card created. The user-space 578 application may choose to do whatever it wants with the data 579 received from the USB Host and choose to provide whatever it 580 wants as audio data to the USB Host. 581 582 Say "y" to link the driver statically, or "m" to build a 583 dynamically linked module called "g_audio". 584 585config GADGET_UAC1 586 bool "UAC 1.0 (Legacy)" 587 depends on USB_AUDIO 588 help 589 If you instead want older UAC Spec-1.0 driver that also has audio 590 paths hardwired to the Audio codec chip on-board and doesn't work 591 without one. 592 593config USB_ETH 594 tristate "Ethernet Gadget (with CDC Ethernet support)" 595 depends on NET 596 select USB_LIBCOMPOSITE 597 select CRC32 598 help 599 This driver implements Ethernet style communication, in one of 600 several ways: 601 602 - The "Communication Device Class" (CDC) Ethernet Control Model. 603 That protocol is often avoided with pure Ethernet adapters, in 604 favor of simpler vendor-specific hardware, but is widely 605 supported by firmware for smart network devices. 606 607 - On hardware can't implement that protocol, a simple CDC subset 608 is used, placing fewer demands on USB. 609 610 - CDC Ethernet Emulation Model (EEM) is a newer standard that has 611 a simpler interface that can be used by more USB hardware. 612 613 RNDIS support is an additional option, more demanding than than 614 subset. 615 616 Within the USB device, this gadget driver exposes a network device 617 "usbX", where X depends on what other networking devices you have. 618 Treat it like a two-node Ethernet link: host, and gadget. 619 620 The Linux-USB host-side "usbnet" driver interoperates with this 621 driver, so that deep I/O queues can be supported. On 2.4 kernels, 622 use "CDCEther" instead, if you're using the CDC option. That CDC 623 mode should also interoperate with standard CDC Ethernet class 624 drivers on other host operating systems. 625 626 Say "y" to link the driver statically, or "m" to build a 627 dynamically linked module called "g_ether". 628 629config USB_ETH_RNDIS 630 bool "RNDIS support" 631 depends on USB_ETH 632 select USB_LIBCOMPOSITE 633 default y 634 help 635 Microsoft Windows XP bundles the "Remote NDIS" (RNDIS) protocol, 636 and Microsoft provides redistributable binary RNDIS drivers for 637 older versions of Windows. 638 639 If you say "y" here, the Ethernet gadget driver will try to provide 640 a second device configuration, supporting RNDIS to talk to such 641 Microsoft USB hosts. 642 643 To make MS-Windows work with this, use Documentation/usb/linux.inf 644 as the "driver info file". For versions of MS-Windows older than 645 XP, you'll need to download drivers from Microsoft's website; a URL 646 is given in comments found in that info file. 647 648config USB_ETH_EEM 649 bool "Ethernet Emulation Model (EEM) support" 650 depends on USB_ETH 651 select USB_LIBCOMPOSITE 652 default n 653 help 654 CDC EEM is a newer USB standard that is somewhat simpler than CDC ECM 655 and therefore can be supported by more hardware. Technically ECM and 656 EEM are designed for different applications. The ECM model extends 657 the network interface to the target (e.g. a USB cable modem), and the 658 EEM model is for mobile devices to communicate with hosts using 659 ethernet over USB. For Linux gadgets, however, the interface with 660 the host is the same (a usbX device), so the differences are minimal. 661 662 If you say "y" here, the Ethernet gadget driver will use the EEM 663 protocol rather than ECM. If unsure, say "n". 664 665config USB_G_NCM 666 tristate "Network Control Model (NCM) support" 667 depends on NET 668 select USB_LIBCOMPOSITE 669 select CRC32 670 help 671 This driver implements USB CDC NCM subclass standard. NCM is 672 an advanced protocol for Ethernet encapsulation, allows grouping 673 of several ethernet frames into one USB transfer and different 674 alignment possibilities. 675 676 Say "y" to link the driver statically, or "m" to build a 677 dynamically linked module called "g_ncm". 678 679config USB_GADGETFS 680 tristate "Gadget Filesystem" 681 help 682 This driver provides a filesystem based API that lets user mode 683 programs implement a single-configuration USB device, including 684 endpoint I/O and control requests that don't relate to enumeration. 685 All endpoints, transfer speeds, and transfer types supported by 686 the hardware are available, through read() and write() calls. 687 688 Say "y" to link the driver statically, or "m" to build a 689 dynamically linked module called "gadgetfs". 690 691config USB_FUNCTIONFS 692 tristate "Function Filesystem" 693 select USB_LIBCOMPOSITE 694 select USB_FUNCTIONFS_GENERIC if !(USB_FUNCTIONFS_ETH || USB_FUNCTIONFS_RNDIS) 695 help 696 The Function Filesystem (FunctionFS) lets one create USB 697 composite functions in user space in the same way GadgetFS 698 lets one create USB gadgets in user space. This allows creation 699 of composite gadgets such that some of the functions are 700 implemented in kernel space (for instance Ethernet, serial or 701 mass storage) and other are implemented in user space. 702 703 If you say "y" or "m" here you will be able what kind of 704 configurations the gadget will provide. 705 706 Say "y" to link the driver statically, or "m" to build 707 a dynamically linked module called "g_ffs". 708 709config USB_FUNCTIONFS_ETH 710 bool "Include configuration with CDC ECM (Ethernet)" 711 depends on USB_FUNCTIONFS && NET 712 help 713 Include a configuration with CDC ECM function (Ethernet) and the 714 Function Filesystem. 715 716config USB_FUNCTIONFS_RNDIS 717 bool "Include configuration with RNDIS (Ethernet)" 718 depends on USB_FUNCTIONFS && NET 719 help 720 Include a configuration with RNDIS function (Ethernet) and the Filesystem. 721 722config USB_FUNCTIONFS_GENERIC 723 bool "Include 'pure' configuration" 724 depends on USB_FUNCTIONFS 725 help 726 Include a configuration with the Function Filesystem alone with 727 no Ethernet interface. 728 729config USB_MASS_STORAGE 730 tristate "Mass Storage Gadget" 731 depends on BLOCK 732 select USB_LIBCOMPOSITE 733 help 734 The Mass Storage Gadget acts as a USB Mass Storage disk drive. 735 As its storage repository it can use a regular file or a block 736 device (in much the same way as the "loop" device driver), 737 specified as a module parameter or sysfs option. 738 739 This driver is a replacement for now removed File-backed 740 Storage Gadget (g_file_storage). 741 742 Say "y" to link the driver statically, or "m" to build 743 a dynamically linked module called "g_mass_storage". 744 745config USB_GADGET_TARGET 746 tristate "USB Gadget Target Fabric Module" 747 depends on TARGET_CORE 748 select USB_LIBCOMPOSITE 749 help 750 This fabric is an USB gadget. Two USB protocols are supported that is 751 BBB or BOT (Bulk Only Transport) and UAS (USB Attached SCSI). BOT is 752 advertised on alternative interface 0 (primary) and UAS is on 753 alternative interface 1. Both protocols can work on USB2.0 and USB3.0. 754 UAS utilizes the USB 3.0 feature called streams support. 755 756config USB_G_SERIAL 757 tristate "Serial Gadget (with CDC ACM and CDC OBEX support)" 758 depends on TTY 759 select USB_U_SERIAL 760 select USB_F_ACM 761 select USB_LIBCOMPOSITE 762 help 763 The Serial Gadget talks to the Linux-USB generic serial driver. 764 This driver supports a CDC-ACM module option, which can be used 765 to interoperate with MS-Windows hosts or with the Linux-USB 766 "cdc-acm" driver. 767 768 This driver also supports a CDC-OBEX option. You will need a 769 user space OBEX server talking to /dev/ttyGS*, since the kernel 770 itself doesn't implement the OBEX protocol. 771 772 Say "y" to link the driver statically, or "m" to build a 773 dynamically linked module called "g_serial". 774 775 For more information, see Documentation/usb/gadget_serial.txt 776 which includes instructions and a "driver info file" needed to 777 make MS-Windows work with CDC ACM. 778 779config USB_MIDI_GADGET 780 tristate "MIDI Gadget" 781 depends on SND 782 select USB_LIBCOMPOSITE 783 select SND_RAWMIDI 784 help 785 The MIDI Gadget acts as a USB Audio device, with one MIDI 786 input and one MIDI output. These MIDI jacks appear as 787 a sound "card" in the ALSA sound system. Other MIDI 788 connections can then be made on the gadget system, using 789 ALSA's aconnect utility etc. 790 791 Say "y" to link the driver statically, or "m" to build a 792 dynamically linked module called "g_midi". 793 794config USB_G_PRINTER 795 tristate "Printer Gadget" 796 select USB_LIBCOMPOSITE 797 help 798 The Printer Gadget channels data between the USB host and a 799 userspace program driving the print engine. The user space 800 program reads and writes the device file /dev/g_printer to 801 receive or send printer data. It can use ioctl calls to 802 the device file to get or set printer status. 803 804 Say "y" to link the driver statically, or "m" to build a 805 dynamically linked module called "g_printer". 806 807 For more information, see Documentation/usb/gadget_printer.txt 808 which includes sample code for accessing the device file. 809 810if TTY 811 812config USB_CDC_COMPOSITE 813 tristate "CDC Composite Device (Ethernet and ACM)" 814 depends on NET 815 select USB_LIBCOMPOSITE 816 select USB_U_SERIAL 817 select USB_F_ACM 818 help 819 This driver provides two functions in one configuration: 820 a CDC Ethernet (ECM) link, and a CDC ACM (serial port) link. 821 822 This driver requires four bulk and two interrupt endpoints, 823 plus the ability to handle altsettings. Not all peripheral 824 controllers are that capable. 825 826 Say "y" to link the driver statically, or "m" to build a 827 dynamically linked module. 828 829config USB_G_NOKIA 830 tristate "Nokia composite gadget" 831 depends on PHONET 832 select USB_LIBCOMPOSITE 833 select USB_U_SERIAL 834 select USB_F_ACM 835 help 836 The Nokia composite gadget provides support for acm, obex 837 and phonet in only one composite gadget driver. 838 839 It's only really useful for N900 hardware. If you're building 840 a kernel for N900, say Y or M here. If unsure, say N. 841 842config USB_G_ACM_MS 843 tristate "CDC Composite Device (ACM and mass storage)" 844 depends on BLOCK 845 select USB_LIBCOMPOSITE 846 select USB_U_SERIAL 847 select USB_F_ACM 848 help 849 This driver provides two functions in one configuration: 850 a mass storage, and a CDC ACM (serial port) link. 851 852 Say "y" to link the driver statically, or "m" to build a 853 dynamically linked module called "g_acm_ms". 854 855config USB_G_MULTI 856 tristate "Multifunction Composite Gadget" 857 depends on BLOCK && NET 858 select USB_G_MULTI_CDC if !USB_G_MULTI_RNDIS 859 select USB_LIBCOMPOSITE 860 select USB_U_SERIAL 861 select USB_F_ACM 862 help 863 The Multifunction Composite Gadget provides Ethernet (RNDIS 864 and/or CDC Ethernet), mass storage and ACM serial link 865 interfaces. 866 867 You will be asked to choose which of the two configurations is 868 to be available in the gadget. At least one configuration must 869 be chosen to make the gadget usable. Selecting more than one 870 configuration will prevent Windows from automatically detecting 871 the gadget as a composite gadget, so an INF file will be needed to 872 use the gadget. 873 874 Say "y" to link the driver statically, or "m" to build a 875 dynamically linked module called "g_multi". 876 877config USB_G_MULTI_RNDIS 878 bool "RNDIS + CDC Serial + Storage configuration" 879 depends on USB_G_MULTI 880 default y 881 help 882 This option enables a configuration with RNDIS, CDC Serial and 883 Mass Storage functions available in the Multifunction Composite 884 Gadget. This is the configuration dedicated for Windows since RNDIS 885 is Microsoft's protocol. 886 887 If unsure, say "y". 888 889config USB_G_MULTI_CDC 890 bool "CDC Ethernet + CDC Serial + Storage configuration" 891 depends on USB_G_MULTI 892 default n 893 help 894 This option enables a configuration with CDC Ethernet (ECM), CDC 895 Serial and Mass Storage functions available in the Multifunction 896 Composite Gadget. 897 898 If unsure, say "y". 899 900endif # TTY 901 902config USB_G_HID 903 tristate "HID Gadget" 904 select USB_LIBCOMPOSITE 905 help 906 The HID gadget driver provides generic emulation of USB 907 Human Interface Devices (HID). 908 909 For more information, see Documentation/usb/gadget_hid.txt which 910 includes sample code for accessing the device files. 911 912 Say "y" to link the driver statically, or "m" to build a 913 dynamically linked module called "g_hid". 914 915# Standalone / single function gadgets 916config USB_G_DBGP 917 tristate "EHCI Debug Device Gadget" 918 depends on TTY 919 select USB_LIBCOMPOSITE 920 help 921 This gadget emulates an EHCI Debug device. This is useful when you want 922 to interact with an EHCI Debug Port. 923 924 Say "y" to link the driver statically, or "m" to build a 925 dynamically linked module called "g_dbgp". 926 927if USB_G_DBGP 928choice 929 prompt "EHCI Debug Device mode" 930 default USB_G_DBGP_SERIAL 931 932config USB_G_DBGP_PRINTK 933 depends on USB_G_DBGP 934 bool "printk" 935 help 936 Directly printk() received data. No interaction. 937 938config USB_G_DBGP_SERIAL 939 depends on USB_G_DBGP 940 select USB_U_SERIAL 941 bool "serial" 942 help 943 Userland can interact using /dev/ttyGSxxx. 944endchoice 945endif 946 947# put drivers that need isochronous transfer support (for audio 948# or video class gadget drivers), or specific hardware, here. 949config USB_G_WEBCAM 950 tristate "USB Webcam Gadget" 951 depends on VIDEO_DEV 952 select USB_LIBCOMPOSITE 953 select VIDEOBUF2_VMALLOC 954 help 955 The Webcam Gadget acts as a composite USB Audio and Video Class 956 device. It provides a userspace API to process UVC control requests 957 and stream video data to the host. 958 959 Say "y" to link the driver statically, or "m" to build a 960 dynamically linked module called "g_webcam". 961 962endchoice 963 964endif # USB_GADGET 965