From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: Gregory CLEMENT <gregory.clement@free-electrons.com>
Cc: Jason Cooper <jason@lakedaemon.net>, Andrew Lunn <andrew@lunn.ch>,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
Ezequiel Garcia <ezequiel.garcia@free-electrons.com>,
linux-arm-kernel@lists.infradead.org,
Maxime Ripard <maxime.ripard@free-electrons.com>,
Boris BREZILLON <boris.brezillon@free-electrons.com>,
Lior Amsalem <alior@marvell.com>,
Tawfik Bayouk <tawfik@marvell.com>,
Nadav Haklai <nadavh@marvell.com>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 4/4] ARM: mvebu: Warn about the wake-up sources not taken into account in suspend
Date: Wed, 1 Jul 2015 18:04:29 +0200 [thread overview]
Message-ID: <20150701180429.3c3ef6de@free-electrons.com> (raw)
In-Reply-To: <1435684740-24912-5-git-send-email-gregory.clement@free-electrons.com>
Hello,
On Tue, 30 Jun 2015 19:19:00 +0200, Gregory CLEMENT wrote:
> On the Armada 370/XP/38x/39x SoCs when the suspend to ram feature is
> supported, the SoC is shutdown and will be waken up by an external
waken -> woken
> micro-controller, so there is no possibility to setup wake-up source
source -> sources
> from Linux. However, in standby mode, the SoCs stay powered and it is
stay powered -> stays powered on
> possible to wake-up from any interrupt sources. As, when user decide to
> setup a wake-up source, there is no way to know if they will be
> wake-up source from suspend or from standby, then we chose allowing to
> setup all the interrupt as wake-up sources.
Hum. "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".
> diff --git a/arch/arm/mach-mvebu/pm.c b/arch/arm/mach-mvebu/pm.c
> index 264073a777d8..4402dcfa7c56 100644
> --- a/arch/arm/mach-mvebu/pm.c
> +++ b/arch/arm/mach-mvebu/pm.c
> @@ -235,6 +235,7 @@ static int mvebu_pm_enter(suspend_state_t state)
> cpu_do_idle();
> break;
> case PM_SUSPEND_MEM:
> + pr_warn("None of the wakeup sources will be taken into account in suspend to ram\n");
We already had some discussion about this, and I believe this continue
to be confusing: there are some wake-up sources taken into account when
in suspend to RAM: the special button used by the micro-controller. It
is indeed not a wake-up source in the Linux sense, but it is still a
wake-up source. With such a message, the user may believe that there is
simply no way of resuming the platform.
Maybe just:
pr_warn("Entering suspend to RAM. Only special wake-up sources will resume the system\n");
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
WARNING: multiple messages have this Message-ID (diff)
From: thomas.petazzoni@free-electrons.com (Thomas Petazzoni)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 4/4] ARM: mvebu: Warn about the wake-up sources not taken into account in suspend
Date: Wed, 1 Jul 2015 18:04:29 +0200 [thread overview]
Message-ID: <20150701180429.3c3ef6de@free-electrons.com> (raw)
In-Reply-To: <1435684740-24912-5-git-send-email-gregory.clement@free-electrons.com>
Hello,
On Tue, 30 Jun 2015 19:19:00 +0200, Gregory CLEMENT wrote:
> On the Armada 370/XP/38x/39x SoCs when the suspend to ram feature is
> supported, the SoC is shutdown and will be waken up by an external
waken -> woken
> micro-controller, so there is no possibility to setup wake-up source
source -> sources
> from Linux. However, in standby mode, the SoCs stay powered and it is
stay powered -> stays powered on
> possible to wake-up from any interrupt sources. As, when user decide to
> setup a wake-up source, there is no way to know if they will be
> wake-up source from suspend or from standby, then we chose allowing to
> setup all the interrupt as wake-up sources.
Hum. "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".
> diff --git a/arch/arm/mach-mvebu/pm.c b/arch/arm/mach-mvebu/pm.c
> index 264073a777d8..4402dcfa7c56 100644
> --- a/arch/arm/mach-mvebu/pm.c
> +++ b/arch/arm/mach-mvebu/pm.c
> @@ -235,6 +235,7 @@ static int mvebu_pm_enter(suspend_state_t state)
> cpu_do_idle();
> break;
> case PM_SUSPEND_MEM:
> + pr_warn("None of the wakeup sources will be taken into account in suspend to ram\n");
We already had some discussion about this, and I believe this continue
to be confusing: there are some wake-up sources taken into account when
in suspend to RAM: the special button used by the micro-controller. It
is indeed not a wake-up source in the Linux sense, but it is still a
wake-up source. With such a message, the user may believe that there is
simply no way of resuming the platform.
Maybe just:
pr_warn("Entering suspend to RAM. Only special wake-up sources will resume the system\n");
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-07-01 16:04 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-30 17:18 [PATCH v2 0/4] Add standby support for the recent mvebu SoCs Gregory CLEMENT
2015-06-30 17:18 ` Gregory CLEMENT
2015-06-30 17:18 ` [PATCH v2 1/4] ARM: mvebu: Use __init for the PM initialization functions Gregory CLEMENT
2015-06-30 17:18 ` Gregory CLEMENT
2015-06-30 17:18 ` Gregory CLEMENT
2015-07-01 15:18 ` Thomas Petazzoni
2015-07-01 15:18 ` Thomas Petazzoni
2015-06-30 17:18 ` [PATCH v2 2/4] ARM: mvebu: Add standby support Gregory CLEMENT
2015-06-30 17:18 ` Gregory CLEMENT
2015-07-01 15:47 ` Thomas Petazzoni
2015-07-01 15:47 ` Thomas Petazzoni
2015-07-03 11:39 ` Gregory CLEMENT
2015-07-03 11:39 ` Gregory CLEMENT
2015-07-03 12:17 ` Thomas Petazzoni
2015-07-03 12:17 ` Thomas Petazzoni
2015-07-03 12:21 ` Gregory CLEMENT
2015-07-03 12:21 ` Gregory CLEMENT
2015-07-03 12:33 ` Thomas Petazzoni
2015-07-03 12:33 ` Thomas Petazzoni
2015-06-30 17:18 ` [PATCH v2 3/4] ARM: mvebu: Allow using the GIC for wakeup in standby mode Gregory CLEMENT
2015-06-30 17:18 ` Gregory CLEMENT
2015-07-01 15:54 ` Thomas Petazzoni
2015-07-01 15:54 ` Thomas Petazzoni
2015-07-03 7:18 ` Gregory CLEMENT
2015-07-03 7:18 ` Gregory CLEMENT
2015-07-27 11:02 ` Sudeep Holla
2015-07-27 11:02 ` Sudeep Holla
2015-07-28 9:42 ` Gregory CLEMENT
2015-07-28 9:42 ` Gregory CLEMENT
2015-07-01 16:05 ` Sudeep Holla
2015-07-01 16:05 ` Sudeep Holla
2015-07-01 16:56 ` Geert Uytterhoeven
2015-07-01 16:56 ` Geert Uytterhoeven
2015-06-30 17:19 ` [PATCH v2 4/4] ARM: mvebu: Warn about the wake-up sources not taken into account in suspend Gregory CLEMENT
2015-06-30 17:19 ` Gregory CLEMENT
2015-07-01 16:04 ` Thomas Petazzoni [this message]
2015-07-01 16:04 ` Thomas Petazzoni
2015-07-03 9:55 ` Gregory CLEMENT
2015-07-03 9:55 ` Gregory CLEMENT
2015-07-25 15:20 ` [PATCH v2 0/4] Add standby support for the recent mvebu SoCs Gregory CLEMENT
2015-07-25 15:20 ` Gregory CLEMENT
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150701180429.3c3ef6de@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=alior@marvell.com \
--cc=andrew@lunn.ch \
--cc=boris.brezillon@free-electrons.com \
--cc=ezequiel.garcia@free-electrons.com \
--cc=gregory.clement@free-electrons.com \
--cc=jason@lakedaemon.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=maxime.ripard@free-electrons.com \
--cc=nadavh@marvell.com \
--cc=sebastian.hesselbarth@gmail.com \
--cc=tawfik@marvell.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.