From: Jens Wiklander <jens.wiklander@linaro.org>
To: Sumit Garg <sumit.garg@linaro.org>
Cc: Etienne Carriere <etienne.carriere@linaro.org>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
op-tee@lists.trustedfirmware.org,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
Subject: Re: [PATCH v6 1/2] dt-bindings: optee driver interrupt can be a per-cpu interrupt
Date: Thu, 30 Mar 2023 11:23:00 +0200 [thread overview]
Message-ID: <20230330092300.GB990388@rayden> (raw)
In-Reply-To: <CAFA6WYP09nmgXafdqZnpBfoe_rHTDCDy+BV8d8jjC-V9mCADSQ@mail.gmail.com>
On Wed, Mar 22, 2023 at 08:26:22PM +0530, Sumit Garg wrote:
> On Wed, 22 Mar 2023 at 18:52, Etienne Carriere
> <etienne.carriere@linaro.org> wrote:
> >
> > Explicit in optee firmware device tree bindings that the interrupt
> > used by optee driver for async notification can be a peripheral
> > interrupt or a per-cpu interrupt.
> >
> > Signed-off-by: Etienne Carriere <etienne.carriere@linaro.org>
> > ---
> > No change since v5
> >
>
> Reviewed-by: Sumit Garg <sumit.garg@linaro.org>
I'm picking up this.
Thanks,
Jens
>
> -Sumit
>
> > No change since v4
> >
> > Changes since v3:
> > - Patch added in this v4 to address review comments.
> > ---
> > .../devicetree/bindings/arm/firmware/linaro,optee-tz.yaml | 3 ++-
> > 1 file changed, 2 insertions(+), 1 deletion(-)
> >
> > diff --git a/Documentation/devicetree/bindings/arm/firmware/linaro,optee-tz.yaml b/Documentation/devicetree/bindings/arm/firmware/linaro,optee-tz.yaml
> > index d4dc0749f9fd..5d033570b57b 100644
> > --- a/Documentation/devicetree/bindings/arm/firmware/linaro,optee-tz.yaml
> > +++ b/Documentation/devicetree/bindings/arm/firmware/linaro,optee-tz.yaml
> > @@ -28,7 +28,8 @@ properties:
> > maxItems: 1
> > description: |
> > This interrupt which is used to signal an event by the secure world
> > - software is expected to be edge-triggered.
> > + software is expected to be either a per-cpu interrupt or an
> > + edge-triggered peripheral interrupt.
> >
> > method:
> > enum: [smc, hvc]
> > --
> > 2.25.1
> >
prev parent reply other threads:[~2023-03-30 9:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-22 13:22 [PATCH v6 1/2] dt-bindings: optee driver interrupt can be a per-cpu interrupt Etienne Carriere
2023-03-22 13:22 ` [PATCH v6 2/2] optee: add per cpu asynchronous notification Etienne Carriere
2023-03-22 14:58 ` Sumit Garg
2023-03-30 9:22 ` Jens Wiklander
2023-03-22 14:56 ` [PATCH v6 1/2] dt-bindings: optee driver interrupt can be a per-cpu interrupt Sumit Garg
2023-03-30 9:23 ` Jens Wiklander [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230330092300.GB990388@rayden \
--to=jens.wiklander@linaro.org \
--cc=etienne.carriere@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=op-tee@lists.trustedfirmware.org \
--cc=robh+dt@kernel.org \
--cc=sumit.garg@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox