Message ID | 1583673879-20714-2-git-send-email-peng.fan@nxp.com |
---|---|
State | Not Applicable, archived |
Headers | show |
Series | firmware: arm_scmi: add smc/hvc transports support | expand |
On 3/8/2020 6:24 AM, peng.fan@nxp.com wrote: > 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> Reviewed-by: Florian Fainelli <f.fainelli@gmail.com>
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: