From: oneukum@suse.com (Oliver Neukum)
To: linux-arm-kernel@lists.infradead.org
Subject: [PSCI DISCUSS] How to implement standby and suspend-to-ram by PSCI
Date: Tue, 17 May 2016 13:53:56 +0200 [thread overview]
Message-ID: <1463486036.19237.9.camel@suse.com> (raw)
In-Reply-To: <DB3PR04MB08125A628F5034749F8109D884730@DB3PR04MB0812.eurprd04.prod.outlook.com>
On Thu, 2016-05-12 at 09:42 +0000, Hongbo Zhang wrote:
> On our platform we have some shallow states which maps to cpuidle
> well,
> and we have two more deeper states:
>
> Sleep state:
> All cores are in WFI state,
> Core cluster is in standby state, e.g. L2 cache is flushed then stops
> snooping,
> Only those modules which are required to wake up the device still have
> a
> running clock, other device modules in chip are clock gated.
>
> Deep sleep state:
> ARM cores and DDR controller are switched off,
> DDR is in self-refresh mode,
> VDD power to off domain IPs are removed, Only the blocks needed to
> detect wake up and sequence the chip out of deep sleep are on.
For the pm module of the core kernel a low power state is a sleep
state if even one of three conditions is met:
a) a device that can be used for input is not a source of wake ups
b) tasks need to be frozen to enter it
c) the display goes off, while it should be on
Generally runtime PM is better if you can get the same results.
Going to a system sleep state is a necessary evil.
Regards
Oliver
next prev parent reply other threads:[~2016-05-17 11:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <DB3PR04MB0812DAA98F71C30E8A8832E3847D0@DB3PR04MB0812.eurprd04.prod.outlook.com>
[not found] ` <572C9BF2.9010004@arm.com>
2016-05-12 9:42 ` [PSCI DISCUSS] How to implement standby and suspend-to-ram by PSCI Hongbo Zhang
2016-05-12 10:08 ` Sudeep Holla
2016-05-19 9:26 ` Hongbo Zhang
2016-05-17 11:53 ` Oliver Neukum [this message]
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=1463486036.19237.9.camel@suse.com \
--to=oneukum@suse.com \
--cc=linux-arm-kernel@lists.infradead.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).