From: "Jason-JH Lin (林睿祥)" <Jason-JH.Lin@mediatek.com>
To: "conor@kernel.org" <conor@kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"Singo Chang (張興國)" <Singo.Chang@mediatek.com>,
"linux-mediatek@lists.infradead.org"
<linux-mediatek@lists.infradead.org>,
"Johnson Wang (王聖鑫)" <Johnson.Wang@mediatek.com>,
"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
"chunkuang.hu@kernel.org" <chunkuang.hu@kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"Jason-ch Chen (陳建豪)" <Jason-ch.Chen@mediatek.com>,
"Shawn Sung (宋孝謙)" <Shawn.Sung@mediatek.com>,
"Nancy Lin (林欣螢)" <Nancy.Lin@mediatek.com>,
"conor+dt@kernel.org" <conor+dt@kernel.org>,
Project_Global_Chrome_Upstream_Group
<Project_Global_Chrome_Upstream_Group@mediatek.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"krzysztof.kozlowski+dt@linaro.org"
<krzysztof.kozlowski+dt@linaro.org>,
"matthias.bgg@gmail.com" <matthias.bgg@gmail.com>,
"jassisinghbrar@gmail.com" <jassisinghbrar@gmail.com>,
"angelogioacchino.delregno@collabora.com"
<angelogioacchino.delregno@collabora.com>
Subject: Re: [PATCH v2 2/4] dt-bindings: mailbox: mediatek: gce-mailbox: Add reference to gce-props.yaml
Date: Wed, 10 Jan 2024 16:36:20 +0000 [thread overview]
Message-ID: <8c4004d5b6f68dc096aaf2a537e429c310b60c08.camel@mediatek.com> (raw)
In-Reply-To: <20240110-grumbling-tattling-0202fc5e21f2@spud>
Hi Conor,
Thanks for the reviews.
On Wed, 2024-01-10 at 10:36 +0000, Conor Dooley wrote:
> On Wed, Jan 10, 2024 at 02:35:30PM +0800, Jason-JH.Lin wrote:
> > 1. Add "Provider" to the title to make it clearer.
> > 2. Add reference to gce-props.yaml for adding mediatek,gce-events
> > property.
>
> I can see this from the diff. There's still no explanation here as to
> why the mailbox provider needs to have a gce-event id. NAK until you
> can
> explain that.
>
Sorry for missing the reason in commit message, I'll add it in the next
version.
There are 2 reasons why the mailbox provider needs gce-events:
1. The mailbox provider here is CMDQ mailbox driver. It configures GCE
hardware register by CPU directly. If we want to set the default value
from 0 to 1 for specific gce-events during the initialization of CMDQ
driver. We need to tell CMDQ driver what gce-events need to be set and
I think such GCE hardware setting can get from its device node.
2. We'll have the secure CMDQ mailbox driver in the future patch [1].
It will request or reserve a mailbox channel, which is a dedicate GCE
thread, as a secure IRQ handler. This GCE thread executes a looping
instruction set that keeps waiting for the gce-event set from another
GCE thread in the secure world. So we also need to tell the CMDQ driver
what gce-event need to be waited.
[1] cmdq_sec_irq_notify_start() is where the GCE thread is requested to
prepare a looping instruction set to wait for the gce-event.
-
https://patchwork.kernel.org/project/linux-mediatek/patch/20231222045228.27826-9-jason-jh.lin@mediatek.com/
Regards,
Jason-JH.Lin
> Cheers,
> Conor.
>
> >
> > Signed-off-by: Jason-JH.Lin <jason-jh.lin@mediatek.com>
> > ---
> > .../devicetree/bindings/mailbox/mediatek,gce-mailbox.yaml | 6
> > ++++--
> > 1 file changed, 4 insertions(+), 2 deletions(-)
> >
> > diff --git
> > a/Documentation/devicetree/bindings/mailbox/mediatek,gce-
> > mailbox.yaml
> > b/Documentation/devicetree/bindings/mailbox/mediatek,gce-
> > mailbox.yaml
> > index cef9d7601398..728dc93117a6 100644
> > --- a/Documentation/devicetree/bindings/mailbox/mediatek,gce-
> > mailbox.yaml
> > +++ b/Documentation/devicetree/bindings/mailbox/mediatek,gce-
> > mailbox.yaml
> > @@ -4,7 +4,7 @@
> > $id:
> > http://devicetree.org/schemas/mailbox/mediatek,gce-mailbox.yaml#
> > $schema: http://devicetree.org/meta-schemas/core.yaml#
> >
> > -title: Mediatek Global Command Engine Mailbox
> > +title: MediaTek Global Command Engine Mailbox Provider
> >
> > maintainers:
> > - Houlong Wei <houlong.wei@mediatek.com>
> > @@ -57,6 +57,8 @@ required:
> > - clocks
> >
> > allOf:
> > + - $ref: mediatek,gce-props.yaml
> > +
> > - if:
> > not:
> > properties:
> > @@ -67,7 +69,7 @@ allOf:
> > required:
> > - clock-names
> >
> > -additionalProperties: false
> > +unevaluatedProperties: false
> >
> > examples:
> > - |
> > --
> > 2.18.0
> >
next prev parent reply other threads:[~2024-01-10 16:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-10 6:35 [PATCH v2 0/4] Add mediatek,gce-props.yaml for other bindings reference mediatek,gce-events Jason-JH.Lin
2024-01-10 6:35 ` [PATCH v2 1/4] dt-bindings: mailbox: Add mediatek,gce-props.yaml Jason-JH.Lin
2024-01-12 7:20 ` Krzysztof Kozlowski
2024-01-12 8:09 ` Jason-JH Lin (林睿祥)
2024-01-10 6:35 ` [PATCH v2 2/4] dt-bindings: mailbox: mediatek: gce-mailbox: Add reference to gce-props.yaml Jason-JH.Lin
2024-01-10 10:36 ` Conor Dooley
2024-01-10 16:36 ` Jason-JH Lin (林睿祥) [this message]
2024-01-11 17:31 ` Conor Dooley
2024-01-12 7:44 ` Jason-JH Lin (林睿祥)
2024-01-15 17:23 ` Conor Dooley
2024-01-16 8:21 ` Jason-JH Lin (林睿祥)
2024-01-16 17:22 ` Conor Dooley
2024-01-17 2:24 ` Jason-JH Lin (林睿祥)
2024-01-10 6:35 ` [PATCH v2 3/4] dt-bindings: media: mediatek: mdp: Change mediatek,gce-events to reference Jason-JH.Lin
2024-01-12 7:22 ` Krzysztof Kozlowski
2024-01-12 7:53 ` Jason-JH Lin (林睿祥)
2024-01-10 6:35 ` [PATCH v2 4/4] dt-bindings: soc: mediatek: Change mediatek,gce-events to refernece Jason-JH.Lin
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=8c4004d5b6f68dc096aaf2a537e429c310b60c08.camel@mediatek.com \
--to=jason-jh.lin@mediatek.com \
--cc=Jason-ch.Chen@mediatek.com \
--cc=Johnson.Wang@mediatek.com \
--cc=Nancy.Lin@mediatek.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=Shawn.Sung@mediatek.com \
--cc=Singo.Chang@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=chunkuang.hu@kernel.org \
--cc=conor+dt@kernel.org \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jassisinghbrar@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=robh+dt@kernel.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