4.17-stable review patch.  If anyone has any objections, please let me know.

------------------

From: Yoshihiro Shimoda <yoshihiro.shimoda...@renesas.com>

commit 003bc1dee216b1fb8e02040a95672bea0f1fe797 upstream.

This patch fixes an issue that this driver cannot call phy_init()
if a gadget driver is alreadly loaded because usb_add_gadget_udc()
might call renesas_usb3_start() via .udc_start.
This patch also revises the typo (s/an optional/optional/).

Fixes: 279d4bc64060 ("usb: gadget: udc: renesas_usb3: add support for generic 
phy")
Cc: <sta...@vger.kernel.org> # v4.15+
Signed-off-by: Yoshihiro Shimoda <yoshihiro.shimoda...@renesas.com>
Reviewed-by: Simon Horman <horms+rene...@verge.net.au>
Signed-off-by: Felipe Balbi <felipe.ba...@linux.intel.com>
Signed-off-by: Greg Kroah-Hartman <gre...@linuxfoundation.org>

---
 drivers/usb/gadget/udc/renesas_usb3.c |   16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)

--- a/drivers/usb/gadget/udc/renesas_usb3.c
+++ b/drivers/usb/gadget/udc/renesas_usb3.c
@@ -2632,6 +2632,14 @@ static int renesas_usb3_probe(struct pla
        if (ret < 0)
                goto err_alloc_prd;
 
+       /*
+        * This is optional. So, if this driver cannot get a phy,
+        * this driver will not handle a phy anymore.
+        */
+       usb3->phy = devm_phy_get(&pdev->dev, "usb");
+       if (IS_ERR(usb3->phy))
+               usb3->phy = NULL;
+
        pm_runtime_enable(&pdev->dev);
        ret = usb_add_gadget_udc(&pdev->dev, &usb3->gadget);
        if (ret < 0)
@@ -2641,14 +2649,6 @@ static int renesas_usb3_probe(struct pla
        if (ret < 0)
                goto err_dev_create;
 
-       /*
-        * This is an optional. So, if this driver cannot get a phy,
-        * this driver will not handle a phy anymore.
-        */
-       usb3->phy = devm_phy_get(&pdev->dev, "usb");
-       if (IS_ERR(usb3->phy))
-               usb3->phy = NULL;
-
        usb3->workaround_for_vbus = priv->workaround_for_vbus;
 
        renesas_usb3_debugfs_init(usb3, &pdev->dev);


Reply via email to