Skip to contentSkip to conversation

ARM: dts: omap5-board-common: fix ldo1_reg and ldo4_reg ranges

PATCH New Tomi Valkeinen 2 participants 3 messages Apr 18, 2016 – Apr 26, 2016 Device tree bindings

lore
Share & tools
lore
#0 lore raw

PATCH 1/2 ARM: dts: omap5-board-common: fix ldo1_reg and ldo4_reg ranges

ldo4_reg is connected to DSS, and should always be 1.8V. However the The dts defines a range of 1.5V-1.8V, which requires somethings to set the actual voltage at runtime. Currently we set the voltage in omapdss driver.

As the voltage must always be 1.8V, let's just define the range to 1.8V so that the driver doesn't need to deal with the voltage. In fact, the driver should not touch the voltage, except in the cases where the voltage needs to be changed at runtime.

I presume the situation is the same for ldo1_reg, used for CSI, although I think it is not currently used in the mainline.

---
 arch/arm/boot/dts/omap5-board-common.dtsi | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
arch/arm/boot/dts/omap5-board-common.dtsi +2 -2
index 902657d6713b..914bf4c47404 100644
@@ -472,7 +472,7 @@
 				ldo1_reg: ldo1 {
 					/* VDDAPHY_CAM: vdda_csiport */
 					regulator-name = "ldo1";
-					regulator-min-microvolt = <1500000>;
+					regulator-min-microvolt = <1800000>;
 					regulator-max-microvolt = <1800000>;
 				};
 
@@ -498,7 +498,7 @@
 				ldo4_reg: ldo4 {
 					/* VDDAPHY_DISP: vdda_dsiport/hdmi */
 					regulator-name = "ldo4";
-					regulator-min-microvolt = <1500000>;
+					regulator-min-microvolt = <1800000>;
 					regulator-max-microvolt = <1800000>;
 				};
 
Signature · 1 line
2.5.0
#1 lore raw

PATCH 2/2 ARM: dts: omap5-cm-t54: fix ldo1_reg and ldo4_reg ranges

ldo4_reg is connected to DSS, and should always be 1.8V. However the The dts defines a range of 1.5V-1.8V, which requires somethings to set the actual voltage at runtime. Currently we set the voltage in omapdss driver.

As the voltage must always be 1.8V, let's just define the range to 1.8V so that the driver doesn't need to deal with the voltage. In fact, the driver should not touch the voltage, except in the cases where the voltage needs to be changed at runtime.

I presume the situation is the same for ldo1_reg, used for CSI, although I think it is not currently used in the mainline.

---
 arch/arm/boot/dts/omap5-cm-t54.dts | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
arch/arm/boot/dts/omap5-cm-t54.dts +2 -2
index ecc591dc0778..4d87d9c6c86d 100644
@@ -513,7 +513,7 @@
 				ldo1_reg: ldo1 {
 					/* VDDAPHY_CAM: vdda_csiport */
 					regulator-name = "ldo1";
-					regulator-min-microvolt = <1500000>;
+					regulator-min-microvolt = <1800000>;
 					regulator-max-microvolt = <1800000>;
 				};
 
@@ -537,7 +537,7 @@
 				ldo4_reg: ldo4 {
 					/* VDDAPHY_DISP: vdda_dsiport/hdmi */
 					regulator-name = "ldo4";
-					regulator-min-microvolt = <1500000>;
+					regulator-min-microvolt = <1800000>;
 					regulator-max-microvolt = <1800000>;
 				};
 
Signature · 1 line
2.5.0
#2 lore raw

PATCH 1/2 ARM: dts: omap5-board-common: fix ldo1_reg and ldo4_reg ranges

In reply to Tomi Valkeinen
Quoted 9 lines · Tomi Valkeinen

ldo4_reg is connected to DSS, and should always be 1.8V. However the The dts defines a range of 1.5V-1.8V, which requires somethings to set the actual voltage at runtime. Currently we set the voltage in omapdss driver.

As the voltage must always be 1.8V, let's just define the range to 1.8V so that the driver doesn't need to deal with the voltage. In fact, the driver should not touch the voltage, except in the cases where the voltage needs to be changed at runtime.

Thanks applying both into omap-for-v4.6/fixes-rc5. Feel free to merge commit 5607959a4d5b54dcc9a3572bdbf967dfda88ae66 into your DSS tree too for v4.7 in case it gets too late for these fixes for v4.6-rc.

Regards,

Tony