From: Hugues FRUCHET <hugues.fruchet@foss.st.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>,
Philipp Zabel <p.zabel@pengutronix.de>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Hans Verkuil <hverkuil@xs4all.nl>, <linux-media@vger.kernel.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
<linux-stm32@st-md-mailman.stormreply.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>, <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
<linux-rockchip@lists.infradead.org>
Cc: Andrzej Pietrasiewicz <andrzej.p@collabora.com>
Subject: Re: [PATCH 1/7] dt-bindings: media: Document STM32MP25 VDEC video decoder
Date: Mon, 9 Oct 2023 15:10:10 +0200 [thread overview]
Message-ID: <b4367291-9e9e-dae3-3b56-c487e714683c@foss.st.com> (raw)
In-Reply-To: <d5dc9b70-00b5-4bda-8fe9-9438f19ecba6@linaro.org>
Hi Krzysztof,
On 10/5/23 21:45, Krzysztof Kozlowski wrote:
> On 04/10/2023 11:15, Hugues Fruchet wrote:
>> Add STM32MP25 VDEC video decoder bindings.
>>
>> Signed-off-by: Hugues Fruchet <hugues.fruchet@foss.st.com>
>> ---
>> .../bindings/media/st,stm32mp25-vdec.yaml | 56 +++++++++++++++++++
>> 1 file changed, 56 insertions(+)
>> create mode 100644 Documentation/devicetree/bindings/media/st,stm32mp25-vdec.yaml
>>
>> diff --git a/Documentation/devicetree/bindings/media/st,stm32mp25-vdec.yaml b/Documentation/devicetree/bindings/media/st,stm32mp25-vdec.yaml
>> new file mode 100644
>> index 000000000000..cf41f704113f
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/media/st,stm32mp25-vdec.yaml
>> @@ -0,0 +1,56 @@
>> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
>> +
>> +%YAML 1.2
>> +---
>> +$id: http://devicetree.org/schemas/media/st,stm32mp25-vdec.yaml#
>> +$schema: http://devicetree.org/meta-schemas/core.yaml#
>> +
>> +title: STMicroelectronics STM32MP25 VDEC video decoder
>> +
>> +maintainers:
>> + - Hugues Fruchet <hugues.fruchet@foss.st.com>
>> +
>> +description:
>> + The STMicroelectronics STM32MP25 SOCs embeds a VDEC video hardware decoder
>> + peripheral based on Verisilicon VC8000NanoD IP (former Hantro G1).
>> +
>> +properties:
>> + compatible:
>> + const: st,stm32mp25-vdec
>> +
>> + reg:
>> + maxItems: 1
>> +
>> + interrupts:
>> + maxItems: 1
>> +
>> + interrupt-names:
>> + maxItems: 1
>
> This must be specific or just drop (little use of names for one entry)
I'll drop in v2.
>
>> +
>> + clocks:
>> + maxItems: 1
>> +
>> + clock-names:
>> + maxItems: 1
>
> Same problem.
I'll drop in v2.
>
>> +
>> +required:
>> + - compatible
>> + - reg
>> + - interrupts
>> + - interrupt-names
>> + - clocks
>> + - clock-names
>> +
>> +additionalProperties: false
>> +
>> +examples:
>> + - |
>> + #include <dt-bindings/interrupt-controller/arm-gic.h>
>> + vdec: vdec@580d0000 {
>
> Drop label. Node name: video-codec
> (assuming this is video coder/decoder)
>
> Node names should be generic. See also an explanation and list of
> examples (not exhaustive) in DT specification:
> https://devicetree-specification.readthedocs.io/en/latest/chapter2-devicetree-basics.html#generic-names-recommendation
I'll do in v2, thanks for pointing-out the "video-codec" generic name.
>
>
> Best regards,
> Krzysztof
>
BR,
Hugues.
next prev parent reply other threads:[~2023-10-09 13:11 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-04 9:15 [PATCH 0/7] Add support for video hardware codec of STMicroelectronics STM32 SoC series Hugues Fruchet
2023-10-04 9:15 ` [PATCH 1/7] dt-bindings: media: Document STM32MP25 VDEC video decoder Hugues Fruchet
2023-10-05 19:45 ` Krzysztof Kozlowski
2023-10-09 13:10 ` Hugues FRUCHET [this message]
2023-10-04 9:15 ` [PATCH 2/7] media: hantro: add support for STM32MP25 VDEC Hugues Fruchet
2023-10-11 15:21 ` Nicolas Dufresne
2023-10-04 9:15 ` [PATCH 3/7] dt-bindings: media: Document STM32MP25 VENC video encoder Hugues Fruchet
2023-10-04 23:41 ` Adam Ford
2023-10-05 7:44 ` Hugues FRUCHET
2023-10-06 16:27 ` Rob Herring
2023-10-09 13:06 ` Hugues FRUCHET
2023-10-05 19:45 ` Krzysztof Kozlowski
2023-10-09 13:49 ` Hugues FRUCHET
2023-10-09 13:56 ` Krzysztof Kozlowski
2023-10-09 14:24 ` Hugues FRUCHET
2023-10-09 14:28 ` Krzysztof Kozlowski
2023-10-09 15:56 ` Hugues FRUCHET
2023-10-04 9:15 ` [PATCH 4/7] media: hantro: add support for STM32MP25 VENC Hugues Fruchet
2023-10-04 9:15 ` [PATCH 5/7] arm64: dts: st: add soc & rifsc structure to stm32mp255 Hugues Fruchet
2023-10-05 19:46 ` Krzysztof Kozlowski
2023-10-09 13:54 ` Hugues FRUCHET
2023-10-04 9:15 ` [PATCH 6/7] arm64: dts: st: add video decoder support " Hugues Fruchet
2023-10-04 9:15 ` [PATCH 7/7] arm64: dts: st: add video encoder " Hugues Fruchet
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=b4367291-9e9e-dae3-3b56-c487e714683c@foss.st.com \
--to=hugues.fruchet@foss.st.com \
--cc=alexandre.torgue@foss.st.com \
--cc=andrzej.p@collabora.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=ezequiel@vanguardiasur.com.ar \
--cc=hverkuil@xs4all.nl \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mchehab@kernel.org \
--cc=mcoquelin.stm32@gmail.com \
--cc=p.zabel@pengutronix.de \
--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;
as well as URLs for NNTP newsgroup(s).