[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230409181918.29270-2-quic_nkela@quicinc.com>
Date: Sun, 9 Apr 2023 11:19:17 -0700
From: Nikunj Kela <quic_nkela@...cinc.com>
To: <sudeep.holla@....com>
CC: <cristian.marussi@....com>, <robh+dt@...nel.org>,
<krzysztof.kozlowski+dt@...aro.org>,
<linux-arm-kernel@...ts.infradead.org>,
<devicetree@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
Nikunj Kela <quic_nkela@...cinc.com>
Subject: [PATCH 1/2] dt-bindings: firmware: arm,scmi: support parameter passing in smc/hvc
Currently, smc/hvc calls are made with smc-id only. The parameters are
all set to zeros. This patch defines two optional device tree bindings,
that can be used to pass parameters in smc/hvc calls.
This is useful when multiple scmi instances are used with common smc-id.
Signed-off-by: Nikunj Kela <quic_nkela@...cinc.com>
---
.../devicetree/bindings/firmware/arm,scmi.yaml | 16 ++++++++++++++++
1 file changed, 16 insertions(+)
diff --git a/Documentation/devicetree/bindings/firmware/arm,scmi.yaml b/Documentation/devicetree/bindings/firmware/arm,scmi.yaml
index 5824c43e9893..08c331a79b80 100644
--- a/Documentation/devicetree/bindings/firmware/arm,scmi.yaml
+++ b/Documentation/devicetree/bindings/firmware/arm,scmi.yaml
@@ -115,6 +115,22 @@ properties:
description:
SMC id required when using smc or hvc transports
+ arm,smc32-params:
+ $ref: /schemas/types.yaml#/definitions/uint32-array
+ description:
+ An optional parameter list passed in smc32 or hvc32 calls
+ default: 0
+ minItems: 1
+ maxItems: 6
+
+ arm,smc64-params:
+ $ref: /schemas/types.yaml#/definitions/uint64-array
+ description:
+ An optional parameter list passed in smc64 or hvc64 calls
+ default: 0
+ minItems: 1
+ maxItems: 6
+
linaro,optee-channel-id:
$ref: /schemas/types.yaml#/definitions/uint32
description:
--
2.17.1
Powered by blists - more mailing lists