After some digging in downstream sources, it was found that the TPS65132
outputs are fixed to +5.4V and -5.4V respectively. This is further confirmed
on runtime through debugfs, the troubleshooting guide confirms this as well.
Specify these limits as such.

Signed-off-by: Stanislav Jakubek <stano.jaku...@gmail.com>
---
 arch/arm/boot/dts/qcom/msm8226-motorola-falcon.dts | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/arch/arm/boot/dts/qcom/msm8226-motorola-falcon.dts 
b/arch/arm/boot/dts/qcom/msm8226-motorola-falcon.dts
index e2bf292159fa9..d6d5a86491aac 100644
--- a/arch/arm/boot/dts/qcom/msm8226-motorola-falcon.dts
+++ b/arch/arm/boot/dts/qcom/msm8226-motorola-falcon.dts
@@ -147,8 +147,8 @@ regulator@3e {
 
                reg_lcd_pos: outp {
                        regulator-name = "outp";
-                       regulator-min-microvolt = <4000000>;
-                       regulator-max-microvolt = <6000000>;
+                       regulator-min-microvolt = <5400000>;
+                       regulator-max-microvolt = <5400000>;
                        regulator-active-discharge = <1>;
                        regulator-boot-on;
                        enable-gpios = <&tlmm 31 GPIO_ACTIVE_HIGH>;
@@ -156,8 +156,8 @@ reg_lcd_pos: outp {
 
                reg_lcd_neg: outn {
                        regulator-name = "outn";
-                       regulator-min-microvolt = <4000000>;
-                       regulator-max-microvolt = <6000000>;
+                       regulator-min-microvolt = <5400000>;
+                       regulator-max-microvolt = <5400000>;
                        regulator-active-discharge = <1>;
                        regulator-boot-on;
                        enable-gpios = <&tlmm 33 GPIO_ACTIVE_HIGH>;
-- 
2.43.0


Reply via email to