summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPhilipp Tomsich <philipp.tomsich@theobroma-systems.com>2017-11-06 23:02:51 +0100
committerPhilipp Tomsich <philipp.tomsich@theobroma-systems.com>2017-11-07 09:16:56 +0100
commitdf1e6212f957627731daf9844efe960ca8a549df (patch)
tree53e17d4e9026236e0459d2cb057cbfb05946f438
parentbe942f2e0dca3065ba530555bb6860dafd60ba16 (diff)
rockchip: dts: rk3399-puma: fix the modelling of BIOS_DISABLE
The fixed regulator for overriding BIOS_DISABLE had been modelling backwards (i.e. the GPIO polarity and the enable-active-low/high property had both been inverted), causing the 'regulator' command to always print/expect 'disabled'/'enabled' backwards. This fixes the mix-up and models it correctly: * the GPIO is low-active * the regulator should be enabled (enable-active-high) during boot-on initialisation Signed-off-by: Philipp Tomsich <philipp.tomsich@theobroma-systems.com> Tested-by: Klaus Goger <klaus.goger@theobroma-systems.com>
-rw-r--r--arch/arm/dts/rk3399-puma.dtsi4
1 files changed, 2 insertions, 2 deletions
diff --git a/arch/arm/dts/rk3399-puma.dtsi b/arch/arm/dts/rk3399-puma.dtsi
index 65ab380139..c4da26956a 100644
--- a/arch/arm/dts/rk3399-puma.dtsi
+++ b/arch/arm/dts/rk3399-puma.dtsi
@@ -111,8 +111,8 @@
compatible = "regulator-fixed";
u-boot,dm-pre-reloc;
regulator-name = "bios_enable";
- enable-active-low;
- gpio = <&gpio3 29 GPIO_ACTIVE_HIGH>;
+ enable-active-high;
+ gpio = <&gpio3 29 GPIO_ACTIVE_LOW>;
regulator-always-on;
regulator-boot-on;
regulator-min-microvolt = <1800000>;