From: peng.fan@nxp.com To: sudeep.holla@arm.com, robh+dt@kernel.org 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, Peng Fan <peng.fan@nxp.com> Subject: [PATCH V5 1/2] dt-bindings: arm: arm,scmi: add smc/hvc transport Date: Sun, 8 Mar 2020 21:24:38 +0800 [thread overview] Message-ID: <1583673879-20714-2-git-send-email-peng.fan@nxp.com> (raw) In-Reply-To: <1583673879-20714-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. Also add arm,scmi-smc compatible string for smc/hvc transport Reviewed-by: Rob Herring <robh@kernel.org> Signed-off-by: Peng Fan <peng.fan@nxp.com> --- Documentation/devicetree/bindings/arm/arm,scmi.txt | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/Documentation/devicetree/bindings/arm/arm,scmi.txt b/Documentation/devicetree/bindings/arm/arm,scmi.txt index f493d69e6194..4ce57b88f84d 100644 --- a/Documentation/devicetree/bindings/arm/arm,scmi.txt +++ b/Documentation/devicetree/bindings/arm/arm,scmi.txt @@ -14,7 +14,7 @@ Required properties: The scmi node with the following properties shall be under the /firmware/ node. -- compatible : shall be "arm,scmi" +- compatible : shall be "arm,scmi" or "arm,scmi-smc" for smc/hvc transports - mboxes: List of phandle and mailbox channel specifiers. It should contain exactly one or two mailboxes, one for transmitting messages("tx") and another optional for receiving the notifications("rx") if @@ -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. +- arm,smc-id : SMC id required when using smc or hvc transports Optional properties: -- 2.16.4
WARNING: multiple messages have this Message-ID (diff)
From: peng.fan@nxp.com To: sudeep.holla@arm.com, robh+dt@kernel.org Cc: devicetree@vger.kernel.org, Peng Fan <peng.fan@nxp.com>, f.fainelli@gmail.com, viresh.kumar@linaro.org, linux-kernel@vger.kernel.org, linux-imx@nxp.com, linux-arm-kernel@lists.infradead.org Subject: [PATCH V5 1/2] dt-bindings: arm: arm,scmi: add smc/hvc transport Date: Sun, 8 Mar 2020 21:24:38 +0800 [thread overview] Message-ID: <1583673879-20714-2-git-send-email-peng.fan@nxp.com> (raw) In-Reply-To: <1583673879-20714-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. Also add arm,scmi-smc compatible string for smc/hvc transport Reviewed-by: Rob Herring <robh@kernel.org> Signed-off-by: Peng Fan <peng.fan@nxp.com> --- Documentation/devicetree/bindings/arm/arm,scmi.txt | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/Documentation/devicetree/bindings/arm/arm,scmi.txt b/Documentation/devicetree/bindings/arm/arm,scmi.txt index f493d69e6194..4ce57b88f84d 100644 --- a/Documentation/devicetree/bindings/arm/arm,scmi.txt +++ b/Documentation/devicetree/bindings/arm/arm,scmi.txt @@ -14,7 +14,7 @@ Required properties: The scmi node with the following properties shall be under the /firmware/ node. -- compatible : shall be "arm,scmi" +- compatible : shall be "arm,scmi" or "arm,scmi-smc" for smc/hvc transports - mboxes: List of phandle and mailbox channel specifiers. It should contain exactly one or two mailboxes, one for transmitting messages("tx") and another optional for receiving the notifications("rx") if @@ -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. +- arm,smc-id : SMC id required when using smc or hvc transports Optional properties: -- 2.16.4 _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-03-08 13:31 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-03-08 13:24 [PATCH V5 0/2] firmware: arm_scmi: add smc/hvc transports support peng.fan 2020-03-08 13:24 ` peng.fan 2020-03-08 13:24 ` peng.fan [this message] 2020-03-08 13:24 ` [PATCH V5 1/2] dt-bindings: arm: arm,scmi: add smc/hvc transport peng.fan 2020-03-08 16:43 ` Florian Fainelli 2020-03-08 16:43 ` Florian Fainelli 2020-03-08 13:24 ` [PATCH V5 2/2] firmware: arm_scmi: " peng.fan 2020-03-08 13:24 ` peng.fan 2020-03-20 8:27 ` [PATCH V5 0/2] firmware: arm_scmi: add smc/hvc transports support Peng Fan 2020-03-20 8:27 ` Peng Fan 2020-03-20 8:37 ` Sudeep Holla 2020-03-20 8:37 ` Sudeep Holla 2020-03-20 8:40 ` Peng Fan 2020-03-20 8:40 ` Peng Fan 2020-03-27 16:32 ` Sudeep Holla 2020-03-27 16:32 ` Sudeep Holla 2020-03-30 14:05 ` Sudeep Holla 2020-03-30 14:05 ` Sudeep Holla 2020-04-15 10:58 ` [PATCH V5 2/2] firmware: arm_scmi: add smc/hvc transport Etienne Carriere 2020-04-15 10:58 ` Etienne Carriere 2020-04-15 13:16 ` Sudeep Holla 2020-04-15 13:16 ` Sudeep Holla 2020-04-15 14:15 ` Etienne Carriere 2020-04-15 14:15 ` Etienne Carriere
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=1583673879-20714-2-git-send-email-peng.fan@nxp.com \ --to=peng.fan@nxp.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=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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.