From: Krzysztof Kozlowski <krzk@kernel.org>
To: "Irui Wang (王瑞)" <Irui.Wang@mediatek.com>,
"Kyrie Wu (吴晗)" <Kyrie.Wu@mediatek.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mediatek@lists.infradead.org"
<linux-mediatek@lists.infradead.org>,
"George Sun (孙林)" <George.Sun@mediatek.com>,
"Tiffany Lin (林慧珊)" <tiffany.lin@mediatek.com>,
"andrzejtp2010@gmail.com" <andrzejtp2010@gmail.com>,
"nhebert@chromium.org" <nhebert@chromium.org>,
"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"mchehab@kernel.org" <mchehab@kernel.org>,
"hverkuil@xs4all.nl" <hverkuil@xs4all.nl>,
"nicolas.dufresne@collabora.com" <nicolas.dufresne@collabora.com>,
"Yunfei Dong (董云飞)" <Yunfei.Dong@mediatek.com>,
"conor+dt@kernel.org" <conor+dt@kernel.org>,
"robh@kernel.org" <robh@kernel.org>,
"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>,
"christophe.jaillet@wanadoo.fr" <christophe.jaillet@wanadoo.fr>,
"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
"arnd@arndb.de" <arnd@arndb.de>,
"Andrew-CT Chen (陳智迪)" <Andrew-CT.Chen@mediatek.com>,
"AngeloGioacchino Del Regno"
<angelogioacchino.delregno@collabora.com>,
"neil.armstrong@linaro.org" <neil.armstrong@linaro.org>
Subject: Re: [PATCH v3 5/6] dt-bindings: media: Add MT8196 mediatek,vcodec-encoder
Date: Wed, 20 Aug 2025 07:55:38 +0200 [thread overview]
Message-ID: <aab06f96-83c9-4e1c-9e1b-6148a3055e67@kernel.org> (raw)
In-Reply-To: <cff7beabdfce15b014597f6fbb0ea23375ecb902.camel@mediatek.com>
On 20/08/2025 04:55, Irui Wang (王瑞) wrote:
> Dear Krzysztof,
>
> Thanks for your reviewing.
>
> On Fri, 2025-08-15 at 10:54 +0200, Krzysztof Kozlowski wrote:
>> External email : Please do not click links or open attachments until
>> you have verified the sender or the content.
>>
>>
>> On Thu, Aug 14, 2025 at 04:56:41PM +0800, Kyrie Wu wrote:
>>> From: Irui Wang <irui.wang@mediatek.com>
>>>
>>> Add MT8196 encoder compatible string, which will reference VCP
>>> device.
>>
>> You ignored comments from v2.
>
> I think I misunderstood the v2 comments, I rewrote the title because it
> said dt-bindings and encoder twice, this is not enough, right? we need
> to describe more information in Body text?
where are lore links in the changelog? Why aren't you using b4 to submit
patches?
>
>>
>>>
>>> Signed-off-by: Irui Wang <irui.wang@mediatek.com>
>>
>> Incorrect SoB chain.
>>
>>> ---
>>> .../bindings/media/mediatek,vcodec-encoder.yaml | 17
>>> +++++++++++++++++
>>> 1 file changed, 17 insertions(+)
>>>
>>> diff --git
>>> a/Documentation/devicetree/bindings/media/mediatek,vcodec-
>>> encoder.yaml
>>> b/Documentation/devicetree/bindings/media/mediatek,vcodec-
>>> encoder.yaml
>>> index ebc615584f92..bb4dbf23ccc5 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,11 @@ properties:
>>> description:
>>> Describes point to scp.
>>>
>>> + mediatek,vcp:
>>> + $ref: /schemas/types.yaml#/definitions/phandle
>>> + description:
>>> + Describes point to vcp.
>>
>> For what? You just repeated the property name. You must say here
>> something useful instead: why this is needed, what is its purpose.
>
> I would like to say:
> "define this 'mediatek,vcp' property here, this is a phandle point to
Don't explain to us what DT is. Above is 100% redundant.
> vcp device, for platforms using vcp firmware."
Explain what is the purpose of this in hardware, how hardware uses it,
what problem for hardware this addresses.
>
> Is this OK for you?
>>
>>
>
>>> +
>>> power-domains:
>>> maxItems: 1
>>>
>>> @@ -76,6 +82,17 @@ required:
>>> - iommus
>>>
>>> allOf:
>>> + - if:
>>> + properties:
>>> + compatible:
>>> + contains:
>>> + enum:
>>> + - mediatek,mt8196-vcodec-enc
>>> +
>>> + then:
>>> + required:
>>> + - mediatek,vcp
>>
>> else
>>
>> mediatek,vcp: false
>
> I think the else statement is no need here. Different platforms are
> using different firmware phandle, vpu, scp, and vcp. so we use if-then
> to describe the required property for these platforms.
Hm? I just told you it is needed. Otherwise, explain why each
variant/device has now VCP.
You have entire commit msg to explain all this.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-08-20 5:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-14 8:56 [PATCH v3 0/6] Add support for MT8196 video encoder Kyrie Wu
2025-08-14 8:56 ` [PATCH v3 1/6] media: mediatek: encoder: Add a new encoder driver interface Kyrie Wu
2025-11-14 21:27 ` Nicolas Dufresne
2025-08-14 8:56 ` [PATCH v3 2/6] media: mediatek: encoder: Add support for common firmware interface Kyrie Wu
2025-11-14 21:31 ` Nicolas Dufresne
2025-08-14 8:56 ` [PATCH v3 3/6] media: mediatek: encoder: Add support for VCP encode process Kyrie Wu
2025-11-14 21:39 ` Nicolas Dufresne
2025-08-14 8:56 ` [PATCH v3 4/6] media: mediatek: encoder: Add a new platform data member Kyrie Wu
2025-11-14 21:40 ` Nicolas Dufresne
2025-08-14 8:56 ` [PATCH v3 5/6] dt-bindings: media: Add MT8196 mediatek,vcodec-encoder Kyrie Wu
2025-08-15 8:54 ` Krzysztof Kozlowski
2025-08-20 2:55 ` Irui Wang (王瑞)
2025-08-20 5:55 ` Krzysztof Kozlowski [this message]
2025-08-20 8:24 ` Irui Wang (王瑞)
2025-08-14 8:56 ` [PATCH v3 6/6] media: mediatek: encoder: Add MT8196 encoder compatible data 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=aab06f96-83c9-4e1c-9e1b-6148a3055e67@kernel.org \
--to=krzk@kernel.org \
--cc=Andrew-CT.Chen@mediatek.com \
--cc=George.Sun@mediatek.com \
--cc=Irui.Wang@mediatek.com \
--cc=Kyrie.Wu@mediatek.com \
--cc=Yunfei.Dong@mediatek.com \
--cc=andrzejtp2010@gmail.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=arnd@arndb.de \
--cc=christophe.jaillet@wanadoo.fr \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hverkuil@xs4all.nl \
--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=neil.armstrong@linaro.org \
--cc=nhebert@chromium.org \
--cc=nicolas.dufresne@collabora.com \
--cc=robh@kernel.org \
--cc=sebastian.fricke@collabora.com \
--cc=tiffany.lin@mediatek.com \
/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®