From: Philipp Tomsich Date: Mon, 6 Nov 2017 22:02:51 +0000 (+0100) Subject: rockchip: dts: rk3399-puma: fix the modelling of BIOS_DISABLE X-Git-Url: http://git.dujemihanovic.xyz/login.html?a=commitdiff_plain;h=df1e6212f957627731daf9844efe960ca8a549df;p=u-boot.git 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 Tested-by: Klaus Goger --- 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>;