Skip to content

Commit 90fccb5

Browse files
Andrzej PietrasiewiczFelipe Balbi
authored andcommitted
usb: gadget: Gadget directory cleanup - group UDC drivers
The drivers/usb/gadget directory contains many files. Files which are related can be distributed into separate directories. This patch moves the UDC drivers into a separate directory. Signed-off-by: Andrzej Pietrasiewicz <[email protected]> Signed-off-by: Felipe Balbi <[email protected]>
1 parent 8443f2d commit 90fccb5

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

51 files changed

+420
-399
lines changed

drivers/usb/gadget/Kconfig

Lines changed: 1 addition & 370 deletions
Original file line numberDiff line numberDiff line change
@@ -127,376 +127,7 @@ config USB_GADGET_STORAGE_NUM_BUFFERS
127127
a module parameter as well.
128128
If unsure, say 2.
129129

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-
#
140-
menu "USB Peripheral Controller"
141-
142-
#
143-
# Integrated controllers
144-
#
145-
146-
config 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-
158-
config USB_LPC32XX
159-
tristate "LPC32XX USB Peripheral Controller"
160-
depends on ARCH_LPC32XX && I2C
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-
169-
config 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-
176-
config 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-
187-
config 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-
202-
config 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-
208-
config 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-
219-
config USB_GR_UDC
220-
tristate "Aeroflex Gaisler GRUSBDC USB Peripheral Controller Driver"
221-
depends on HAS_DMA
222-
help
223-
Select this to support Aeroflex Gaisler GRUSBDC cores from the GRLIB
224-
VHDL IP core library.
225-
226-
config USB_OMAP
227-
tristate "OMAP USB Device Controller"
228-
depends on ARCH_OMAP1
229-
depends on ISP1301_OMAP || !(MACH_OMAP_H2 || MACH_OMAP_H3)
230-
help
231-
Many Texas Instruments OMAP processors have flexible full
232-
speed USB device controllers, with support for up to 30
233-
endpoints (plus endpoint zero). This driver supports the
234-
controller in the OMAP 1611, and should work with controllers
235-
in other OMAP processors too, given minor tweaks.
236-
237-
Say "y" to link the driver statically, or "m" to build a
238-
dynamically linked module called "omap_udc" and force all
239-
gadget drivers to also be dynamically linked.
240-
241-
config USB_PXA25X
242-
tristate "PXA 25x or IXP 4xx"
243-
depends on (ARCH_PXA && PXA25x) || ARCH_IXP4XX
244-
help
245-
Intel's PXA 25x series XScale ARM-5TE processors include
246-
an integrated full speed USB 1.1 device controller. The
247-
controller in the IXP 4xx series is register-compatible.
248-
249-
It has fifteen fixed-function endpoints, as well as endpoint
250-
zero (for control transfers).
251-
252-
Say "y" to link the driver statically, or "m" to build a
253-
dynamically linked module called "pxa25x_udc" and force all
254-
gadget drivers to also be dynamically linked.
255-
256-
# if there's only one gadget driver, using only two bulk endpoints,
257-
# don't waste memory for the other endpoints
258-
config USB_PXA25X_SMALL
259-
depends on USB_PXA25X
260-
bool
261-
default n if USB_ETH_RNDIS
262-
default y if USB_ZERO
263-
default y if USB_ETH
264-
default y if USB_G_SERIAL
265-
266-
config USB_R8A66597
267-
tristate "Renesas R8A66597 USB Peripheral Controller"
268-
depends on HAS_DMA
269-
help
270-
R8A66597 is a discrete USB host and peripheral controller chip that
271-
supports both full and high speed USB 2.0 data transfers.
272-
It has nine configurable endpoints, and endpoint zero.
273-
274-
Say "y" to link the driver statically, or "m" to build a
275-
dynamically linked module called "r8a66597_udc" and force all
276-
gadget drivers to also be dynamically linked.
277-
278-
config USB_RENESAS_USBHS_UDC
279-
tristate 'Renesas USBHS controller'
280-
depends on USB_RENESAS_USBHS
281-
help
282-
Renesas USBHS is a discrete USB host and peripheral controller chip
283-
that supports both full and high speed USB 2.0 data transfers.
284-
It has nine or more configurable endpoints, and endpoint zero.
285-
286-
Say "y" to link the driver statically, or "m" to build a
287-
dynamically linked module called "renesas_usbhs" and force all
288-
gadget drivers to also be dynamically linked.
289-
290-
config USB_PXA27X
291-
tristate "PXA 27x"
292-
help
293-
Intel's PXA 27x series XScale ARM v5TE processors include
294-
an integrated full speed USB 1.1 device controller.
295-
296-
It has up to 23 endpoints, as well as endpoint zero (for
297-
control transfers).
298-
299-
Say "y" to link the driver statically, or "m" to build a
300-
dynamically linked module called "pxa27x_udc" and force all
301-
gadget drivers to also be dynamically linked.
302-
303-
config 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-
314-
config USB_S3C2410_DEBUG
315-
boolean "S3C2410 udc debug messages"
316-
depends on USB_S3C2410
317-
318-
config 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-
328-
config 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-
336-
config 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-
347-
config 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-
362-
config 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-
376-
config 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-
389-
config 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-
401-
config 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-
411-
config USB_NET2280
412-
tristate "NetChip 228x / PLX USB338x"
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-
PLX 3380 / 3382 is a PCIe based USB peripheral controller which
423-
supports full, high speed USB 2.0 and super speed USB 3.0
424-
data transfers.
425-
426-
It has eight configurable endpoints, as well as endpoint zero
427-
(for control transfers) and several endpoints with dedicated
428-
functions.
429-
430-
Say "y" to link the driver statically, or "m" to build a
431-
dynamically linked module called "net2280" and force all
432-
gadget drivers to also be dynamically linked.
433-
434-
config USB_GOKU
435-
tristate "Toshiba TC86C001 'Goku-S'"
436-
depends on PCI
437-
help
438-
The Toshiba TC86C001 is a PCI device which includes controllers
439-
for full speed USB devices, IDE, I2C, SIO, plus a USB host (OHCI).
440-
441-
The device controller has three configurable (bulk or interrupt)
442-
endpoints, plus endpoint zero (for control transfers).
443-
444-
Say "y" to link the driver statically, or "m" to build a
445-
dynamically linked module called "goku_udc" and to force all
446-
gadget drivers to also be dynamically linked.
447-
448-
config USB_EG20T
449-
tristate "Intel EG20T PCH/LAPIS Semiconductor IOH(ML7213/ML7831) UDC"
450-
depends on PCI
451-
help
452-
This is a USB device driver for EG20T PCH.
453-
EG20T PCH is the platform controller hub that is used in Intel's
454-
general embedded platform. EG20T PCH has USB device interface.
455-
Using this interface, it is able to access system devices connected
456-
to USB device.
457-
This driver enables USB device function.
458-
USB device is a USB peripheral controller which
459-
supports both full and high speed USB 2.0 data transfers.
460-
This driver supports both control transfer and bulk transfer modes.
461-
This driver dose not support interrupt transfer or isochronous
462-
transfer modes.
463-
464-
This driver also can be used for LAPIS Semiconductor's ML7213 which is
465-
for IVI(In-Vehicle Infotainment) use.
466-
ML7831 is for general purpose use.
467-
ML7213/ML7831 is companion chip for Intel Atom E6xx series.
468-
ML7213/ML7831 is completely compatible for Intel EG20T PCH.
469-
470-
#
471-
# LAST -- dummy/emulated controller
472-
#
473-
474-
config USB_DUMMY_HCD
475-
tristate "Dummy HCD (DEVELOPMENT)"
476-
depends on USB=y || (USB=m && USB_GADGET=m)
477-
help
478-
This host controller driver emulates USB, looping all data transfer
479-
requests back to a USB "gadget driver" in the same host. The host
480-
side is the master; the gadget side is the slave. Gadget drivers
481-
can be high, full, or low speed; and they have access to endpoints
482-
like those from NET2280, PXA2xx, or SA1100 hardware.
483-
484-
This may help in some stages of creating a driver to embed in a
485-
Linux device, since it lets you debug several parts of the gadget
486-
driver without its hardware or drivers being involved.
487-
488-
Since such a gadget side driver needs to interoperate with a host
489-
side Linux-USB device driver, this may help to debug both sides
490-
of a USB protocol stack.
491-
492-
Say "y" to link the driver statically, or "m" to build a
493-
dynamically linked module called "dummy_hcd" and force all
494-
gadget drivers to also be dynamically linked.
495-
496-
# NOTE: Please keep dummy_hcd LAST so that "real hardware" appears
497-
# first and will be selected by default.
498-
499-
endmenu
130+
source "drivers/usb/gadget/udc/Kconfig"
500131

501132
#
502133
# USB Gadget Drivers

0 commit comments

Comments
 (0)