summaryrefslogtreecommitdiffstats
path: root/drivers/soc/Makefile
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 /drivers/soc/Makefile
parent3cbd6a6ca81c9e8438b592099495a7c2b72de9e3 (diff)
downloadblackbird-op-linux-482d638f98cc626bf01d4c9f6d6d35fc77d630c8.tar.gz
blackbird-op-linux-482d638f98cc626bf01d4c9f6d6d35fc77d630c8.zip
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>
Diffstat (limited to 'drivers/soc/Makefile')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud