Now that machines may select the mode of working of DWC3 (HOST only,
GADGET only or DUAL_ROLE), lets set DWC3 mode based on that
rather than fixing it to whatever DWC3 hardware says.
This way we can skip initializing Gadget/Host in case
we are using Host-only/Gadget-only mode respectively.

Signed-off-by: Vivek Gautam <gautam.vi...@samsung.com>
---

Changes from RFC patch "usb: dwc3: Set GCTL.PrtCapDir based on selected mode"
 - Setting the mode in dwc3 context structure based on
   selected mode in machine, rather than programming PrtCapDir

 drivers/usb/dwc3/core.c |    7 ++++++-
 1 files changed, 6 insertions(+), 1 deletions(-)

diff --git a/drivers/usb/dwc3/core.c b/drivers/usb/dwc3/core.c
index 79f335f..be0672f 100644
--- a/drivers/usb/dwc3/core.c
+++ b/drivers/usb/dwc3/core.c
@@ -478,7 +478,12 @@ static int dwc3_probe(struct platform_device *pdev)
                goto err1;
        }
 
-       mode = DWC3_MODE(dwc->hwparams.hwparams0);
+       if (IS_ENABLED(CONFIG_USB_DWC3_HOST))
+               mode = DWC3_MODE_HOST;
+       else if (IS_ENABLED(CONFIG_USB_DWC3_GADGET))
+               mode = DWC3_MODE_DEVICE;
+       else
+               mode = DWC3_MODE_DRD;
 
        switch (mode) {
        case DWC3_MODE_DEVICE:
-- 
1.7.6.5

--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to