Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 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). |
Matt LaPlante | cab0089 | 2006-10-03 22:36:44 +0200 | [diff] [blame] | 10 | # - Some systems have both kinds of controllers. |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 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 | # |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 15 | |
Denis Cheng | b75be4a | 2008-01-24 16:36:31 +0800 | [diff] [blame] | 16 | menuconfig USB_GADGET |
| 17 | tristate "USB Gadget Support" |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 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 |
Jules Villard | e113f29 | 2006-08-22 22:40:15 +0200 | [diff] [blame] | 28 | familiar host side controllers have names like "EHCI", "OHCI", |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 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 | |
Denis Cheng | b75be4a | 2008-01-24 16:36:31 +0800 | [diff] [blame] | 44 | if USB_GADGET |
| 45 | |
David Brownell | 70790f6 | 2007-07-01 17:35:28 -0700 | [diff] [blame] | 46 | config USB_GADGET_DEBUG |
Robert P. J. Day | afd0e0f | 2008-03-10 15:09:51 -0400 | [diff] [blame] | 47 | boolean "Debugging messages (DEVELOPMENT)" |
David Brownell | 36e893d | 2008-09-12 09:39:06 -0700 | [diff] [blame] | 48 | depends on DEBUG_KERNEL |
David Brownell | 70790f6 | 2007-07-01 17:35:28 -0700 | [diff] [blame] | 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 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 60 | config USB_GADGET_DEBUG_FILES |
Robert P. J. Day | afd0e0f | 2008-03-10 15:09:51 -0400 | [diff] [blame] | 61 | boolean "Debugging information files (DEVELOPMENT)" |
David Brownell | 36e893d | 2008-09-12 09:39:06 -0700 | [diff] [blame] | 62 | depends on PROC_FS |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 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 | |
Haavard Skinnemoen | 914a3f3 | 2007-10-10 02:29:43 -0700 | [diff] [blame] | 71 | config USB_GADGET_DEBUG_FS |
Robert P. J. Day | afd0e0f | 2008-03-10 15:09:51 -0400 | [diff] [blame] | 72 | boolean "Debugging information files in debugfs (DEVELOPMENT)" |
David Brownell | 36e893d | 2008-09-12 09:39:06 -0700 | [diff] [blame] | 73 | depends on DEBUG_FS |
Haavard Skinnemoen | 914a3f3 | 2007-10-10 02:29:43 -0700 | [diff] [blame] | 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 | |
David Brownell | 36e893d | 2008-09-12 09:39:06 -0700 | [diff] [blame] | 82 | config 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 | |
David Brownell | 028b271 | 2005-05-06 07:02:01 -0700 | [diff] [blame] | 99 | config USB_GADGET_SELECTED |
| 100 | boolean |
| 101 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 102 | # |
| 103 | # USB Peripheral Controller Support |
| 104 | # |
David Brownell | a7a19fa | 2008-08-14 17:04:48 -0700 | [diff] [blame] | 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 | # |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 112 | choice |
| 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 | |
David Brownell | a7a19fa | 2008-08-14 17:04:48 -0700 | [diff] [blame] | 121 | # |
| 122 | # Integrated controllers |
| 123 | # |
| 124 | |
| 125 | config USB_GADGET_AT91 |
| 126 | boolean "Atmel AT91 USB Device Port" |
| 127 | depends on ARCH_AT91 && !ARCH_AT91SAM9RL && !ARCH_AT91CAP9 |
| 128 | select USB_GADGET_SELECTED |
Thomas Dahlmann | 55d402d | 2007-07-16 21:40:54 -0700 | [diff] [blame] | 129 | help |
David Brownell | a7a19fa | 2008-08-14 17:04:48 -0700 | [diff] [blame] | 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). |
Thomas Dahlmann | 55d402d | 2007-07-16 21:40:54 -0700 | [diff] [blame] | 133 | |
| 134 | Say "y" to link the driver statically, or "m" to build a |
David Brownell | a7a19fa | 2008-08-14 17:04:48 -0700 | [diff] [blame] | 135 | dynamically linked module called "at91_udc" and force all |
Thomas Dahlmann | 55d402d | 2007-07-16 21:40:54 -0700 | [diff] [blame] | 136 | gadget drivers to also be dynamically linked. |
| 137 | |
David Brownell | a7a19fa | 2008-08-14 17:04:48 -0700 | [diff] [blame] | 138 | config USB_AT91 |
Thomas Dahlmann | 55d402d | 2007-07-16 21:40:54 -0700 | [diff] [blame] | 139 | tristate |
David Brownell | a7a19fa | 2008-08-14 17:04:48 -0700 | [diff] [blame] | 140 | depends on USB_GADGET_AT91 |
Thomas Dahlmann | 55d402d | 2007-07-16 21:40:54 -0700 | [diff] [blame] | 141 | default USB_GADGET |
Thomas Dahlmann | 55d402d | 2007-07-16 21:40:54 -0700 | [diff] [blame] | 142 | |
Haavard Skinnemoen | 914a3f3 | 2007-10-10 02:29:43 -0700 | [diff] [blame] | 143 | config USB_GADGET_ATMEL_USBA |
| 144 | boolean "Atmel USBA" |
| 145 | select USB_GADGET_DUALSPEED |
Nicolas Ferre | ba45ca4 | 2008-04-08 13:59:18 +0100 | [diff] [blame] | 146 | depends on AVR32 || ARCH_AT91CAP9 || ARCH_AT91SAM9RL |
Haavard Skinnemoen | 914a3f3 | 2007-10-10 02:29:43 -0700 | [diff] [blame] | 147 | help |
| 148 | USBA is the integrated high-speed USB Device controller on |
Nicolas Ferre | ba45ca4 | 2008-04-08 13:59:18 +0100 | [diff] [blame] | 149 | the AT32AP700x, some AT91SAM9 and AT91CAP9 processors from Atmel. |
Haavard Skinnemoen | 914a3f3 | 2007-10-10 02:29:43 -0700 | [diff] [blame] | 150 | |
| 151 | config USB_ATMEL_USBA |
| 152 | tristate |
| 153 | depends on USB_GADGET_ATMEL_USBA |
| 154 | default USB_GADGET |
| 155 | select USB_GADGET_SELECTED |
| 156 | |
Li Yang | b504882 | 2007-04-23 10:54:25 -0700 | [diff] [blame] | 157 | config USB_GADGET_FSL_USB2 |
| 158 | boolean "Freescale Highspeed USB DR Peripheral Controller" |
Guennadi Liakhovetski | 54e4026 | 2009-04-15 14:25:33 +0200 | [diff] [blame] | 159 | depends on FSL_SOC || ARCH_MXC |
Li Yang | b504882 | 2007-04-23 10:54:25 -0700 | [diff] [blame] | 160 | select USB_GADGET_DUALSPEED |
| 161 | help |
| 162 | Some of Freescale PowerPC processors have a High Speed |
| 163 | Dual-Role(DR) USB controller, which supports device mode. |
| 164 | |
| 165 | The number of programmable endpoints is different through |
| 166 | SOC revisions. |
| 167 | |
| 168 | Say "y" to link the driver statically, or "m" to build a |
| 169 | dynamically linked module called "fsl_usb2_udc" and force |
| 170 | all gadget drivers to also be dynamically linked. |
| 171 | |
| 172 | config USB_FSL_USB2 |
| 173 | tristate |
| 174 | depends on USB_GADGET_FSL_USB2 |
| 175 | default USB_GADGET |
| 176 | select USB_GADGET_SELECTED |
| 177 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 178 | config USB_GADGET_LH7A40X |
| 179 | boolean "LH7A40X" |
| 180 | depends on ARCH_LH7A40X |
| 181 | help |
David Brownell | a7a19fa | 2008-08-14 17:04:48 -0700 | [diff] [blame] | 182 | This driver provides USB Device Controller driver for LH7A40x |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 183 | |
| 184 | config USB_LH7A40X |
| 185 | tristate |
| 186 | depends on USB_GADGET_LH7A40X |
| 187 | default USB_GADGET |
David Brownell | 028b271 | 2005-05-06 07:02:01 -0700 | [diff] [blame] | 188 | select USB_GADGET_SELECTED |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 189 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 190 | config USB_GADGET_OMAP |
| 191 | boolean "OMAP USB Device Controller" |
| 192 | depends on ARCH_OMAP |
Tony Lindgren | f1c9e15 | 2008-09-04 16:25:14 -0700 | [diff] [blame] | 193 | select ISP1301_OMAP if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_H4_OTG |
David Brownell | 54b9ed3 | 2009-02-11 22:31:12 -0800 | [diff] [blame] | 194 | select USB_OTG_UTILS if ARCH_OMAP |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 195 | help |
| 196 | Many Texas Instruments OMAP processors have flexible full |
| 197 | speed USB device controllers, with support for up to 30 |
| 198 | endpoints (plus endpoint zero). This driver supports the |
| 199 | controller in the OMAP 1611, and should work with controllers |
| 200 | in other OMAP processors too, given minor tweaks. |
| 201 | |
| 202 | Say "y" to link the driver statically, or "m" to build a |
| 203 | dynamically linked module called "omap_udc" and force all |
| 204 | gadget drivers to also be dynamically linked. |
| 205 | |
| 206 | config USB_OMAP |
| 207 | tristate |
| 208 | depends on USB_GADGET_OMAP |
| 209 | default USB_GADGET |
David Brownell | 028b271 | 2005-05-06 07:02:01 -0700 | [diff] [blame] | 210 | select USB_GADGET_SELECTED |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 211 | |
| 212 | config USB_OTG |
| 213 | boolean "OTG Support" |
| 214 | depends on USB_GADGET_OMAP && ARCH_OMAP_OTG && USB_OHCI_HCD |
| 215 | help |
| 216 | The most notable feature of USB OTG is support for a |
| 217 | "Dual-Role" device, which can act as either a device |
| 218 | or a host. The initial role choice can be changed |
| 219 | later, when two dual-role devices talk to each other. |
| 220 | |
| 221 | Select this only if your OMAP board has a Mini-AB connector. |
| 222 | |
David Brownell | a7a19fa | 2008-08-14 17:04:48 -0700 | [diff] [blame] | 223 | config USB_GADGET_PXA25X |
| 224 | boolean "PXA 25x or IXP 4xx" |
| 225 | depends on (ARCH_PXA && PXA25x) || ARCH_IXP4XX |
| 226 | help |
| 227 | Intel's PXA 25x series XScale ARM-5TE processors include |
| 228 | an integrated full speed USB 1.1 device controller. The |
| 229 | controller in the IXP 4xx series is register-compatible. |
| 230 | |
| 231 | It has fifteen fixed-function endpoints, as well as endpoint |
| 232 | zero (for control transfers). |
| 233 | |
| 234 | Say "y" to link the driver statically, or "m" to build a |
| 235 | dynamically linked module called "pxa25x_udc" and force all |
| 236 | gadget drivers to also be dynamically linked. |
| 237 | |
| 238 | config USB_PXA25X |
| 239 | tristate |
| 240 | depends on USB_GADGET_PXA25X |
| 241 | default USB_GADGET |
| 242 | select USB_GADGET_SELECTED |
| 243 | |
| 244 | # if there's only one gadget driver, using only two bulk endpoints, |
| 245 | # don't waste memory for the other endpoints |
| 246 | config USB_PXA25X_SMALL |
| 247 | depends on USB_GADGET_PXA25X |
| 248 | bool |
| 249 | default n if USB_ETH_RNDIS |
| 250 | default y if USB_ZERO |
| 251 | default y if USB_ETH |
| 252 | default y if USB_G_SERIAL |
| 253 | |
| 254 | config USB_GADGET_PXA27X |
| 255 | boolean "PXA 27x" |
Robert Jarzmik | 9f5351b | 2009-04-21 20:34:44 -0700 | [diff] [blame] | 256 | depends on ARCH_PXA && (PXA27x || PXA3xx) |
Robert Jarzmik | 7fec3c2 | 2009-01-24 23:57:30 -0800 | [diff] [blame] | 257 | select USB_OTG_UTILS |
David Brownell | a7a19fa | 2008-08-14 17:04:48 -0700 | [diff] [blame] | 258 | help |
| 259 | Intel's PXA 27x series XScale ARM v5TE processors include |
| 260 | an integrated full speed USB 1.1 device controller. |
| 261 | |
| 262 | It has up to 23 endpoints, as well as endpoint zero (for |
| 263 | control transfers). |
| 264 | |
| 265 | Say "y" to link the driver statically, or "m" to build a |
| 266 | dynamically linked module called "pxa27x_udc" and force all |
| 267 | gadget drivers to also be dynamically linked. |
| 268 | |
| 269 | config USB_PXA27X |
| 270 | tristate |
| 271 | depends on USB_GADGET_PXA27X |
| 272 | default USB_GADGET |
| 273 | select USB_GADGET_SELECTED |
| 274 | |
Ben Dooks | 5b7d70c | 2009-06-02 14:58:06 +0100 | [diff] [blame] | 275 | config USB_GADGET_S3C_HSOTG |
| 276 | boolean "S3C HS/OtG USB Device controller" |
| 277 | depends on S3C_DEV_USB_HSOTG |
| 278 | select USB_GADGET_S3C_HSOTG_PIO |
| 279 | help |
| 280 | The Samsung S3C64XX USB2.0 high-speed gadget controller |
| 281 | integrated into the S3C64XX series SoC. |
| 282 | |
| 283 | config USB_S3C_HSOTG |
| 284 | tristate |
| 285 | depends on USB_GADGET_S3C_HSOTG |
| 286 | default USB_GADGET |
| 287 | select USB_GADGET_SELECTED |
| 288 | |
Arnaud Patard | 3fc154b | 2007-06-06 21:05:49 -0700 | [diff] [blame] | 289 | config USB_GADGET_S3C2410 |
| 290 | boolean "S3C2410 USB Device Controller" |
| 291 | depends on ARCH_S3C2410 |
| 292 | help |
| 293 | Samsung's S3C2410 is an ARM-4 processor with an integrated |
| 294 | full speed USB 1.1 device controller. It has 4 configurable |
| 295 | endpoints, as well as endpoint zero (for control transfers). |
| 296 | |
| 297 | This driver has been tested on the S3C2410, S3C2412, and |
| 298 | S3C2440 processors. |
| 299 | |
| 300 | config USB_S3C2410 |
| 301 | tristate |
| 302 | depends on USB_GADGET_S3C2410 |
| 303 | default USB_GADGET |
| 304 | select USB_GADGET_SELECTED |
| 305 | |
| 306 | config USB_S3C2410_DEBUG |
| 307 | boolean "S3C2410 udc debug messages" |
| 308 | depends on USB_GADGET_S3C2410 |
| 309 | |
David Brownell | a7a19fa | 2008-08-14 17:04:48 -0700 | [diff] [blame] | 310 | # |
| 311 | # Controllers available in both integrated and discrete versions |
| 312 | # |
| 313 | |
| 314 | # musb builds in ../musb along with host support |
| 315 | config USB_GADGET_MUSB_HDRC |
Bryan Wu | 085ad40 | 2008-12-02 21:33:49 +0200 | [diff] [blame] | 316 | boolean "Inventra HDRC USB Peripheral (TI, ADI, ...)" |
David Brownell | a7a19fa | 2008-08-14 17:04:48 -0700 | [diff] [blame] | 317 | depends on USB_MUSB_HDRC && (USB_MUSB_PERIPHERAL || USB_MUSB_OTG) |
| 318 | select USB_GADGET_DUALSPEED |
David Brownell | bae4bd8 | 2006-01-22 10:32:37 -0800 | [diff] [blame] | 319 | select USB_GADGET_SELECTED |
| 320 | help |
David Brownell | a7a19fa | 2008-08-14 17:04:48 -0700 | [diff] [blame] | 321 | This OTG-capable silicon IP is used in dual designs including |
Bryan Wu | 085ad40 | 2008-12-02 21:33:49 +0200 | [diff] [blame] | 322 | the TI DaVinci, OMAP 243x, OMAP 343x, TUSB 6010, and ADI Blackfin |
David Brownell | a7a19fa | 2008-08-14 17:04:48 -0700 | [diff] [blame] | 323 | |
Darius Augulis | 2a4f136 | 2008-11-12 13:38:31 -0800 | [diff] [blame] | 324 | config USB_GADGET_IMX |
| 325 | boolean "Freescale IMX USB Peripheral Controller" |
| 326 | depends on ARCH_MX1 |
| 327 | help |
| 328 | Freescale's IMX series include an integrated full speed |
| 329 | USB 1.1 device controller. The controller in the IMX series |
| 330 | is register-compatible. |
| 331 | |
| 332 | It has Six fixed-function endpoints, as well as endpoint |
| 333 | zero (for control transfers). |
| 334 | |
| 335 | Say "y" to link the driver statically, or "m" to build a |
| 336 | dynamically linked module called "imx_udc" and force all |
| 337 | gadget drivers to also be dynamically linked. |
| 338 | |
| 339 | config USB_IMX |
| 340 | tristate |
| 341 | depends on USB_GADGET_IMX |
| 342 | default USB_GADGET |
| 343 | select USB_GADGET_SELECTED |
| 344 | |
David Brownell | a7a19fa | 2008-08-14 17:04:48 -0700 | [diff] [blame] | 345 | config USB_GADGET_M66592 |
| 346 | boolean "Renesas M66592 USB Peripheral Controller" |
| 347 | select USB_GADGET_DUALSPEED |
| 348 | help |
| 349 | M66592 is a discrete USB peripheral controller chip that |
| 350 | supports both full and high speed USB 2.0 data transfers. |
| 351 | It has seven configurable endpoints, and endpoint zero. |
David Brownell | bae4bd8 | 2006-01-22 10:32:37 -0800 | [diff] [blame] | 352 | |
| 353 | Say "y" to link the driver statically, or "m" to build a |
David Brownell | a7a19fa | 2008-08-14 17:04:48 -0700 | [diff] [blame] | 354 | dynamically linked module called "m66592_udc" and force all |
David Brownell | bae4bd8 | 2006-01-22 10:32:37 -0800 | [diff] [blame] | 355 | gadget drivers to also be dynamically linked. |
| 356 | |
David Brownell | a7a19fa | 2008-08-14 17:04:48 -0700 | [diff] [blame] | 357 | config USB_M66592 |
David Brownell | bae4bd8 | 2006-01-22 10:32:37 -0800 | [diff] [blame] | 358 | tristate |
David Brownell | a7a19fa | 2008-08-14 17:04:48 -0700 | [diff] [blame] | 359 | depends on USB_GADGET_M66592 |
David Brownell | bae4bd8 | 2006-01-22 10:32:37 -0800 | [diff] [blame] | 360 | default USB_GADGET |
David Brownell | a7a19fa | 2008-08-14 17:04:48 -0700 | [diff] [blame] | 361 | select USB_GADGET_SELECTED |
| 362 | |
| 363 | config SUPERH_BUILT_IN_M66592 |
| 364 | boolean "Enable SuperH built-in USB like the M66592" |
| 365 | depends on USB_GADGET_M66592 && CPU_SUBTYPE_SH7722 |
| 366 | help |
| 367 | SH7722 has USB like the M66592. |
| 368 | |
| 369 | The transfer rate is very slow when use "Ethernet Gadget". |
| 370 | However, this problem is improved if change a value of |
| 371 | NET_IP_ALIGN to 4. |
| 372 | |
| 373 | # |
| 374 | # Controllers available only in discrete form (and all PCI controllers) |
| 375 | # |
| 376 | |
| 377 | config 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 | |
| 392 | config USB_AMD5536UDC |
| 393 | tristate |
| 394 | depends on USB_GADGET_AMD5536UDC |
| 395 | default USB_GADGET |
| 396 | select USB_GADGET_SELECTED |
| 397 | |
Li Yang | 3948f0e | 2008-09-02 19:58:10 +0800 | [diff] [blame] | 398 | config 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 |
Matt LaPlante | 692105b | 2009-01-26 11:12:25 +0100 | [diff] [blame] | 409 | dynamically linked module called "fsl_qe_udc". |
Li Yang | 3948f0e | 2008-09-02 19:58:10 +0800 | [diff] [blame] | 410 | |
| 411 | config USB_FSL_QE |
| 412 | tristate |
| 413 | depends on USB_GADGET_FSL_QE |
| 414 | default USB_GADGET |
| 415 | select USB_GADGET_SELECTED |
| 416 | |
David Lopo | aa69a80 | 2008-11-17 14:14:51 -0800 | [diff] [blame] | 417 | config 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 | |
| 429 | config USB_CI13XXX |
| 430 | tristate |
| 431 | depends on USB_GADGET_CI13XXX |
| 432 | default USB_GADGET |
| 433 | select USB_GADGET_SELECTED |
| 434 | |
David Brownell | a7a19fa | 2008-08-14 17:04:48 -0700 | [diff] [blame] | 435 | config 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 | |
| 451 | config USB_NET2280 |
| 452 | tristate |
| 453 | depends on USB_GADGET_NET2280 |
| 454 | default USB_GADGET |
| 455 | select USB_GADGET_SELECTED |
| 456 | |
| 457 | config 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 | |
| 471 | config USB_GOKU |
| 472 | tristate |
| 473 | depends on USB_GADGET_GOKU |
| 474 | default USB_GADGET |
| 475 | select USB_GADGET_SELECTED |
| 476 | |
Xiaochen Shen | 5be19a9 | 2009-06-04 15:34:49 +0800 | [diff] [blame] | 477 | config 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 | |
| 492 | config USB_LANGWELL |
| 493 | tristate |
| 494 | depends on USB_GADGET_LANGWELL |
| 495 | default USB_GADGET |
| 496 | select USB_GADGET_SELECTED |
| 497 | |
David Brownell | a7a19fa | 2008-08-14 17:04:48 -0700 | [diff] [blame] | 498 | |
| 499 | # |
| 500 | # LAST -- dummy/emulated controller |
| 501 | # |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 502 | |
| 503 | config USB_GADGET_DUMMY_HCD |
| 504 | boolean "Dummy HCD (DEVELOPMENT)" |
Robert P. J. Day | afd0e0f | 2008-03-10 15:09:51 -0400 | [diff] [blame] | 505 | depends on USB=y || (USB=m && USB_GADGET=m) |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 506 | select USB_GADGET_DUALSPEED |
| 507 | help |
| 508 | This host controller driver emulates USB, looping all data transfer |
| 509 | requests back to a USB "gadget driver" in the same host. The host |
| 510 | side is the master; the gadget side is the slave. Gadget drivers |
| 511 | can be high, full, or low speed; and they have access to endpoints |
| 512 | like those from NET2280, PXA2xx, or SA1100 hardware. |
| 513 | |
| 514 | This may help in some stages of creating a driver to embed in a |
| 515 | Linux device, since it lets you debug several parts of the gadget |
| 516 | driver without its hardware or drivers being involved. |
| 517 | |
| 518 | Since such a gadget side driver needs to interoperate with a host |
| 519 | side Linux-USB device driver, this may help to debug both sides |
| 520 | of a USB protocol stack. |
| 521 | |
| 522 | Say "y" to link the driver statically, or "m" to build a |
| 523 | dynamically linked module called "dummy_hcd" and force all |
| 524 | gadget drivers to also be dynamically linked. |
| 525 | |
| 526 | config USB_DUMMY_HCD |
| 527 | tristate |
| 528 | depends on USB_GADGET_DUMMY_HCD |
| 529 | default USB_GADGET |
David Brownell | 028b271 | 2005-05-06 07:02:01 -0700 | [diff] [blame] | 530 | select USB_GADGET_SELECTED |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 531 | |
| 532 | # NOTE: Please keep dummy_hcd LAST so that "real hardware" appears |
| 533 | # first and will be selected by default. |
| 534 | |
| 535 | endchoice |
| 536 | |
| 537 | config USB_GADGET_DUALSPEED |
| 538 | bool |
| 539 | depends on USB_GADGET |
| 540 | default n |
| 541 | help |
| 542 | Means that gadget drivers should include extra descriptors |
| 543 | and code to handle dual-speed controllers. |
| 544 | |
| 545 | # |
| 546 | # USB Gadget Drivers |
| 547 | # |
| 548 | choice |
| 549 | tristate "USB Gadget Drivers" |
David Brownell | 028b271 | 2005-05-06 07:02:01 -0700 | [diff] [blame] | 550 | depends on USB_GADGET && USB_GADGET_SELECTED |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 551 | default USB_ETH |
| 552 | help |
| 553 | A Linux "Gadget Driver" talks to the USB Peripheral Controller |
| 554 | driver through the abstract "gadget" API. Some other operating |
| 555 | systems call these "client" drivers, of which "class drivers" |
| 556 | are a subset (implementing a USB device class specification). |
| 557 | A gadget driver implements one or more USB functions using |
| 558 | the peripheral hardware. |
| 559 | |
| 560 | Gadget drivers are hardware-neutral, or "platform independent", |
| 561 | except that they sometimes must understand quirks or limitations |
| 562 | of the particular controllers they work with. For example, when |
| 563 | a controller doesn't support alternate configurations or provide |
| 564 | enough of the right types of endpoints, the gadget driver might |
| 565 | not be able work with that controller, or might need to implement |
| 566 | a less common variant of a device class protocol. |
| 567 | |
| 568 | # this first set of drivers all depend on bulk-capable hardware. |
| 569 | |
| 570 | config USB_ZERO |
| 571 | tristate "Gadget Zero (DEVELOPMENT)" |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 572 | help |
| 573 | Gadget Zero is a two-configuration device. It either sinks and |
| 574 | sources bulk data; or it loops back a configurable number of |
| 575 | transfers. It also implements control requests, for "chapter 9" |
| 576 | conformance. The driver needs only two bulk-capable endpoints, so |
| 577 | it can work on top of most device-side usb controllers. It's |
| 578 | useful for testing, and is also a working example showing how |
| 579 | USB "gadget drivers" can be written. |
| 580 | |
| 581 | Make this be the first driver you try using on top of any new |
| 582 | USB peripheral controller driver. Then you can use host-side |
| 583 | test software, like the "usbtest" driver, to put your hardware |
| 584 | and its driver through a basic set of functional tests. |
| 585 | |
| 586 | Gadget Zero also works with the host-side "usb-skeleton" driver, |
| 587 | and with many kinds of host-side test software. You may need |
| 588 | to tweak product and vendor IDs before host software knows about |
| 589 | this device, and arrange to select an appropriate configuration. |
| 590 | |
| 591 | Say "y" to link the driver statically, or "m" to build a |
| 592 | dynamically linked module called "g_zero". |
| 593 | |
| 594 | config USB_ZERO_HNPTEST |
| 595 | boolean "HNP Test Device" |
| 596 | depends on USB_ZERO && USB_OTG |
| 597 | help |
| 598 | You can configure this device to enumerate using the device |
| 599 | identifiers of the USB-OTG test device. That means that when |
| 600 | this gadget connects to another OTG device, with this one using |
| 601 | the "B-Peripheral" role, that device will use HNP to let this |
| 602 | one serve as the USB host instead (in the "B-Host" role). |
| 603 | |
Bryan Wu | c6994e6 | 2009-06-03 09:17:58 -0400 | [diff] [blame] | 604 | config USB_AUDIO |
| 605 | tristate "Audio Gadget (EXPERIMENTAL)" |
| 606 | depends on SND |
| 607 | help |
| 608 | Gadget Audio is compatible with USB Audio Class specification 1.0. |
| 609 | It will include at least one AudioControl interface, zero or more |
| 610 | AudioStream interface and zero or more MIDIStream interface. |
| 611 | |
| 612 | Gadget Audio will use on-board ALSA (CONFIG_SND) audio card to |
| 613 | playback or capture audio stream. |
| 614 | |
| 615 | Say "y" to link the driver statically, or "m" to build a |
| 616 | dynamically linked module called "g_audio". |
| 617 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 618 | config USB_ETH |
| 619 | tristate "Ethernet Gadget (with CDC Ethernet support)" |
| 620 | depends on NET |
| 621 | help |
| 622 | This driver implements Ethernet style communication, in either |
| 623 | of two ways: |
| 624 | |
| 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 | |
| 630 | - On hardware can't implement that protocol, a simple CDC subset |
| 631 | is used, placing fewer demands on USB. |
| 632 | |
| 633 | RNDIS support is a third option, more demanding than that subset. |
| 634 | |
| 635 | Within the USB device, this gadget driver exposes a network device |
| 636 | "usbX", where X depends on what other networking devices you have. |
| 637 | Treat it like a two-node Ethernet link: host, and gadget. |
| 638 | |
| 639 | The Linux-USB host-side "usbnet" driver interoperates with this |
| 640 | driver, so that deep I/O queues can be supported. On 2.4 kernels, |
| 641 | use "CDCEther" instead, if you're using the CDC option. That CDC |
| 642 | mode should also interoperate with standard CDC Ethernet class |
| 643 | drivers on other host operating systems. |
| 644 | |
| 645 | Say "y" to link the driver statically, or "m" to build a |
| 646 | dynamically linked module called "g_ether". |
| 647 | |
| 648 | config USB_ETH_RNDIS |
Robert P. J. Day | afd0e0f | 2008-03-10 15:09:51 -0400 | [diff] [blame] | 649 | bool "RNDIS support" |
| 650 | depends on USB_ETH |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 651 | default y |
| 652 | help |
| 653 | Microsoft Windows XP bundles the "Remote NDIS" (RNDIS) protocol, |
| 654 | and Microsoft provides redistributable binary RNDIS drivers for |
| 655 | older versions of Windows. |
| 656 | |
| 657 | If you say "y" here, the Ethernet gadget driver will try to provide |
| 658 | a second device configuration, supporting RNDIS to talk to such |
| 659 | Microsoft USB hosts. |
| 660 | |
| 661 | To make MS-Windows work with this, use Documentation/usb/linux.inf |
| 662 | as the "driver info file". For versions of MS-Windows older than |
| 663 | XP, you'll need to download drivers from Microsoft's website; a URL |
| 664 | is given in comments found in that info file. |
| 665 | |
| 666 | config USB_GADGETFS |
| 667 | tristate "Gadget Filesystem (EXPERIMENTAL)" |
| 668 | depends on EXPERIMENTAL |
| 669 | help |
| 670 | This driver provides a filesystem based API that lets user mode |
| 671 | programs implement a single-configuration USB device, including |
| 672 | endpoint I/O and control requests that don't relate to enumeration. |
| 673 | All endpoints, transfer speeds, and transfer types supported by |
| 674 | the hardware are available, through read() and write() calls. |
| 675 | |
Robert P. J. Day | afd0e0f | 2008-03-10 15:09:51 -0400 | [diff] [blame] | 676 | Currently, this option is still labelled as EXPERIMENTAL because |
| 677 | of existing race conditions in the underlying in-kernel AIO core. |
| 678 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 679 | Say "y" to link the driver statically, or "m" to build a |
| 680 | dynamically linked module called "gadgetfs". |
| 681 | |
| 682 | config USB_FILE_STORAGE |
| 683 | tristate "File-backed Storage Gadget" |
Randy Dunlap | 8784028 | 2007-03-21 13:57:51 -0700 | [diff] [blame] | 684 | depends on BLOCK |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 685 | help |
| 686 | The File-backed Storage Gadget acts as a USB Mass Storage |
| 687 | disk drive. As its storage repository it can use a regular |
| 688 | file or a block device (in much the same way as the "loop" |
| 689 | device driver), specified as a module parameter. |
| 690 | |
| 691 | Say "y" to link the driver statically, or "m" to build a |
| 692 | dynamically linked module called "g_file_storage". |
| 693 | |
| 694 | config USB_FILE_STORAGE_TEST |
| 695 | bool "File-backed Storage Gadget testing version" |
| 696 | depends on USB_FILE_STORAGE |
| 697 | default n |
| 698 | help |
| 699 | Say "y" to generate the larger testing version of the |
| 700 | File-backed Storage Gadget, useful for probing the |
| 701 | behavior of USB Mass Storage hosts. Not needed for |
| 702 | normal operation. |
| 703 | |
| 704 | config USB_G_SERIAL |
Felipe Balbi | 3086775 | 2008-08-18 17:39:30 -0700 | [diff] [blame] | 705 | tristate "Serial Gadget (with CDC ACM and CDC OBEX support)" |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 706 | help |
| 707 | The Serial Gadget talks to the Linux-USB generic serial driver. |
| 708 | This driver supports a CDC-ACM module option, which can be used |
| 709 | to interoperate with MS-Windows hosts or with the Linux-USB |
| 710 | "cdc-acm" driver. |
| 711 | |
Felipe Balbi | 3086775 | 2008-08-18 17:39:30 -0700 | [diff] [blame] | 712 | This driver also supports a CDC-OBEX option. You will need a |
| 713 | user space OBEX server talking to /dev/ttyGS*, since the kernel |
| 714 | itself doesn't implement the OBEX protocol. |
| 715 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 716 | Say "y" to link the driver statically, or "m" to build a |
| 717 | dynamically linked module called "g_serial". |
| 718 | |
| 719 | For more information, see Documentation/usb/gadget_serial.txt |
| 720 | which includes instructions and a "driver info file" needed to |
Felipe Balbi | 3086775 | 2008-08-18 17:39:30 -0700 | [diff] [blame] | 721 | make MS-Windows work with CDC ACM. |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 722 | |
Ben Williamson | f2ebf92c | 2006-08-01 11:28:16 +1000 | [diff] [blame] | 723 | config USB_MIDI_GADGET |
| 724 | tristate "MIDI Gadget (EXPERIMENTAL)" |
| 725 | depends on SND && EXPERIMENTAL |
| 726 | select SND_RAWMIDI |
| 727 | help |
| 728 | The MIDI Gadget acts as a USB Audio device, with one MIDI |
| 729 | input and one MIDI output. These MIDI jacks appear as |
| 730 | a sound "card" in the ALSA sound system. Other MIDI |
| 731 | connections can then be made on the gadget system, using |
| 732 | ALSA's aconnect utility etc. |
| 733 | |
| 734 | Say "y" to link the driver statically, or "m" to build a |
| 735 | dynamically linked module called "g_midi". |
| 736 | |
Craig W. Nadler | 25a010c | 2007-11-11 15:00:15 -0800 | [diff] [blame] | 737 | config USB_G_PRINTER |
| 738 | tristate "Printer Gadget" |
| 739 | help |
| 740 | The Printer Gadget channels data between the USB host and a |
| 741 | userspace program driving the print engine. The user space |
| 742 | program reads and writes the device file /dev/g_printer to |
| 743 | receive or send printer data. It can use ioctl calls to |
| 744 | the device file to get or set printer status. |
| 745 | |
| 746 | Say "y" to link the driver statically, or "m" to build a |
| 747 | dynamically linked module called "g_printer". |
| 748 | |
| 749 | For more information, see Documentation/usb/gadget_printer.txt |
| 750 | which includes sample code for accessing the device file. |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 751 | |
David Brownell | 19e2068 | 2008-06-19 18:20:26 -0700 | [diff] [blame] | 752 | config USB_CDC_COMPOSITE |
| 753 | tristate "CDC Composite Device (Ethernet and ACM)" |
Randy Dunlap | 4ddd9ec | 2008-07-03 14:44:59 -0700 | [diff] [blame] | 754 | depends on NET |
David Brownell | 19e2068 | 2008-06-19 18:20:26 -0700 | [diff] [blame] | 755 | help |
| 756 | This driver provides two functions in one configuration: |
| 757 | a CDC Ethernet (ECM) link, and a CDC ACM (serial port) link. |
| 758 | |
| 759 | This driver requires four bulk and two interrupt endpoints, |
| 760 | plus the ability to handle altsettings. Not all peripheral |
| 761 | controllers are that capable. |
| 762 | |
| 763 | Say "y" to link the driver statically, or "m" to build a |
| 764 | dynamically linked module. |
| 765 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 766 | # put drivers that need isochronous transfer support (for audio |
| 767 | # or video class gadget drivers), or specific hardware, here. |
| 768 | |
| 769 | # - none yet |
| 770 | |
| 771 | endchoice |
| 772 | |
Denis Cheng | b75be4a | 2008-01-24 16:36:31 +0800 | [diff] [blame] | 773 | endif # USB_GADGET |