Facilitate getting required 3.3V and 1.0V VDD supply for
EHCI controller on Exynos.
With 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,
certain perripherals will now need to ensure that,
they request VDD regulators in their drivers, and enable
them so as to make them working.
Signed-off-by: Vivek Gautam <redacted>
Cc: Jingoo Han <redacted>
---
Changes from v1:
- Addressed review comments for making the regulators optional,
and thus refactored the checks for the obtained regulators.
drivers/usb/host/ehci-exynos.c | 59 +++++++++++++++++++++++++++++++++++++++-
1 file changed, 58 insertions(+), 1 deletion(-)
Facilitate getting required 3.3V and 1.0V VDD supply for
OHCI controller on Exynos.
With 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,
certain perripherals will now need to ensure that,
they request VDD regulators in their drivers, and enable
them so as to make them working.
Signed-off-by: Vivek Gautam <redacted>
Cc: Jingoo Han <redacted>
---
Changes from v1:
- Addressed review comments for making the regulators optional,
and thus refactored the checks for the obtained regulators.
drivers/usb/host/ohci-exynos.c | 59 +++++++++++++++++++++++++++++++++++++++-
1 file changed, 58 insertions(+), 1 deletion(-)
From: Alan Stern <stern@rowland.harvard.edu> Date: 2014-06-11 15:39:14
On Fri, 6 Jun 2014, Vivek Gautam wrote:
Facilitate getting required 3.3V and 1.0V VDD supply for
EHCI controller on Exynos.
With 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,
certain perripherals will now need to ensure that,
they request VDD regulators in their drivers, and enable
them so as to make them working.
"Certain peripherals"? Don't you mean "certain controllers"?
Does this mean some controllers don't need to use the VDD regulators?
quoted hunk
@@ -193,7 +196,31 @@ 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(&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;+ }+ } else {+ dev_warn(&pdev->dev, "Regulator 3.3V Vdd supply not found\n");+ }
What if this is one of the controllers that don't need to use a VDD
regulator? Do you really want to print out a warning in that case?
Should you call devm_regulator_get_optional() instead?
Alan Stern
From: Jingoo Han <hidden> Date: 2014-06-12 04:21:21
On Thursday, June 12, 2014 12:39 AM, Alan Stern wrote:
On Fri, 6 Jun 2014, Vivek Gautam wrote:
quoted
Facilitate getting required 3.3V and 1.0V VDD supply for
EHCI controller on Exynos.
With 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,
certain perripherals will now need to ensure that,
they request VDD regulators in their drivers, and enable
them so as to make them working.
"Certain peripherals"? Don't you mean "certain controllers"?
Does this mean some controllers don't need to use the VDD regulators?
quoted
@@ -193,7 +196,31 @@ 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(&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;+ }+ } else {+ dev_warn(&pdev->dev, "Regulator 3.3V Vdd supply not found\n");+ }
What if this is one of the controllers that don't need to use a VDD
regulator? Do you really want to print out a warning in that case?
Should you call devm_regulator_get_optional() instead?
I agree with Alan's suggestion. This warning message is not
proper, when USB controllers that don't need a VDD regulator
are used. The devm_regulator_get_optional() looks better.
Best regards,
Jingoo Han
Hi,
On Wed, Jun 11, 2014 at 9:09 PM, Alan Stern [off-list ref] wrote:
On Fri, 6 Jun 2014, Vivek Gautam wrote:
quoted
Facilitate getting required 3.3V and 1.0V VDD supply for
EHCI controller on Exynos.
With 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,
certain perripherals will now need to ensure that,
they request VDD regulators in their drivers, and enable
them so as to make them working.
"Certain peripherals"? Don't you mean "certain controllers"?
Right, 'certain controllers'.
Does this mean some controllers don't need to use the VDD regulators?
Actually until the two patches got merged, the USB controllers were
depending on bootloader
for the VDD supply, wherein it was enabled, which ofcourse was bad.
And by 'certain' i meant that above mentioned dt patches enable only the minimum
number of regulators for the system, however leaves other for the
drivers to enable.
Anyways, i will re-do this commit message.
quoted
@@ -193,7 +196,31 @@ 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(&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;+ }+ } else {+ dev_warn(&pdev->dev, "Regulator 3.3V Vdd supply not found\n");+ }
What if this is one of the controllers that don't need to use a VDD
regulator? Do you really want to print out a warning in that case?
Should you call devm_regulator_get_optional() instead?
Right, better to use devm_regulator_get_optional(). Thanks for
pointing this out.
--
Best Regards
Vivek Gautam
Samsung R&D Institute, Bangalore
India
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 <redacted>
Cc: Jingoo Han <redacted>
Cc: Alan Stern <stern@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(-)
@@ -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:
Facilitate getting required 3.3V and 1.0V VDD supply for
OHCI controller on Exynos.
With 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 <redacted>
Cc: Jingoo Han <redacted>
Cc: Alan Stern <stern@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 | 4 ++
drivers/usb/host/ohci-exynos.c | 55 +++++++++++++++++++-
2 files changed, 58 insertions(+), 1 deletion(-)
@@ -63,6 +63,10 @@ Required properties: port 2 is HSIC phy1 - phys: from the *Generic PHY* bindings, specifying phy used by port.+Optional properties:+ - 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: usb at 12120000 { compatible = "samsung,exynos4210-ohci";
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 <redacted>
Cc: Jingoo Han <redacted>
Cc: Alan Stern <stern@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