From: "Jason-JH Lin (林睿祥)" <Jason-JH.Lin@mediatek.com>
To: "robh@kernel.org" <robh@kernel.org>,
"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
"conor+dt@kernel.org" <conor+dt@kernel.org>,
"mchehab@kernel.org" <mchehab@kernel.org>,
"chunkuang.hu@kernel.org" <chunkuang.hu@kernel.org>,
"jassisinghbrar@gmail.com" <jassisinghbrar@gmail.com>
Cc: "linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
"Sirius Wang (王皓昱)" <Sirius.Wang@mediatek.com>,
"Moudy Ho (何宗原)" <Moudy.Ho@mediatek.com>,
"Nancy Lin (林欣螢)" <Nancy.Lin@mediatek.com>,
"Xiandong Wang (王先冬)" <Xiandong.Wang@mediatek.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Project_Global_Chrome_Upstream_Group
<Project_Global_Chrome_Upstream_Group@mediatek.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"linux-mediatek@lists.infradead.org"
<linux-mediatek@lists.infradead.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"fshao@chromium.org" <fshao@chromium.org>,
"Singo Chang (張興國)" <Singo.Chang@mediatek.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"Xavier Chang (張獻文)" <Xavier.Chang@mediatek.com>,
"matthias.bgg@gmail.com" <matthias.bgg@gmail.com>,
"treapking@chromium.org" <treapking@chromium.org>
Subject: Re: [PATCH v4 4/8] soc: mediatek: mtk-cmdq: Add pa_base parsing for unsupported subsys ID hardware
Date: Wed, 5 Mar 2025 09:46:22 +0000 [thread overview]
Message-ID: <03c523e66fd56442f49c38456476cf18be59e8fb.camel@mediatek.com> (raw)
In-Reply-To: <581fc075-25d8-4104-a4ee-8c97e1a017e6@collabora.com>
On Tue, 2025-03-04 at 10:35 +0100, AngeloGioacchino Del Regno wrote:
>
> External email : Please do not click links or open attachments until
> you have verified the sender or the content.
>
>
> Il 18/02/25 06:41, Jason-JH Lin ha scritto:
> > When GCE executes instructions, the corresponding hardware register
> > can be found through the subsys ID. For hardware that does not
> > support
> > subsys ID, its subsys ID will be set to invalid value and its
> > physical
> > address needs to be used to generate GCE instructions.
> >
> > This commit adds a pa_base parsing flow to the cmdq_client_reg
> > structure
> > for these unsupported subsys ID hardware.
> >
>
> Does this work only for the MMINFRA located GCEs, or does this work
> also for
> the legacy ones in MT8173/83/88/92/95 // MT6795/6893/etc?
>
> In order to actually review and decide, I do need to know :-)
>
Yes, it's for the SoCs without subsys ID, it's not related to the
MMINFRA.
This can also work on MT8173/83/92/95 // MT6795/6893/etc.
You can remove the `mediatek,gce-client-reg` properties in their dtsi
and cherry-pick this series to verify it. :-)
Regards,
Jason-JH Lin
> Thanks,
> Angelo
>
>
next prev parent reply other threads:[~2025-03-05 9:48 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-18 5:41 [PATCH v4 0/8] Add GCE support for MT8196 Jason-JH Lin
2025-02-18 5:41 ` [PATCH v4 1/8] dt-bindings: mailbox: mediatek: Add support for MT8196 GCE mailbox Jason-JH Lin
2025-02-18 8:12 ` Krzysztof Kozlowski
2025-02-18 5:41 ` [PATCH v4 2/8] arm64: dts: mediatek: Add GCE header for MT8196 Jason-JH Lin
2025-02-18 5:41 ` [PATCH v4 3/8] mailbox: mtk-cmdq: Add driver data to support " Jason-JH Lin
2025-02-18 9:25 ` CK Hu (胡俊光)
2025-02-22 10:44 ` Jason-JH Lin (林睿祥)
2025-03-04 9:32 ` AngeloGioacchino Del Regno
2025-03-05 8:36 ` Jason-JH Lin (林睿祥)
2025-03-05 12:05 ` AngeloGioacchino Del Regno
2025-03-06 11:00 ` Jason-JH Lin (林睿祥)
2025-03-06 13:08 ` AngeloGioacchino Del Regno
2025-03-07 1:11 ` Jason-JH Lin (林睿祥)
2025-02-18 5:41 ` [PATCH v4 4/8] soc: mediatek: mtk-cmdq: Add pa_base parsing for unsupported subsys ID hardware Jason-JH Lin
2025-03-04 9:35 ` AngeloGioacchino Del Regno
2025-03-05 9:46 ` Jason-JH Lin (林睿祥) [this message]
2025-03-05 11:03 ` AngeloGioacchino Del Regno
2025-03-05 15:58 ` Jason-JH Lin (林睿祥)
2025-03-05 17:40 ` AngeloGioacchino Del Regno
2025-02-18 5:41 ` [PATCH v4 5/8] soc: mediatek: mtk-cmdq: Add mminfra_offset compatibility for DRAM address Jason-JH Lin
2025-03-04 9:37 ` AngeloGioacchino Del Regno
2025-03-05 16:26 ` Jason-JH Lin (林睿祥)
2025-02-18 5:41 ` [PATCH v4 6/8] soc: mediatek: Add programming flow for unsupported subsys ID hardware Jason-JH Lin
2025-03-04 9:41 ` AngeloGioacchino Del Regno
2025-03-05 16:12 ` Jason-JH Lin (林睿祥)
2025-03-05 18:08 ` AngeloGioacchino Del Regno
2025-03-06 11:05 ` Jason-JH Lin (林睿祥)
2025-02-18 5:41 ` [PATCH v4 7/8] drm/mediatek: " Jason-JH Lin
2025-03-06 9:47 ` AngeloGioacchino Del Regno
2025-03-06 11:10 ` Jason-JH Lin (林睿祥)
2025-02-18 5:41 ` [PATCH v4 8/8] media: mediatek: mdp3: " 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=03c523e66fd56442f49c38456476cf18be59e8fb.camel@mediatek.com \
--to=jason-jh.lin@mediatek.com \
--cc=Moudy.Ho@mediatek.com \
--cc=Nancy.Lin@mediatek.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=Singo.Chang@mediatek.com \
--cc=Sirius.Wang@mediatek.com \
--cc=Xavier.Chang@mediatek.com \
--cc=Xiandong.Wang@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=chunkuang.hu@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=fshao@chromium.org \
--cc=jassisinghbrar@gmail.com \
--cc=krzk+dt@kernel.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=mchehab@kernel.org \
--cc=robh@kernel.org \
--cc=treapking@chromium.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