From: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: Sudeep Holla <sudeep.holla@arm.com>,
yoma sophian <sophian.yoma@gmail.com>,
linux-arm-kernel@lists.infradead.org, linux-pm@vger.kernel.org
Subject: Re: how to enable suspend to ram for arm-64 bits
Date: Tue, 18 Oct 2016 11:28:18 +0100 [thread overview]
Message-ID: <20161018102818.GA1212@red-moon> (raw)
In-Reply-To: <20161018100002.GA4347@xo-6d-61-c0.localdomain>
On Tue, Oct 18, 2016 at 12:00:02PM +0200, Pavel Machek wrote:
> Hi!
>
> > >b. in arm64, if some platform has its own suspend flow, couldn't it
> > >adopts arm/match-xxx to register its own global suspend method?
> > >
> >
> > No, PSCI is highly recommended.
>
> Relying on firmware for suspend on x86 was a great disaster, lets not
> repeat that mistake. arm32 has better powermanagement than x86 ever
> will (see Nokia N900 for example) -- feel free to copy that code from
> arm32.
Yes sure, feel free to copy my:
NACKed-by: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
to all the resulting patches then. On ARM64 if he wants to implement
suspend-to-RAM his PSCI firmware will have to implement PSCI system
suspend method, end of this discussion.
By the way, why are you advising people on this subject ?
What do you know about the PSCI firmware interface to state what
you are saying above ?
Lorenzo
next prev parent reply other threads:[~2016-10-18 10:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-17 17:26 how to enable suspend to ram for arm-64 bits yoma sophian
2016-08-17 17:49 ` Sudeep Holla
2016-08-18 2:07 ` yoma sophian
2016-08-18 8:47 ` Sudeep Holla
2016-08-18 10:43 ` yoma sophian
2016-08-18 10:52 ` Sudeep Holla
2016-08-22 14:41 ` yoma sophian
2016-08-22 15:00 ` Sudeep Holla
2016-10-18 10:00 ` Pavel Machek
2016-10-18 10:21 ` Sudeep Holla
2016-10-18 10:28 ` Lorenzo Pieralisi [this message]
2016-10-18 10:45 ` Mark Rutland
2016-10-18 10:59 ` Sudeep Holla
2016-10-19 7:18 ` yoma sophian
2016-10-19 9:42 ` Pavel Machek
2016-10-19 13:11 ` Mark Rutland
2016-11-03 9:57 ` Pavel Machek
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=20161018102818.GA1212@red-moon \
--to=lorenzo.pieralisi@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=sophian.yoma@gmail.com \
--cc=sudeep.holla@arm.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 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).