e006fee6ec
Update DWC2 kconfig and makefile to support dual-role mode. The platform file will always get compiled for the case where the controller is directly connected to the CPU. So for loadable modules, only dwc2.ko is needed. Signed-off-by: Dinh Nguyen <dinguyen@opensource.altera.com> Acked-by: Paul Zimmerman <paulz@synopsys.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
96 lines
3.0 KiB
Plaintext
96 lines
3.0 KiB
Plaintext
config USB_DWC2
|
|
tristate "DesignWare USB2 DRD Core Support"
|
|
depends on USB
|
|
help
|
|
Say Y here if your system has a Dual Role Hi-Speed USB
|
|
controller based on the DesignWare HSOTG IP Core.
|
|
|
|
If you choose to build the driver as dynamically
|
|
linked modules, a single dwc2.ko(regardless of mode of operation)
|
|
will get built for both platform IPs and PCI.
|
|
|
|
if USB_DWC2
|
|
|
|
choice
|
|
bool "DWC2 Mode Selection"
|
|
default USB_DWC2_DUAL_ROLE if (USB && USB_GADGET)
|
|
default USB_DWC2_HOST if (USB && !USB_GADGET)
|
|
default USB_DWC2_PERIPHERAL if (!USB && USB_GADGET)
|
|
|
|
config USB_DWC2_HOST
|
|
bool "Host only mode"
|
|
depends on USB
|
|
help
|
|
The Designware USB2.0 high-speed host controller
|
|
integrated into many SoCs. Select this option if you want the
|
|
driver to operate in Host-only mode.
|
|
|
|
config USB_DWC2_PCI
|
|
bool "DWC2 PCI"
|
|
depends on USB_DWC2_HOST && PCI
|
|
default USB_DWC2_HOST
|
|
help
|
|
The Designware USB2.0 PCI interface module for controllers
|
|
connected to a PCI bus. This is only used for host mode.
|
|
|
|
comment "Gadget mode requires USB Gadget support to be enabled"
|
|
|
|
config USB_DWC2_PERIPHERAL
|
|
bool "Gadget only mode"
|
|
depends on USB_GADGET=y || USB_GADGET=USB_DWC2
|
|
help
|
|
The Designware USB2.0 high-speed gadget controller
|
|
integrated into many SoCs. Select this option if you want the
|
|
driver to operate in Peripheral-only mode. This option requires
|
|
USB_GADGET=y.
|
|
|
|
config USB_DWC2_DUAL_ROLE
|
|
bool "Dual Role mode"
|
|
depends on ((USB=y || USB=USB_DWC2) && (USB_GADGET=y || USB_GADGET=USB_DWC2))
|
|
help
|
|
Select this option if you want the driver to work in a dual-role
|
|
mode. In this mode both host and gadget features are enabled, and
|
|
the role will be determined by the cable that gets plugged-in. This
|
|
option requires USB_GADGET=y.
|
|
endchoice
|
|
|
|
config USB_DWC2_PLATFORM
|
|
bool
|
|
depends on !PCI
|
|
default y
|
|
help
|
|
The Designware USB2.0 platform interface module for
|
|
controllers directly connected to the CPU.
|
|
|
|
config USB_DWC2_DEBUG
|
|
bool "Enable Debugging Messages"
|
|
help
|
|
Say Y here to enable debugging messages in the DWC2 Driver.
|
|
|
|
config USB_DWC2_VERBOSE
|
|
bool "Enable Verbose Debugging Messages"
|
|
depends on USB_DWC2_DEBUG
|
|
help
|
|
Say Y here to enable verbose debugging messages in the DWC2 Driver.
|
|
WARNING: Enabling this will quickly fill your message log.
|
|
If in doubt, say N.
|
|
|
|
config USB_DWC2_TRACK_MISSED_SOFS
|
|
bool "Enable Missed SOF Tracking"
|
|
help
|
|
Say Y here to enable logging of missed SOF events to the dmesg log.
|
|
WARNING: This feature is still experimental.
|
|
If in doubt, say N.
|
|
|
|
config USB_DWC2_DEBUG_PERIODIC
|
|
bool "Enable Debugging Messages For Periodic Transfers"
|
|
depends on USB_DWC2_DEBUG || USB_DWC2_VERBOSE
|
|
default y
|
|
help
|
|
Say N here to disable (verbose) debugging messages to be
|
|
logged for periodic transfers. This allows better debugging of
|
|
non-periodic transfers, but of course the debug logs will be
|
|
incomplete. Note that this also disables some debug messages
|
|
for which the transfer type cannot be deduced.
|
|
endif
|