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@xxxxxxx> > --- > Cc: Rob Herring <robh@xxxxxxxxxx> > Cc: Krzysztof Kozlowski <krzk+dt@xxxxxxxxxx> > Cc: Conor Dooley <conor+dt@xxxxxxxxxx> > Cc: devicetree@xxxxxxxxxxxxxxx > --- > 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@xxxxxxxxxx>
