summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorGregory CLEMENT <gregory.clement@free-electrons.com>2015-07-03 13:55:53 +0200
committerGregory CLEMENT <gregory.clement@free-electrons.com>2015-07-28 11:40:47 +0200
commit482d638f98cc626bf01d4c9f6d6d35fc77d630c8 (patch)
treea8b1547143ebbd0577e348d10d500b86bad09916
parent3cbd6a6ca81c9e8438b592099495a7c2b72de9e3 (diff)
downloadop-kernel-dev-482d638f98cc626bf01d4c9f6d6d35fc77d630c8.zip
op-kernel-dev-482d638f98cc626bf01d4c9f6d6d35fc77d630c8.tar.gz
ARM: mvebu: Warn about the wake-up sources not taken into account in suspend
On the Armada 370/XP/38x/39x SoCs when the suspend to ram feature is supported, the SoCs are shutdown and will be woken up by an external micro-controller, so there is no possibility to setup wake-up sources from Linux. However, in standby mode, the SoCs stay powered and it is possible to wake-up from any interrupt sources. Since when the users configures the enabled wake-up sources there is no way to know if the user will be doing suspend to RAM or standby, we just allow all wake-up sources to be enabled, and only warn when entering suspend to RAM The purpose of this patch is to inform the user that in suspend to ram mode, the wake-up sources won't be taken into consideration. Signed-off-by: Gregory CLEMENT <gregory.clement@free-electrons.com>
-rw-r--r--arch/arm/mach-mvebu/pm.c1
1 files changed, 1 insertions, 0 deletions
diff --git a/arch/arm/mach-mvebu/pm.c b/arch/arm/mach-mvebu/pm.c
index b058307..8d32bf7 100644
--- a/arch/arm/mach-mvebu/pm.c
+++ b/arch/arm/mach-mvebu/pm.c
@@ -192,6 +192,7 @@ static int mvebu_pm_enter(suspend_state_t state)
cpu_do_idle();
break;
case PM_SUSPEND_MEM:
+ pr_warn("Entering suspend to RAM. Only special wake-up sources will resume the system\n");
return mvebu_enter_suspend();
default:
return -EINVAL;
OpenPOWER on IntegriCloud