summaryrefslogtreecommitdiff
path: root/arch/arm/boot/dts/rk3288-veyron-pinky.dts
diff options
context:
space:
mode:
authorBrian Norris <briannorris@chromium.org>2015-08-20 01:18:41 +0300
committerHeiko Stuebner <heiko@sntech.de>2015-08-21 02:40:35 +0300
commit467fb18a8d538be6548ef4093003b63aebbb07b9 (patch)
treed9ce273bd83e297284e9325b77783246bb24813c /arch/arm/boot/dts/rk3288-veyron-pinky.dts
parent6a414e462a7c493ed83535f388b07a34446f33f4 (diff)
downloadlinux-467fb18a8d538be6548ef4093003b63aebbb07b9.tar.xz
ARM: dts: rockchip: correct regulator power states for suspend
When getting translated from a downstream device tree that used slightly different DT bindings, these regulators got labeled with the "on-in-suspend" state, when they were actually supposed to be turned off for S3 suspend. This was harmless, but not intentional, AFAICT. Let's turn them off to get the optimal power state. Signed-off-by: Brian Norris <briannorris@chromium.org> Reviewed-by: Javier Martinez Canillas <javier@osg.samsung.com> Signed-off-by: Heiko Stuebner <heiko@sntech.de>
Diffstat (limited to 'arch/arm/boot/dts/rk3288-veyron-pinky.dts')
-rw-r--r--arch/arm/boot/dts/rk3288-veyron-pinky.dts2
1 files changed, 1 insertions, 1 deletions
diff --git a/arch/arm/boot/dts/rk3288-veyron-pinky.dts b/arch/arm/boot/dts/rk3288-veyron-pinky.dts
index 25eb4b0c1330..94b56e33d947 100644
--- a/arch/arm/boot/dts/rk3288-veyron-pinky.dts
+++ b/arch/arm/boot/dts/rk3288-veyron-pinky.dts
@@ -109,7 +109,7 @@
regulator-boot-on;
regulator-name = "vcc18_lcd";
regulator-state-mem {
- regulator-on-in-suspend;
+ regulator-off-in-suspend;
};
};
};