From: Sudeep Holla <sudeep.holla@arm.com>
To: Hongbo Zhang <hongbo.zhang@nxp.com>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>
Cc: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Marc Zyngier <marc.zyngier@arm.com>,
Jan Kiszka <jan.kiszka@siemens.com>,
Mark Rutland <mark.rutland@arm.com>,
Sudeep Holla <sudeep.holla@arm.com>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Chen-Yu Tsai <wens@csie.org>, Hans de Goede <hdegoede@redhat.com>,
Frank Li <Frank.Li@freescale.com>,
Peng Fan <Peng.Fan@freescale.com>,
Tom Warren <twarren@nvidia.com>,
Vincent Guittot <vincent.guittot@linaro.org>
Subject: Re: [PSCI DISCUSS] How to implement standby and suspend-to-ram by PSCI
Date: Fri, 6 May 2016 14:28:18 +0100 [thread overview]
Message-ID: <572C9BF2.9010004@arm.com> (raw)
In-Reply-To: <DB3PR04MB0812DAA98F71C30E8A8832E3847D0@DB3PR04MB0812.eurprd04.prod.outlook.com>
Hi Hongbo,
On 06/05/16 11:11, Hongbo Zhang wrote:
> Hi Guys,
> We know in the legacy kernel suspend codes, a typical suspend_ops->enter
> callback is like this:
>
[...]
>
> That means we implement standby and suspend-to-ram in one callback, and
> these two state can be identified by an input parameter 'state'.
>
> While now PSCI is used for ARM to implement cores operations and power
> management, for the above suspend_ops->enter we choose SYSTEM_SUSPEND
> function, and this function is defined for suspend-to-ram, then here
> comes the problem:
>
> How can we implement the standby state following the PSCI framework?
>
Jisheng Zhang raised similar question few months back and we had a
discussion. Please have a look at the thread [1]
> I couldn't find other PSCI function which fits for standby well.
> In the spec there isn't such a 'state' parameter passed for
> SYSTEM_SUSPEND (only entry_point_address and context_id), can we change
> the spec a bit, e.g. using one more register to pass another 'state'
> parameter? is that acceptable? (similar like CPU_SUSPEND then)
>
Since the standby state is not well defined on ARM systems, it's hard to
define the conditions like system suspend and hence difficult to
generalize in the spec. I think suspend-to-idle should suffice in your
case. Anyways its better to get more information on the definition of
standby on your platform.
--
Regards,
Sudeep
[1]
http://lists.infradead.org/pipermail/linux-arm-kernel/2015-July/356467.html
next prev parent reply other threads:[~2016-05-06 13:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-06 10:11 [PSCI DISCUSS] How to implement standby and suspend-to-ram by PSCI Hongbo Zhang
2016-05-06 13:28 ` Sudeep Holla [this message]
2016-05-12 9:42 ` Hongbo Zhang
2016-05-12 10:08 ` Sudeep Holla
2016-05-19 9:26 ` Hongbo Zhang
2016-05-17 11:53 ` Oliver Neukum
2016-05-19 10:27 ` Hongbo Zhang
2016-05-19 12:01 ` Oliver Neukum
2016-05-20 8:23 ` Hongbo Zhang
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=572C9BF2.9010004@arm.com \
--to=sudeep.holla@arm.com \
--cc=Frank.Li@freescale.com \
--cc=Peng.Fan@freescale.com \
--cc=daniel.lezcano@linaro.org \
--cc=hdegoede@redhat.com \
--cc=hongbo.zhang@nxp.com \
--cc=jan.kiszka@siemens.com \
--cc=linux-pm@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=marc.zyngier@arm.com \
--cc=mark.rutland@arm.com \
--cc=twarren@nvidia.com \
--cc=vincent.guittot@linaro.org \
--cc=wens@csie.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).