UPSTREAM: 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 Change-Id: I868f3d9ebaed3d1a17b66244dd84ed9332bf24a1 Signed-off-by: Philipp Tomsich <philipp.tomsich@theobroma-systems.com> Tested-by: Klaus Goger <klaus.goger@theobroma-systems.com> Signed-off-by: Kever Yang <kever.yang@rock-chips.com> (cherry picked from commit df1e6212f957627731daf9844efe960ca8a549df)
This commit is contained in:
parent
d8bee3a4c9
commit
f2d89a0e58
|
|
@ -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>;
|
||||
|
|
|
|||
Loading…
Reference in New Issue