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