Re: [PATCH v3 1/2] usb: ehci-exynos: Make provision for vdd regulators

2015-05-31 Thread Krzysztof Kozlowski
2014-06-25 21:42 GMT+09:00 Vivek Gautam gautam.vi...@samsung.com:
 Facilitate getting required 3.3V and 1.0V VDD supply for
 EHCI controller on Exynos.

 With the patches for regulators' nodes merged in 3.15:
 c8c253f ARM: dts: Add regulator entries to smdk5420
 275dcd2 ARM: dts: add max77686 pmic node for smdk5250,
 the exynos systems turn on only minimal number of regulators.

 Until now, the VDD regulator supplies were either turned on
 by the bootloader, or the regulators were enabled by default
 in the kernel, so that the controller drivers did not need to
 care about turning on these regulators on their own.
 This was rather bad about these controller drivers.
 So ensuring now that the controller driver requests the necessary
 VDD regulators (if available, unless there are direct VDD rails),
 and enable them so as to make them working.

 Signed-off-by: Vivek Gautam gautam.vi...@samsung.com
 Cc: Jingoo Han jg1@samsung.com
 Cc: Alan Stern st...@rowland.harvard.edu
 ---

 Changes from v2:
  - replaced devm_regulator_get() with devm_regulator_get_optional().
  - Added Documentation for the vdd supplies for the controller.
  - Re-did the commit message.

The patch looks useful but it seems it was forgotten. Do you have any
plans to resend it?

Best regards,
Krzysztof
--
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


[PATCH v3 1/2] usb: ehci-exynos: Make provision for vdd regulators

2014-06-25 Thread Vivek Gautam
Facilitate getting required 3.3V and 1.0V VDD supply for
EHCI controller on Exynos.

With the patches for regulators' nodes merged in 3.15:
c8c253f ARM: dts: Add regulator entries to smdk5420
275dcd2 ARM: dts: add max77686 pmic node for smdk5250,
the exynos systems turn on only minimal number of regulators.

Until now, the VDD regulator supplies were either turned on
by the bootloader, or the regulators were enabled by default
in the kernel, so that the controller drivers did not need to
care about turning on these regulators on their own.
This was rather bad about these controller drivers.
So ensuring now that the controller driver requests the necessary
VDD regulators (if available, unless there are direct VDD rails),
and enable them so as to make them working.

Signed-off-by: Vivek Gautam gautam.vi...@samsung.com
Cc: Jingoo Han jg1@samsung.com
Cc: Alan Stern st...@rowland.harvard.edu
---

Changes from v2:
 - replaced devm_regulator_get() with devm_regulator_get_optional().
 - Added Documentation for the vdd supplies for the controller.
 - Re-did the commit message.

 .../devicetree/bindings/usb/exynos-usb.txt |2 +
 drivers/usb/host/ehci-exynos.c |   55 +++-
 2 files changed, 56 insertions(+), 1 deletion(-)

diff --git a/Documentation/devicetree/bindings/usb/exynos-usb.txt 
b/Documentation/devicetree/bindings/usb/exynos-usb.txt
index a3b5990..b04b015 100644
--- a/Documentation/devicetree/bindings/usb/exynos-usb.txt
+++ b/Documentation/devicetree/bindings/usb/exynos-usb.txt
@@ -23,6 +23,8 @@ Required properties:
 Optional properties:
  - samsung,vbus-gpio:  if present, specifies the GPIO that
needs to be pulled up for the bus to be powered.
+ - vdd33-supply: handle to 3.3V Vdd supply regulator for the controller.
+ - vdd10-supply: handle to 1.0V Vdd supply regulator for the controller.
 
 Example:
 
diff --git a/drivers/usb/host/ehci-exynos.c b/drivers/usb/host/ehci-exynos.c
index d1c7621..b920642 100644
--- a/drivers/usb/host/ehci-exynos.c
+++ b/drivers/usb/host/ehci-exynos.c
@@ -21,6 +21,7 @@
 #include linux/of_gpio.h
 #include linux/phy/phy.h
 #include linux/platform_device.h
+#include linux/regulator/consumer.h
 #include linux/usb/phy.h
 #include linux/usb/samsung_usb_phy.h
 #include linux/usb.h
@@ -50,6 +51,8 @@ struct exynos_ehci_hcd {
struct usb_phy *phy;
struct usb_otg *otg;
struct phy *phy_g[PHY_NUMBER];
+   struct regulator *vdd33;
+   struct regulator *vdd10;
 };
 
 #define to_exynos_ehci(hcd) (struct exynos_ehci_hcd *)(hcd_to_ehci(hcd)-priv)
@@ -193,7 +196,27 @@ static int exynos_ehci_probe(struct platform_device *pdev)
 
err = exynos_ehci_get_phy(pdev-dev, exynos_ehci);
if (err)
-   goto fail_clk;
+   goto fail_regulator1;
+
+   exynos_ehci-vdd33 = devm_regulator_get_optional(pdev-dev, vdd33);
+   if (!IS_ERR(exynos_ehci-vdd33)) {
+   err = regulator_enable(exynos_ehci-vdd33);
+   if (err) {
+   dev_err(pdev-dev,
+   Failed to enable 3.3V Vdd supply\n);
+   goto fail_regulator1;
+   }
+   }
+
+   exynos_ehci-vdd10 = devm_regulator_get_optional(pdev-dev, vdd10);
+   if (!IS_ERR(exynos_ehci-vdd10)) {
+   err = regulator_enable(exynos_ehci-vdd10);
+   if (err) {
+   dev_err(pdev-dev,
+   Failed to enable 1.0V Vdd supply\n);
+   goto fail_regulator2;
+   }
+   }
 
 skip_phy:
 
@@ -262,6 +285,10 @@ fail_add_hcd:
 fail_io:
clk_disable_unprepare(exynos_ehci-clk);
 fail_clk:
+   regulator_disable(exynos_ehci-vdd10);
+fail_regulator2:
+   regulator_disable(exynos_ehci-vdd33);
+fail_regulator1:
usb_put_hcd(hcd);
return err;
 }
@@ -280,6 +307,11 @@ static int exynos_ehci_remove(struct platform_device *pdev)
 
clk_disable_unprepare(exynos_ehci-clk);
 
+   if (!IS_ERR(exynos_ehci-vdd33))
+   regulator_disable(exynos_ehci-vdd33);
+   if (!IS_ERR(exynos_ehci-vdd10))
+   regulator_disable(exynos_ehci-vdd10);
+
usb_put_hcd(hcd);
 
return 0;
@@ -305,6 +337,11 @@ static int exynos_ehci_suspend(struct device *dev)
 
clk_disable_unprepare(exynos_ehci-clk);
 
+   if (!IS_ERR(exynos_ehci-vdd33))
+   regulator_disable(exynos_ehci-vdd33);
+   if (!IS_ERR(exynos_ehci-vdd10))
+   regulator_disable(exynos_ehci-vdd10);
+
return rc;
 }
 
@@ -314,6 +351,22 @@ static int exynos_ehci_resume(struct device *dev)
struct exynos_ehci_hcd *exynos_ehci = to_exynos_ehci(hcd);
int ret;
 
+   if (!IS_ERR(exynos_ehci-vdd33)) {
+   ret = regulator_enable(exynos_ehci-vdd33);
+   if (ret) {
+   dev_err(dev, Failed to enable 3.3V Vdd supply\n);
+   return ret;
+