On Thu, Nov 12, 2020 at 12:56:26PM -0500, Jim Quinlan wrote: > In normal use of smc/hvc transport in SCMI the message completion is > indicated by the return of the SMC call. This commit provides for an > optional interrupt named "message-serviced" which is used instead to > indicate the completion of a message. > > Signed-off-by: Jim Quinlan <james.quin...@broadcom.com> > --- > Documentation/devicetree/bindings/arm/arm,scmi.txt | 8 ++++++++ > 1 file changed, 8 insertions(+) > > diff --git a/Documentation/devicetree/bindings/arm/arm,scmi.txt > b/Documentation/devicetree/bindings/arm/arm,scmi.txt > index 55deb68230eb..7cdad11f40b1 100644 > --- a/Documentation/devicetree/bindings/arm/arm,scmi.txt > +++ b/Documentation/devicetree/bindings/arm/arm,scmi.txt > @@ -31,6 +31,14 @@ Optional properties: > > - mbox-names: shall be "tx" or "rx" depending on mboxes entries. > > +- interrupts : when using smc or hvc transports, this optional > + property indicates that msg completion by the platform is indicated > + by an interrupt rather than by the return of the smc call. This > + should not be used except when the platform requires such behavior. > + > +- interrupt-names : if "interrupts" is present, interrupt-names must also > + be present and have the value "message-serviced".
Don't really need names when only one, but wouldn't 'a2p' be more concise and based on SCMI spec (just guessing...). > + > See Documentation/devicetree/bindings/mailbox/mailbox.txt for more details > about the generic mailbox controller and client driver bindings. > > -- > 2.17.1 >
