From: Simon Horman <horms@verge.net.au>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: linux-renesas-soc@vger.kernel.org, devicetree@vger.kernel.org,
Magnus Damm <magnus.damm@gmail.com>,
linux-arm-kernel@lists.infradead.org,
Khiem Nguyen <khiem.nguyen.xt@renesas.com>
Subject: Re: [PATCH v2 0/2] arm64: dts: renesas: Upgrade to PSCI v1.0 to support Suspend-to-RAM
Date: Thu, 2 Mar 2017 16:05:34 +0100 [thread overview]
Message-ID: <20170302150534.GU6301@verge.net.au> (raw)
In-Reply-To: <1487944154-31435-1-git-send-email-geert+renesas@glider.be>
On Fri, Feb 24, 2017 at 02:49:12PM +0100, Geert Uytterhoeven wrote:
> Hi Simon, Magnus,
>
> This patch series upgrades the version of the PSCI firmware, as
> advertised in DT on Renesas R-Car Gen3 systems, from v0.2 to v1.0.
>
> Note that this series does not have any runtime effects: as of PSCI
> v0.2, PSCI provides a VERSION API. Hence Linux always detected the
> actual version, regardless of what was stated in DT, and enabled v1.0
> features like system suspend:
>
> PSCIv1.0 detected in firmware.
>
> However, it is better to have the real hardware^H^H^H^H^H^H^H^Hfirmware
> description in DT.
>
> Changes compared to v1:
> - Keep "arm,psci-0.2".
>
> Tested on Salvator-X (both H3 and M3-W) with firmware v2.16.0, but I do
> have old boot logs showing that PSCIv1.0 has been detected for a long
> time.
>
> Thanks for applying!
Thanks, I have queued these up for v4.12.
prev parent reply other threads:[~2017-03-02 15:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-24 13:49 [PATCH v2 0/2] arm64: dts: renesas: Upgrade to PSCI v1.0 to support Suspend-to-RAM Geert Uytterhoeven
2017-02-24 13:49 ` [PATCH v2 1/2] arm64: dts: r8a7795: " Geert Uytterhoeven
2017-02-24 13:49 ` [PATCH v2 2/2] arm64: dts: r8a7796: " Geert Uytterhoeven
2017-03-02 15:05 ` Simon Horman [this message]
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=20170302150534.GU6301@verge.net.au \
--to=horms@verge.net.au \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=khiem.nguyen.xt@renesas.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.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).