suspend: gxm can not enter suspend state issue [1/2]

PD#SWPL-13523

Problem:
gxm can't enter suspend

Solution:
modify the system sleep parameter

Verify:
gxm_q201

Change-Id: I697f03170a56925aa0fdb2160340cc0d480623a8
Signed-off-by: Hong Guo <hong.guo@amlogic.com>

diff --git a/arch/arm/boot/dts/amlogic/mesongxm.dtsi b/arch/arm/boot/dts/amlogic/mesongxm.dtsi
index e960b37..7976c6a 100644 (file)
--- a/arch/arm/boot/dts/amlogic/mesongxm.dtsi
+++ b/arch/arm/boot/dts/amlogic/mesongxm.dtsi
@@ -212,7 +212,7 @@
 */
                        SYSTEM_SLEEP_0: system-sleep-0 {
                                compatible = "arm,idle-state";
-                               arm,psci-suspend-param = <0x1010000>;
+                               arm,psci-suspend-param = <0x1020000>;
                                local-timer-stop;
                                entry-latency-us = <0x3fffffff>;
                                exit-latency-us = <0x40000000>;

diff --git a/arch/arm64/boot/dts/amlogic/mesongxm.dtsi b/arch/arm64/boot/dts/amlogic/mesongxm.dtsi
index 578949c..493e4f4 100644 (file)
--- a/arch/arm64/boot/dts/amlogic/mesongxm.dtsi
+++ b/arch/arm64/boot/dts/amlogic/mesongxm.dtsi
@@ -212,7 +212,7 @@
 */
                        SYSTEM_SLEEP_0: system-sleep-0 {
                                compatible = "arm,idle-state";
-                               arm,psci-suspend-param = <0x1010000>;
+                               arm,psci-suspend-param = <0x1020000>;
                                local-timer-stop;
                                entry-latency-us = <0x3fffffff>;
                                exit-latency-us = <0x40000000>;