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