usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 22:10:58 +07:00
|
|
|
config USB_DWC3
|
|
|
|
|
tristate "DesignWare USB3 DRD Core Support"
|
2013-08-30 14:39:53 +07:00
|
|
|
depends on (USB || USB_GADGET) && HAS_DMA
|
2012-05-11 17:23:40 +07:00
|
|
|
select USB_XHCI_PLATFORM if USB_SUPPORT && USB_XHCI_HCD
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 22:10:58 +07:00
|
|
|
help
|
|
|
|
|
Say Y or M here if your system has a Dual Role SuperSpeed
|
|
|
|
|
USB controller based on the DesignWare USB3 IP Core.
|
|
|
|
|
|
|
|
|
|
If you choose to build this driver is a dynamically linked
|
|
|
|
|
module, the module will be called dwc3.ko.
|
|
|
|
|
|
|
|
|
|
if USB_DWC3
|
|
|
|
|
|
2013-01-15 17:39:21 +07:00
|
|
|
choice
|
|
|
|
|
bool "DWC3 Mode Selection"
|
|
|
|
|
default USB_DWC3_DUAL_ROLE if (USB && USB_GADGET)
|
|
|
|
|
default USB_DWC3_HOST if (USB && !USB_GADGET)
|
|
|
|
|
default USB_DWC3_GADGET if (!USB && USB_GADGET)
|
|
|
|
|
|
|
|
|
|
config USB_DWC3_HOST
|
|
|
|
|
bool "Host only mode"
|
2013-05-14 19:02:16 +07:00
|
|
|
depends on USB=y || USB=USB_DWC3
|
2013-01-15 17:39:21 +07:00
|
|
|
help
|
|
|
|
|
Select this when you want to use DWC3 in host mode only,
|
|
|
|
|
thereby the gadget feature will be regressed.
|
|
|
|
|
|
|
|
|
|
config USB_DWC3_GADGET
|
|
|
|
|
bool "Gadget only mode"
|
2013-05-14 19:02:16 +07:00
|
|
|
depends on USB_GADGET=y || USB_GADGET=USB_DWC3
|
2013-01-15 17:39:21 +07:00
|
|
|
help
|
|
|
|
|
Select this when you want to use DWC3 in gadget mode only,
|
|
|
|
|
thereby the host feature will be regressed.
|
|
|
|
|
|
|
|
|
|
config USB_DWC3_DUAL_ROLE
|
|
|
|
|
bool "Dual Role mode"
|
2013-05-14 19:02:16 +07:00
|
|
|
depends on ((USB=y || USB=USB_DWC3) && (USB_GADGET=y || USB_GADGET=USB_DWC3))
|
2013-01-15 17:39:21 +07:00
|
|
|
help
|
|
|
|
|
This is the default mode of working of DWC3 controller where
|
|
|
|
|
both host and gadget features are enabled.
|
|
|
|
|
|
|
|
|
|
endchoice
|
|
|
|
|
|
2013-06-26 19:14:06 +07:00
|
|
|
comment "Platform Glue Driver Support"
|
|
|
|
|
|
|
|
|
|
config USB_DWC3_OMAP
|
|
|
|
|
tristate "Texas Instruments OMAP5 and similar Platforms"
|
|
|
|
|
depends on EXTCON
|
|
|
|
|
default USB_DWC3
|
|
|
|
|
help
|
|
|
|
|
Some platforms from Texas Instruments like OMAP5, DRA7xxx and
|
|
|
|
|
AM437x use this IP for USB2/3 functionality.
|
|
|
|
|
|
|
|
|
|
Say 'Y' or 'M' here if you have one such device
|
|
|
|
|
|
|
|
|
|
config USB_DWC3_EXYNOS
|
|
|
|
|
tristate "Samsung Exynos Platform"
|
|
|
|
|
default USB_DWC3
|
|
|
|
|
help
|
|
|
|
|
Recent Exynos5 SoCs ship with one DesignWare Core USB3 IP inside,
|
|
|
|
|
say 'Y' or 'M' if you have one such device.
|
|
|
|
|
|
|
|
|
|
config USB_DWC3_PCI
|
|
|
|
|
tristate "PCIe-based Platforms"
|
|
|
|
|
depends on PCI
|
|
|
|
|
default USB_DWC3
|
|
|
|
|
help
|
|
|
|
|
If you're using the DesignWare Core IP with a PCIe, please say
|
|
|
|
|
'Y' or 'M' here.
|
|
|
|
|
|
|
|
|
|
One such PCIe-based platform is Synopsys' PCIe HAPS model of
|
|
|
|
|
this IP.
|
|
|
|
|
|
|
|
|
|
comment "Debugging features"
|
|
|
|
|
|
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 22:10:58 +07:00
|
|
|
config USB_DWC3_DEBUG
|
|
|
|
|
bool "Enable Debugging Messages"
|
|
|
|
|
help
|
|
|
|
|
Say Y here to enable debugging messages on DWC3 Driver.
|
|
|
|
|
|
|
|
|
|
config USB_DWC3_VERBOSE
|
|
|
|
|
bool "Enable Verbose Debugging Messages"
|
|
|
|
|
depends on USB_DWC3_DEBUG
|
|
|
|
|
help
|
|
|
|
|
Say Y here to enable verbose debugging messages on DWC3 Driver.
|
|
|
|
|
|
|
|
|
|
endif
|