From: "Irui Wang (王瑞)" <Irui.Wang@mediatek.com>
To: "krzk@kernel.org" <krzk@kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"Longfei Wang (王龙飞)" <Longfei.Wang@mediatek.com>,
"Tiffany Lin (林慧珊)" <tiffany.lin@mediatek.com>,
"wenst@chromium.org" <wenst@chromium.org>,
"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"Maoguang Meng (孟毛广)" <Maoguang.Meng@mediatek.com>,
"linux-mediatek@lists.infradead.org"
<linux-mediatek@lists.infradead.org>,
"nicolas.dufresne@collabora.com" <nicolas.dufresne@collabora.com>,
"mchehab@kernel.org" <mchehab@kernel.org>,
"Kyrie Wu (吴晗)" <Kyrie.Wu@mediatek.com>,
"Yunfei Dong (董云飞)" <Yunfei.Dong@mediatek.com>,
Project_Global_Chrome_Upstream_Group
<Project_Global_Chrome_Upstream_Group@mediatek.com>,
"hverkuil-cisco@xs4all.nl" <hverkuil-cisco@xs4all.nl>,
"sebastian.fricke@collabora.com" <sebastian.fricke@collabora.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"matthias.bgg@gmail.com" <matthias.bgg@gmail.com>,
"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
"AngeloGioacchino Del Regno"
<angelogioacchino.delregno@collabora.com>
Subject: Re: [PATCH v4 5/6] dt-bindings: media: mediatek,vcodec-encoder: Add MT8196 with VCP support
Date: Fri, 13 Feb 2026 09:27:25 +0000 [thread overview]
Message-ID: <13bf9b8673c6d47e07dee4a233945ed542e9b4f3.camel@mediatek.com> (raw)
In-Reply-To: <20260213-didactic-whispering-impala-ea9e64@quoll>
Dear Krzysztof,
I sincerely apologize for taking up your time to review and respond to
this patch. The maintainers' review comments are very important to us,
so we will never ignore them, there must be some misunderstanding in
this process.
On Fri, 2026-02-13 at 08:52 +0100, Krzysztof Kozlowski wrote:
> On Thu, Feb 12, 2026 at 06:01:02PM +0800, Irui Wang wrote:
> > Add support for MT8196 video encoder which uses VCP (Video Co-
> > Processor)
> > for firmware management. Unlike previous platforms that use
> > SCP/VPU, MT8196
> > requires VCP to load and execute the video encoding firmware, with
> > the
> > encoder communicating through VCP to perform encoding operations.
>
> Again, read review from v2. Subject is still wrong.
From the reviews of v2 and v3, my understanding is that the patch lacks
details, so we add more description for current modification, for 'VCP'
usage. So we are very grateful if you could provide a `correct Subject
` example for us, thanks a lot.
> >
> > Add the "mediatek,mt8196-vcodec-enc" compatible string and
> > introduce
> > the "mediatek,vcp" property to reference the VCP device, which is
> > required for MT8196 encoder operation.
> >
> > Signed-off-by: Irui Wang <irui.wang@mediatek.com>
> > ---
> > .../media/mediatek,vcodec-encoder.yaml | 19
> > +++++++++++++++++++
> > 1 file changed, 19 insertions(+)
> >
> > diff --git
> > a/Documentation/devicetree/bindings/media/mediatek,vcodec-
> > encoder.yaml
> > b/Documentation/devicetree/bindings/media/mediatek,vcodec-
> > encoder.yaml
> > index ebc615584f92..4c8acebeb9d3 100644
> > --- a/Documentation/devicetree/bindings/media/mediatek,vcodec-
> > encoder.yaml
> > +++ b/Documentation/devicetree/bindings/media/mediatek,vcodec-
> > encoder.yaml
> > @@ -24,6 +24,7 @@ properties:
> > - mediatek,mt8188-vcodec-enc
> > - mediatek,mt8192-vcodec-enc
> > - mediatek,mt8195-vcodec-enc
> > + - mediatek,mt8196-vcodec-enc
> > - items:
> > - const: mediatek,mt8186-vcodec-enc
> > - const: mediatek,mt8183-vcodec-enc
> > @@ -58,6 +59,13 @@ properties:
> > description:
> > Describes point to scp.
> >
> > + mediatek,vcp:
> > + $ref: /schemas/types.yaml#/definitions/phandle
> > + description:
> > + Reference to the VCP (Video Co-Processor) device that loads
> > and executes
> > + the video encoding firmware. The encoder communicates with
> > the firmware
> > + through VCP to perform encoding operations.
> > +
> > power-domains:
> > maxItems: 1
> >
> > @@ -76,6 +84,17 @@ required:
> > - iommus
> >
> > allOf:
> > + - if:
> > + properties:
> > + compatible:
> > + contains:
> > + enum:
> > + - mediatek,mt8196-vcodec-enc
> > +
> > + then:
> > + required:
> > + - mediatek,vcp
>
> And here still did not implement the comment. So basically you did
> not
> implement fully v2 and v3.
If you are mean about the `else statement`, I left a comments and want
to get an explanation from you, if you feel that my reply is
unsatisfactory or incorrect, please let me know.
The key point is that our patch can satisfy you and get a Reviewed-by
from you.
Thanks
Best Regards
>
> And if something was not clear, you have entire huge Mediatek
> company,
> with huge budget and enormous resources, to help you instead of
> pushing
> something which ignores review THIRD time.
>
> NAK
>
> Best regards,
> Krzysztof
>
next prev parent reply other threads:[~2026-02-13 9:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-12 10:00 [PATCH v4 0/6] Add support for MT8196 video encoder Irui Wang
2026-02-12 10:00 ` [PATCH v4 1/6] media: mediatek: encoder: Add a new encoder driver interface Irui Wang
2026-02-12 10:00 ` [PATCH v4 2/6] media: mediatek: encoder: Add support for common firmware interface Irui Wang
2026-02-12 10:01 ` [PATCH v4 3/6] media: mediatek: encoder: Add support for VCP encode process Irui Wang
2026-02-12 10:01 ` [PATCH v4 4/6] media: mediatek: encoder: Add a new platform data member Irui Wang
2026-02-12 10:01 ` [PATCH v4 5/6] dt-bindings: media: mediatek,vcodec-encoder: Add MT8196 with VCP support Irui Wang
2026-02-13 7:52 ` Krzysztof Kozlowski
2026-02-13 9:27 ` Irui Wang (王瑞) [this message]
2026-02-13 9:32 ` Krzysztof Kozlowski
2026-02-13 9:47 ` Irui Wang (王瑞)
2026-02-13 9:51 ` Krzysztof Kozlowski
2026-02-13 10:00 ` Irui Wang (王瑞)
2026-02-12 10:01 ` [PATCH v4 6/6] media: mediatek: encoder: Add MT8196 encoder compatible data Irui Wang
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=13bf9b8673c6d47e07dee4a233945ed542e9b4f3.camel@mediatek.com \
--to=irui.wang@mediatek.com \
--cc=Kyrie.Wu@mediatek.com \
--cc=Longfei.Wang@mediatek.com \
--cc=Maoguang.Meng@mediatek.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=Yunfei.Dong@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=hverkuil-cisco@xs4all.nl \
--cc=krzk+dt@kernel.org \
--cc=krzk@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=nicolas.dufresne@collabora.com \
--cc=robh+dt@kernel.org \
--cc=sebastian.fricke@collabora.com \
--cc=tiffany.lin@mediatek.com \
--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®