From: ashwin.chaugule@linaro.org (Ashwin Chaugule)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v9 2/3] Documentation: devicetree: Add new binding for PSCIv0.2
Date: Wed, 7 May 2014 10:27:26 -0400 [thread overview]
Message-ID: <1399472847-14377-3-git-send-email-ashwin.chaugule@linaro.org> (raw)
In-Reply-To: <1399472847-14377-1-git-send-email-ashwin.chaugule@linaro.org>
The PSCI v0.2+ spec defines standard values for PSCI function IDs.
Add a new binding entry so that pre v0.2 implementations can
use DT entries for function IDs and v0.2+ implementations use
standard entries as defined by the PSCIv0.2 specification.
Signed-off-by: Ashwin Chaugule <ashwin.chaugule@linaro.org>
Acked-by: Rob Herring <robh@kernel.org>
---
Documentation/devicetree/bindings/arm/psci.txt | 35 +++++++++++++++++++++++++-
1 file changed, 34 insertions(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/arm/psci.txt b/Documentation/devicetree/bindings/arm/psci.txt
index 433afe9..d01a90b 100644
--- a/Documentation/devicetree/bindings/arm/psci.txt
+++ b/Documentation/devicetree/bindings/arm/psci.txt
@@ -21,7 +21,15 @@ to #0.
Main node required properties:
- - compatible : Must be "arm,psci"
+ - compatible : should contain at least one of:
+
+ * "arm,psci" : for implementations complying to PSCI versions prior to
+ 0.2. For these cases function IDs must be provided.
+
+ * "arm,psci-0.2" : for implementations complying to PSCI 0.2. Function
+ IDs are not required and should be ignored by an OS with PSCI 0.2
+ support, but are permitted to be present for compatibility with
+ existing software when "arm,psci" is later in the compatible list.
- method : The method of calling the PSCI firmware. Permitted
values are:
@@ -45,6 +53,8 @@ Main node optional properties:
Example:
+Case 1: PSCI v0.1 only.
+
psci {
compatible = "arm,psci";
method = "smc";
@@ -53,3 +63,26 @@ Example:
cpu_on = <0x95c10002>;
migrate = <0x95c10003>;
};
+
+
+Case 2: PSCI v0.2 only
+
+ psci {
+ compatible = "arm,psci-0.2";
+ method = "smc";
+ };
+
+Case 3: PSCI v0.2 and PSCI v0.1.
+
+ As described above, for compatibility with existing kernels, the
+ hypervisor will likely want to provide IDs, e.g.
+
+ psci {
+ compatible = "arm,psci-0.2", "arm,psci";
+ method = "hvc";
+
+ cpu_on = < arbitrary value >;
+ cpu_off = < arbitrary value >;
+
+ ...
+ };
--
1.8.3.2
next prev parent reply other threads:[~2014-05-07 14:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-07 14:27 [PATCH v9 0/3] PSCI v0.2 support and DT bindings Ashwin Chaugule
2014-05-07 14:27 ` [PATCH v9 1/3] PSCI: Add initial support for PSCIv0.2 functions Ashwin Chaugule
2014-05-11 8:14 ` Anup Patel
2014-05-12 13:52 ` Ashwin Chaugule
2014-05-12 9:10 ` Mark Rutland
2014-05-12 14:02 ` Ashwin Chaugule
2014-05-13 17:09 ` Ashwin Chaugule
2014-05-13 21:29 ` Catalin Marinas
2014-05-07 14:27 ` Ashwin Chaugule [this message]
2014-05-12 8:54 ` [PATCH v9 2/3] Documentation: devicetree: Add new binding for PSCIv0.2 Mark Rutland
2014-05-07 14:27 ` [PATCH v9 3/3] ARM: Check if a CPU has gone offline Ashwin Chaugule
2014-05-12 10:16 ` Mark Rutland
2014-05-12 13:49 ` Ashwin Chaugule
2014-05-08 4:48 ` [PATCH v9 0/3] PSCI v0.2 support and DT bindings Ashwin Chaugule
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=1399472847-14377-3-git-send-email-ashwin.chaugule@linaro.org \
--to=ashwin.chaugule@linaro.org \
--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).