Depending on hardware and firmware design choices different platforms can
end-up having different requirements around transport features.
Introduce max-msg-size and max-msg properties to describe platform specific
transport constraints.
Signed-off-by: Cristian Marussi <cristian.marussi@xxxxxxx>
---
.../devicetree/bindings/firmware/arm,scmi.yaml | 15 +++++++++++++++
1 file changed, 15 insertions(+)
diff --git a/Documentation/devicetree/bindings/firmware/arm,scmi.yaml b/Documentation/devicetree/bindings/firmware/arm,scmi.yaml
index 7c9fa07e2ff2..998fde321d82 100644
--- a/Documentation/devicetree/bindings/firmware/arm,scmi.yaml
+++ b/Documentation/devicetree/bindings/firmware/arm,scmi.yaml
@@ -128,6 +128,21 @@ properties:
be a non-zero value if set.
minimum: 1
+ max-msg-size:
+ $ref: /schemas/types.yaml#/definitions/uint32
+ description:
+ An optional value, expressed in bytes, representing the transport maximum
+ message size. The value should at least allow for the 4-bytes SCMI message
+ header to be transmitted if set.
+ minimum: 4
+
+ max-msg:
+ $ref: /schemas/types.yaml#/definitions/uint32
+ description:
+ An optional value representing the transport maximum number of concurrent
+ in-flight messages. The value should be a non-zero value if set.
+ minimum: 1
+
arm,smc-id:
$ref: /schemas/types.yaml#/definitions/uint32
description:
--
2.45.2
