> From: Marek Szyprowski [mailto:m.szyprow...@samsung.com]
> Sent: Monday, October 20, 2014 3:46 AM
> 
> This patch moves phy enable/disable calls from pullup() method to
> udc_start/stop functions. This solves the issue related to limited caller
> context for PHY functions, because they cannot be called from non-sleeping
> context. This is also a preparation for using soft-disconnect feature of
> udc controller in pullup() method.
> 
> Signed-off-by: Marek Szyprowski <m.szyprow...@samsung.com>
> ---
>  drivers/usb/dwc2/gadget.c | 6 ++++--
>  1 file changed, 4 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/usb/dwc2/gadget.c b/drivers/usb/dwc2/gadget.c
> index 5eb2473031c4..98adf8d17493 100644
> --- a/drivers/usb/dwc2/gadget.c
> +++ b/drivers/usb/dwc2/gadget.c
> @@ -2919,6 +2919,8 @@ static int s3c_hsotg_udc_start(struct usb_gadget 
> *gadget,
>               goto err;
>       }
> 
> +     s3c_hsotg_phy_enable(hsotg);
> +
>       dev_info(hsotg->dev, "bound driver %s\n", driver->driver.name);
>       return 0;
> 
> @@ -2955,6 +2957,8 @@ static int s3c_hsotg_udc_stop(struct usb_gadget *gadget,
> 
>       spin_unlock_irqrestore(&hsotg->lock, flags);
> 
> +     s3c_hsotg_phy_disable(hsotg);
> +
>       regulator_bulk_disable(ARRAY_SIZE(hsotg->supplies), hsotg->supplies);
> 
>       clk_disable(hsotg->clk);
> @@ -2989,13 +2993,11 @@ static int s3c_hsotg_pullup(struct usb_gadget 
> *gadget, int is_on)
> 
>       spin_lock_irqsave(&hsotg->lock, flags);
>       if (is_on) {
> -             s3c_hsotg_phy_enable(hsotg);
>               clk_enable(hsotg->clk);
>               s3c_hsotg_core_init_disconnected(hsotg);
>               s3c_hsotg_core_connect(hsotg);
>       } else {
>               clk_disable(hsotg->clk);
> -             s3c_hsotg_phy_disable(hsotg);
>       }
> 
>       hsotg->gadget.speed = USB_SPEED_UNKNOWN;

Acked-by: Paul Zimmerman <pa...@synopsys.com>

--
To unsubscribe from this list: send the line "unsubscribe linux-usb" 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