On Mon, Dec 7, 2020 at 2:01 PM Rob Herring <robh@xxxxxxxxxx> wrote: > > 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.quinlan@xxxxxxxxxxxx> > > --- > > 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...). I gave it a name because (a) its presence is atypical/not common and (b) future changes may add more interrupts and I don't want this interrupt at index 0. As far as "message-serviced", this was Sudeep's suggestion, IIRC, although I had a similarly long name. Sudeep, are you okay with "a2p". Thanks, Jim > > > + > > See Documentation/devicetree/bindings/mailbox/mailbox.txt for more details > > about the generic mailbox controller and client driver bindings. > > > > -- > > 2.17.1 > > > > -- This electronic communication and the information and any files transmitted with it, or attached to it, are confidential and are intended solely for the use of the individual or entity to whom it is addressed and may contain information that is confidential, legally privileged, protected by privacy laws, or otherwise restricted from disclosure to anyone else. If you are not the intended recipient or the person responsible for delivering the e-mail to the intended recipient, you are hereby notified that any use, copying, distributing, dissemination, forwarding, printing, or copying of this e-mail is strictly prohibited. If you received this e-mail in error, please return the e-mail to the sender, delete it from your computer, and destroy any printed copy of it.
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature
