From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 7/7] dts: calxeda: add ARM PSCI binding
Date: Mon, 29 Jul 2013 15:30:50 +0100 [thread overview]
Message-ID: <20130729143050.GC25264@e106331-lin.cambridge.arm.com> (raw)
In-Reply-To: <51F66A72.7070209@gmail.com>
On Mon, Jul 29, 2013 at 02:13:22PM +0100, Rob Herring wrote:
> On 07/29/2013 05:24 AM, Mark Rutland wrote:
> > On Sun, Jul 28, 2013 at 10:56:38PM +0100, Rob Herring wrote:
> >> From: Rob Herring <rob.herring@calxeda.com>
> >>
> >> Add the PSCI binding for Calxeda SOCs. The PSCI function numbers are
> >> different from the DT binding example because the numbering changed in
> >> revisions of the PSCI spec and are already fixed in highbank firmware.
> >> Since the numbering is transparent to the kernel, this difference is not
> >> significant.
> >>
> >> Signed-off-by: Rob Herring <rob.herring@calxeda.com>
> >> ---
> >> arch/arm/boot/dts/ecx-common.dtsi | 10 ++++++++++
> >> 1 file changed, 10 insertions(+)
> >>
> >> diff --git a/arch/arm/boot/dts/ecx-common.dtsi b/arch/arm/boot/dts/ecx-common.dtsi
> >> index e8559b7..f1dfc09 100644
> >> --- a/arch/arm/boot/dts/ecx-common.dtsi
> >> +++ b/arch/arm/boot/dts/ecx-common.dtsi
> >> @@ -19,6 +19,16 @@
> >> bootargs = "console=ttyAMA0";
> >> };
> >>
> >> + psci {
> >> + compatible = "arm,psci";
> >> + method = "smc";
> >> + cpu_suspend = <0x84000002>;
> >> + cpu_off = <0x84000004>;
> >> + cpu_on = <0x84000006>;
> >> + system_off = <0x84000100>;
> >> + system_reset = <0x84000101>;
> >> + };
> >> +
> >
> > I see this is somewhat beyond the original PSCI, given the addition of
> > SYSTEM_OFF and SYSTEM_RESET, but not quite PSCI 0.2 as you don't have
> > PSCI_VERSION.
>
> I do actually support PSCI_VERSION. Forgot to add that to the dts.
Ah, ok. Can you upgrade the compatible string to include "arm,psci-0.2"
while you're at it?
>
> > It would be nice it the compatible string were more specific here to
> > deal with this and any implementation-specific power_state ID values.
> > Something like "calxeda,highbank-psci", "arm,psci" ?
>
> Is that something we always want to do? You can't really know the
> implementation quirks up front.
While we might not know the quirks up front, it'll mean that when we
discover one we have a greater chance of being able to find out the
presence of the quirk from an old dts.
Thanks,
Mark.
prev parent reply other threads:[~2013-07-29 14:30 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-28 21:56 [PATCH v3 0/7] PSCI support for highbank Rob Herring
2013-07-28 21:56 ` [PATCH 1/7] dt: update PSCI binding documentation for v0.2 Rob Herring
2013-07-29 10:13 ` Mark Rutland
2013-07-29 20:18 ` Rob Herring
2013-07-30 9:49 ` Mark Rutland
2013-07-30 12:42 ` Rob Herring
2013-07-30 12:56 ` Mark Rutland
2013-07-30 13:44 ` Mark Rutland
2013-07-30 14:33 ` Stefano Stabellini
2013-07-30 14:42 ` Ian Campbell
2013-07-30 17:48 ` Matt Sealey
2013-07-31 8:55 ` Ian Campbell
2013-07-31 13:49 ` Mark Rutland
2013-07-31 17:24 ` Matt Sealey
2013-07-31 17:49 ` Rob Herring
2013-08-01 17:51 ` Dave Martin
2013-08-01 19:02 ` Rob Herring
2013-08-01 21:04 ` Matt Sealey
2013-07-31 13:07 ` Mark Rutland
2013-07-30 19:34 ` Rob Herring
2013-07-31 8:57 ` Ian Campbell
2013-07-31 13:05 ` Mark Rutland
2013-07-30 10:01 ` Dave Martin
2013-07-28 21:56 ` [PATCH 2/7] ARM: PSCI: remove unnecessary include of arm-gic.h Rob Herring
2013-07-28 21:56 ` [PATCH 3/7] ARM: PSCI: add ops for system restart and power off Rob Herring
2013-07-28 21:56 ` [PATCH 4/7] cpuidle: calxeda: add support to use PSCI calls Rob Herring
2013-07-29 14:14 ` Daniel Lezcano
2013-07-29 14:39 ` Rob Herring
2013-07-29 14:46 ` Daniel Lezcano
2013-07-28 21:56 ` [PATCH 5/7] ARM: highbank: clean-up some unused includes Rob Herring
2013-07-28 21:56 ` [PATCH 6/7] ARM: highbank: adapt to use ARM PSCI calls Rob Herring
2013-07-28 21:56 ` [PATCH 7/7] dts: calxeda: add ARM PSCI binding Rob Herring
2013-07-29 10:24 ` Mark Rutland
2013-07-29 13:13 ` Rob Herring
2013-07-29 14:30 ` Mark Rutland [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=20130729143050.GC25264@e106331-lin.cambridge.arm.com \
--to=mark.rutland@arm.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).