DWC3 controller on Exynos SoC series have separate control for
suspend clock which replaces pipe3_rx_pclk as clock source to
a small part of DWC3 core that operates when SS PHY is in its
lowest power state (P3) in states SS.disabled and U3.

Suggested-by: Anton Tikhomirov <av.tikhomi...@samsung.com>
Signed-off-by: Vivek Gautam <gautam.vi...@samsung.com>
---
 drivers/usb/dwc3/dwc3-exynos.c |   11 +++++++++++
 1 file changed, 11 insertions(+)

diff --git a/drivers/usb/dwc3/dwc3-exynos.c b/drivers/usb/dwc3/dwc3-exynos.c
index 7109de7..af15ab3 100644
--- a/drivers/usb/dwc3/dwc3-exynos.c
+++ b/drivers/usb/dwc3/dwc3-exynos.c
@@ -35,6 +35,8 @@ struct dwc3_exynos {
        struct device           *dev;
 
        struct clk              *clk;
+       struct clk              *susp_clk;
+
        struct regulator        *vdd33;
        struct regulator        *vdd10;
 };
@@ -141,6 +143,13 @@ static int dwc3_exynos_probe(struct platform_device *pdev)
        }
        clk_prepare_enable(exynos->clk);
 
+       exynos->susp_clk = devm_clk_get(dev, "usbdrd30_susp_clk");
+       if (IS_ERR(exynos->susp_clk)) {
+               dev_dbg(dev, "no suspend clk specified\n");
+               exynos->susp_clk = NULL;
+       }
+       clk_prepare_enable(exynos->susp_clk);
+
        exynos->vdd33 = devm_regulator_get(dev, "vdd33");
        if (IS_ERR(exynos->vdd33)) {
                ret = PTR_ERR(exynos->vdd33);
@@ -182,6 +191,7 @@ err4:
 err3:
        regulator_disable(exynos->vdd33);
 err2:
+       clk_disable_unprepare(exynos->susp_clk);
        clk_disable_unprepare(exynos->clk);
        return ret;
 }
@@ -194,6 +204,7 @@ static int dwc3_exynos_remove(struct platform_device *pdev)
        platform_device_unregister(exynos->usb2_phy);
        platform_device_unregister(exynos->usb3_phy);
 
+       clk_disable_unprepare(exynos->susp_clk);
        clk_disable_unprepare(exynos->clk);
 
        regulator_disable(exynos->vdd33);
-- 
1.7.10.4

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