From: "Kyrie Wu (吴晗)" <Kyrie.Wu@mediatek.com>
To: "conor@kernel.org" <conor@kernel.org>
Cc: "fshao@chromium.org" <fshao@chromium.org>,
"conor+dt@kernel.org" <conor+dt@kernel.org>,
"Yunfei Dong (董云飞)" <Yunfei.Dong@mediatek.com>,
"fanwu01@zju.edu.cn" <fanwu01@zju.edu.cn>,
"jacopo.mondi@ideasonboard.com" <jacopo.mondi@ideasonboard.com>,
"haoxiang_li2024@163.com" <haoxiang_li2024@163.com>,
"tfiga@chromium.org" <tfiga@chromium.org>,
"rongqianfeng@vivo.com" <rongqianfeng@vivo.com>,
"Andrew-CT Chen (陳智迪)" <Andrew-CT.Chen@mediatek.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"ribalda@chromium.org" <ribalda@chromium.org>,
"wenst@chromium.org" <wenst@chromium.org>,
"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
"kees@kernel.org" <kees@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"benjamin.gaignard@collabora.com"
<benjamin.gaignard@collabora.com>,
"Irui Wang (王瑞)" <Irui.Wang@mediatek.com>,
"Kyrie Wu (吴晗)" <Kyrie.Wu@mediatek.com>,
"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
"p.zabel@pengutronix.de" <p.zabel@pengutronix.de>,
"linux-mediatek@lists.infradead.org"
<linux-mediatek@lists.infradead.org>,
"Tiffany Lin (林慧珊)" <tiffany.lin@mediatek.com>,
"sakari.ailus@linux.intel.com" <sakari.ailus@linux.intel.com>,
"matthias.bgg@gmail.com" <matthias.bgg@gmail.com>,
"AngeloGioacchino Del Regno"
<angelogioacchino.delregno@collabora.com>,
"mchehab@kernel.org" <mchehab@kernel.org>,
"sebastian.fricke@collabora.com" <sebastian.fricke@collabora.com>,
"robh@kernel.org" <robh@kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"tzungbi@kernel.org" <tzungbi@kernel.org>,
"nicolas.dufresne@collabora.com" <nicolas.dufresne@collabora.com>,
"hverkuil+cisco@kernel.org" <hverkuil+cisco@kernel.org>,
"laurent.pinchart+renesas@ideasonboard.com"
<laurent.pinchart+renesas@ideasonboard.com>
Subject: Re: [PATCH v5 11/14] dt-bindings: media: mediatek: vcodec: add decoder dt-bindings for mt8196
Date: Mon, 13 Jul 2026 03:16:14 +0000 [thread overview]
Message-ID: <f7b6225063d1cb92d5ea12d0d40f8a1c1d51c9c8.camel@mediatek.com> (raw)
In-Reply-To: <20260702-parlor-disband-fdc2f049336c@spud>
On Thu, 2026-07-02 at 19:55 +0100, Conor Dooley wrote:
> On Thu, Jul 02, 2026 at 05:39:24AM +0000, Kyrie Wu (吴晗) wrote:
> > On Wed, 2026-06-03 at 17:14 +0100, Conor Dooley wrote:
> > > On Wed, Jun 03, 2026 at 04:40:41PM +0800, Kyrie Wu wrote:
> > > > From: Yunfei Dong <yunfei.dong@mediatek.com>
> > > >
> > > > The MT8196 decoder differs from previous generations in several
> > > > key aspects, most notably in its use of VCP instead of SCP.
> > > > Additionally, the MT8196 enhances codec capabilities by
> > > > supporting
> > > > HEVC Main10 profile decoding. To accommodate these hardware
> > > > changes,
> > > > the binding constraints specify a total of 12 clock inputs,
> > > > consisting of 9 decoder clocks and 3 VCP interface clocks,
> > > > along with 2 power domains covering both the decoder and VCP
> > > > subsystems.
> > >
> > > I'm pretty pretty confused by this statement about constraints,
> > > since
> > > there's none added?
> > > The vcodec-dec node doesn't even seem to permit clocks at all?
> > >
> > Dear Conor,
> >
> > I apologize for any confusion my commit message caused. What I
> > wanted
> > to convey was the hardware differences between the MT8196 and
> > previous
> > ICs. If you feel that the VCP and clock information are not
> > suitable
> > for this location, I would like to rewrite the commit message as
> > follows:
> > Compared to previous ICs, the MT8196 supports a 10-bit decoder and
> > has
> > a decoding capability of 4K@120fps, using a dual hardware decoding
> > architecture of LAT+CORE.
>
> Sure? But your comments about the constraints are odd and I do not
> know
> if that means you omitted changing constraints when you should have?
> For example, using lat+core only permits you 10 input clocks but your
> commit message talks about 12.
>
Dear Conor,
I apologize for any confusion my commit message caused. What I wanted
to convey was the hardware differences between the MT8196 and previous
ICs. I would like to rewrite the commit message as follows:
Compared to previous ICs, the MT8196 supports a 10-bit decoder and has
a decoding capability of 4K@120fps, also supports 36-bit DRAM IOVA
address and Video Power Control to optimize bandwidth and voltage
usage.
I will update the commit message accordingly in the next revision.
Thanks a lot.
Regards,
Kyrie
> >
> > Thanks.
> >
> > Regards,
> > Kyrie.
> > > >
> > > > Signed-off-by: Yunfei Dong <yunfei.dong@mediatek.com>
> > > > Acked-by: Nicolas Dufresne <nicolas.dufresne@collabora.com>
> > > > ---
> > > > .../bindings/media/mediatek,vcodec-subdev-
> > > > decoder.yaml |
> > > > 1 +
> > > > 1 file changed, 1 insertion(+)
> > > >
> > > > diff --git
> > > > a/Documentation/devicetree/bindings/media/mediatek,vcodec-
> > > > subdev-
> > > > decoder.yaml
> > > > b/Documentation/devicetree/bindings/media/mediatek,vcodec-
> > > > subdev-
> > > > decoder.yaml
> > > > index bf8082d87ac0..74e1d88d3056 100644
> > > > --- a/Documentation/devicetree/bindings/media/mediatek,vcodec-
> > > > subdev-decoder.yaml
> > > > +++ b/Documentation/devicetree/bindings/media/mediatek,vcodec-
> > > > subdev-decoder.yaml
> > > > @@ -76,6 +76,7 @@ properties:
> > > > - mediatek,mt8186-vcodec-dec
> > > > - mediatek,mt8188-vcodec-dec
> > > > - mediatek,mt8195-vcodec-dec
> > > > + - mediatek,mt8196-vcodec-dec
> > > >
> > > > reg:
> > > > minItems: 1
> > > > --
> > > > 2.45.2
> > > >
next prev parent reply other threads:[~2026-07-13 3:16 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-03 8:40 [PATCH v5 00/14] media: mediatek: vcodec: support video decoder in mt8196 Kyrie Wu
2026-06-03 8:40 ` [PATCH v5 01/14] media: mediatek: vcodec: support vcp architecture Kyrie Wu
2026-06-03 8:40 ` [PATCH v5 02/14] media: mediatek: vcodec: add driver to support vcp Kyrie Wu
2026-07-16 0:50 ` Nicolas Dufresne
2026-07-17 1:53 ` Kyrie Wu (吴晗)
2026-06-03 8:40 ` [PATCH v5 03/14] media: mediatek: vcodec: add driver to support vcp encoder Kyrie Wu
2026-06-03 8:40 ` [PATCH v5 04/14] media: mediatek: vcodec: get different firmware ipi id Kyrie Wu
2026-06-03 8:40 ` [PATCH v5 05/14] media: mediatek: vcodec: get share memory address Kyrie Wu
2026-06-03 8:40 ` [PATCH v5 06/14] media: mediatek: vcodec: define MT8196 vcodec levels Kyrie Wu
2026-06-03 8:40 ` [PATCH v5 07/14] media: mediatek: vcodec: support 36bit iova address Kyrie Wu
2026-06-03 8:40 ` [PATCH v5 08/14] media: mediatek: vcodec: clean xpc status Kyrie Wu
2026-06-03 8:40 ` [PATCH v5 09/14] media: mediatek: vcodec: add debug information Kyrie Wu
2026-06-03 8:40 ` [PATCH v5 10/14] media: mediatek: vcodec: send share memory address to vcp Kyrie Wu
2026-06-03 8:40 ` [PATCH v5 11/14] dt-bindings: media: mediatek: vcodec: add decoder dt-bindings for mt8196 Kyrie Wu
2026-06-03 16:14 ` Conor Dooley
2026-07-02 5:39 ` Kyrie Wu (吴晗)
2026-07-02 18:55 ` Conor Dooley
2026-07-13 3:16 ` Kyrie Wu (吴晗) [this message]
2026-06-03 8:40 ` [PATCH v5 12/14] media: mediatek: vcodec: add decoder compatible to support mt8196 Kyrie Wu
2026-06-03 8:40 ` [PATCH v5 13/14] media: mediatek: decoder: fill av1 buffer size with picinfo Kyrie Wu
2026-06-03 8:40 ` [PATCH v5 14/14] media: mediatek: decoder: support av1 extend vsi Kyrie Wu
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=f7b6225063d1cb92d5ea12d0d40f8a1c1d51c9c8.camel@mediatek.com \
--to=kyrie.wu@mediatek.com \
--cc=Andrew-CT.Chen@mediatek.com \
--cc=Irui.Wang@mediatek.com \
--cc=Yunfei.Dong@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=benjamin.gaignard@collabora.com \
--cc=conor+dt@kernel.org \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=fanwu01@zju.edu.cn \
--cc=fshao@chromium.org \
--cc=haoxiang_li2024@163.com \
--cc=hverkuil+cisco@kernel.org \
--cc=jacopo.mondi@ideasonboard.com \
--cc=kees@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--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=nicolas.dufresne@collabora.com \
--cc=p.zabel@pengutronix.de \
--cc=ribalda@chromium.org \
--cc=robh@kernel.org \
--cc=rongqianfeng@vivo.com \
--cc=sakari.ailus@linux.intel.com \
--cc=sebastian.fricke@collabora.com \
--cc=tfiga@chromium.org \
--cc=tiffany.lin@mediatek.com \
--cc=tzungbi@kernel.org \
--cc=wenst@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
all inboxes | Powered by JetHome®