| Message ID | 20241021170726.2564329-4-cristian.marussi@arm.com (mailing list archive) |
|---|---|
| State | New |
| Headers | show |
| Series | Expose SCMI Transport properties | expand |
On Mon, 21 Oct 2024 18:07:24 +0100, Cristian Marussi wrote: > Depending on specific hardware and firmware design choices, it may be > possible for different platforms to end up having different requirements > regarding the same transport characteristics. > > Introduce max-msg-size and max-msg properties to describe such platform > specific transport constraints, since they cannot be discovered otherwise. > > Signed-off-by: Cristian Marussi <cristian.marussi@arm.com> > --- > Cc: Rob Herring <robh@kernel.org> > Cc: Krzysztof Kozlowski <krzk+dt@kernel.org> > Cc: Conor Dooley <conor+dt@kernel.org> > Cc: devicetree@vger.kernel.org > --- > v1 --> v2 > - added vendor prefix > - dropped warnings about resonable minimum max-msg-size > - clarified the intended usage of max-msg > - fixed Cc to include all maintainers and using correct e-mails > --- > .../devicetree/bindings/firmware/arm,scmi.yaml | 15 +++++++++++++++ > 1 file changed, 15 insertions(+) > Reviewed-by: Rob Herring (Arm) <robh@kernel.org>
diff --git a/Documentation/devicetree/bindings/firmware/arm,scmi.yaml b/Documentation/devicetree/bindings/firmware/arm,scmi.yaml index 54d7d11bfed4..9d6e1147f9e9 100644 --- a/Documentation/devicetree/bindings/firmware/arm,scmi.yaml +++ b/Documentation/devicetree/bindings/firmware/arm,scmi.yaml @@ -131,6 +131,21 @@ properties: be a non-zero value if set. minimum: 1 + arm,max-msg-size: + $ref: /schemas/types.yaml#/definitions/uint32 + description: + An optional value, expressed in bytes, representing the maximum size + allowed for the payload of messages transmitted on this transport. + + arm,max-msg: + $ref: /schemas/types.yaml#/definitions/uint32 + description: + An optional value representing the maximum number of concurrent in-flight + messages allowed by this transport; this number represents the maximum + number of concurrently outstanding messages that the server can handle on + this platform. If set, the value should be non-zero. + minimum: 1 + arm,smc-id: $ref: /schemas/types.yaml#/definitions/uint32 description:
Depending on specific hardware and firmware design choices, it may be possible for different platforms to end up having different requirements regarding the same transport characteristics. Introduce max-msg-size and max-msg properties to describe such platform specific transport constraints, since they cannot be discovered otherwise. Signed-off-by: Cristian Marussi <cristian.marussi@arm.com> --- Cc: Rob Herring <robh@kernel.org> Cc: Krzysztof Kozlowski <krzk+dt@kernel.org> Cc: Conor Dooley <conor+dt@kernel.org> Cc: devicetree@vger.kernel.org --- v1 --> v2 - added vendor prefix - dropped warnings about resonable minimum max-msg-size - clarified the intended usage of max-msg - fixed Cc to include all maintainers and using correct e-mails --- .../devicetree/bindings/firmware/arm,scmi.yaml | 15 +++++++++++++++ 1 file changed, 15 insertions(+)