From: peng.fan@nxp.com
To: sudeep.holla@arm.com, robh+dt@kernel.org, mark.rutland@arm.com
Cc: viresh.kumar@linaro.org, f.fainelli@gmail.com, linux-imx@nxp.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
andre.przywara@arm.com, Peng Fan <peng.fan@nxp.com>
Subject: [PATCH V2 1/2] dt-bindings: arm: arm,scmi: add smc/hvc transports
Date: Thu, 13 Feb 2020 11:58:49 +0800 [thread overview]
Message-ID: <1581566330-1029-2-git-send-email-peng.fan@nxp.com> (raw)
In-Reply-To: <1581566330-1029-1-git-send-email-peng.fan@nxp.com>
From: Peng Fan <peng.fan@nxp.com>
SCMI could use SMC/HVC as tranports. Since there is no
standardized id, we need to use vendor specific id. So
add into devicetree binding doc.
Signed-off-by: Peng Fan <peng.fan@nxp.com>
---
Documentation/devicetree/bindings/arm/arm,scmi.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/arm/arm,scmi.txt b/Documentation/devicetree/bindings/arm/arm,scmi.txt
index f493d69e6194..dacc62dc248b 100644
--- a/Documentation/devicetree/bindings/arm/arm,scmi.txt
+++ b/Documentation/devicetree/bindings/arm/arm,scmi.txt
@@ -25,6 +25,7 @@ The scmi node with the following properties shall be under the /firmware/ node.
protocol identifier for a given sub-node.
- #size-cells : should be '0' as 'reg' property doesn't have any size
associated with it.
+- smc-id : SMC id required when using smc or hvc transports
Optional properties:
--
2.16.4
next prev parent reply other threads:[~2020-02-13 4:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-13 3:58 [PATCH V2 0/2] firmware: arm_scmi: add smc/hvc transports support peng.fan
2020-02-13 3:58 ` peng.fan [this message]
2020-02-13 10:54 ` [PATCH V2 1/2] dt-bindings: arm: arm,scmi: add smc/hvc transports Sudeep Holla
2020-02-14 0:59 ` Peng Fan
2020-02-13 3:58 ` [PATCH V2 2/2] firmware: arm_scmi: " peng.fan
2020-02-13 11:04 ` Sudeep Holla
2020-02-14 1:04 ` Peng Fan
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=1581566330-1029-2-git-send-email-peng.fan@nxp.com \
--to=peng.fan@nxp.com \
--cc=andre.przywara@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=sudeep.holla@arm.com \
--cc=viresh.kumar@linaro.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).