On Fri, Oct 18, 2024 at 09:06:00AM +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. > > Cc: devicetree@xxxxxxxxxxxxxxx > Cc: Rob Herring (Arm) <robh@xxxxxxxxxx> > Cc: Krzysztof Kozlowski <krzysztof.kozlowski@xxxxxxxxxx> > Signed-off-by: Cristian Marussi <cristian.marussi@xxxxxxx> > --- > .../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 54d7d11bfed4..42852ed887f2 100644 > --- a/Documentation/devicetree/bindings/firmware/arm,scmi.yaml > +++ b/Documentation/devicetree/bindings/firmware/arm,scmi.yaml > @@ -131,6 +131,22 @@ properties: > be a non-zero value if set. > minimum: 1 > > + max-msg-size: Vendor prefix needed. > + $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. > + If set it is recommended to be greater or equal than the minimum size > + required to support all the messages defined by the set of protocols > + implemented on this platform. Sounds kind of broken if less than the minimum... > + > + max-msg: Vendor prefix and could be a bit more specific what this is. > + $ref: /schemas/types.yaml#/definitions/uint32 > + description: > + An optional value representing the maximum number of concurrent in-flight > + messages allowed by this transport. If set, the value should be non-zero. > + minimum: 1 > + > arm,smc-id: > $ref: /schemas/types.yaml#/definitions/uint32 > description: > -- > 2.46.1 >
