From: thierry.reding@gmail.com (Thierry Reding)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 8/9] arm64: tegra: Enable PSCI on P3310
Date: Thu, 17 Nov 2016 18:33:28 +0100 [thread overview]
Message-ID: <20161117173328.GB7915@ulmo.ba.sec> (raw)
In-Reply-To: <786f354d-a1f2-f2c6-fde7-7b1af3df756c@arm.com>
On Thu, Nov 17, 2016 at 05:21:34PM +0000, Sudeep Holla wrote:
>
>
> On 17/11/16 17:11, Thierry Reding wrote:
> > From: Thierry Reding <treding@nvidia.com>
> >
> > The P3310 processor module comes ships with a firmware that implements
> > PSCI 1.0. Enable and use it to bring up all CPUs.
> >
> > Signed-off-by: Thierry Reding <treding@nvidia.com>
> > ---
> > arch/arm64/boot/dts/nvidia/tegra186-p3310.dtsi | 36 ++++++++++++++++++++++++++
> > 1 file changed, 36 insertions(+)
> >
> > diff --git a/arch/arm64/boot/dts/nvidia/tegra186-p3310.dtsi b/arch/arm64/boot/dts/nvidia/tegra186-p3310.dtsi
> > index 807af7b68761..2c158c6809a5 100644
> > --- a/arch/arm64/boot/dts/nvidia/tegra186-p3310.dtsi
> > +++ b/arch/arm64/boot/dts/nvidia/tegra186-p3310.dtsi
> > @@ -26,7 +26,43 @@
> > status = "okay";
> > };
> >
> > + cpus {
> > + cpu at 0 {
> > + enable-method = "psci";
> > + };
> > +
> > + cpu at 1 {
> > + enable-method = "psci";
> > + };
> > +
> > + cpu at 2 {
> > + enable-method = "psci";
> > + };
> > +
> > + cpu at 3 {
> > + enable-method = "psci";
> > + };
> > +
> > + cpu at 4 {
> > + enable-method = "psci";
> > + };
> > +
> > + cpu at 5 {
> > + enable-method = "psci";
> > + };
> > + };
> > +
> > bpmp {
> > status = "okay";
> > };
> > +
> > + psci {
> > + compatible = "arm,psci-1.0";
> > + status = "okay";
> > + method = "smc";
>
> [...]
>
> > +
> > + cpu_off = <0x84000002>;
> > + cpu_on = <0xc4000003>;
> > + cpu_suspend = <0xc4000001>;
>
> These are applicable only for "arm,psci"(i.e. PSCI v0.1), so you need to
> drop them.
Oh, indeed. I obviously skipped the arm,psci and arm,psci-0.2 entries in
the binding documentation and then assumed the optional properties
applied regardless of PSCI version.
Removed these and everything still works as expected.
Thanks,
Thierry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20161117/e20a846e/attachment.sig>
next prev parent reply other threads:[~2016-11-17 17:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-17 17:11 [PATCH 1/9] arm64: tegra: Add Tegra186 support Thierry Reding
2016-11-17 17:11 ` [PATCH 2/9] arm64: tegra: Add CPU nodes for Tegra186 Thierry Reding
2016-11-17 17:11 ` [PATCH 3/9] arm64: tegra: Add serial ports on Tegra186 Thierry Reding
2016-11-17 17:11 ` [PATCH 4/9] arm64: tegra: Add I2C controllers " Thierry Reding
2016-11-17 17:11 ` [PATCH 5/9] arm64: tegra: Add SDHCI " Thierry Reding
2016-11-17 17:11 ` [PATCH 6/9] arm64: tegra: Add GPIO " Thierry Reding
2016-11-17 17:11 ` [PATCH 7/9] arm64: tegra: Add NVIDIA P3310 processor module support Thierry Reding
2016-11-17 17:11 ` [PATCH 8/9] arm64: tegra: Enable PSCI on P3310 Thierry Reding
2016-11-17 17:21 ` Sudeep Holla
2016-11-17 17:33 ` Thierry Reding [this message]
2016-11-17 17:11 ` [PATCH 9/9] arm64: tegra: Add NVIDIA P2771 board support Thierry Reding
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=20161117173328.GB7915@ulmo.ba.sec \
--to=thierry.reding@gmail.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).