From: Krzysztof Kozlowski <krzk@kernel.org>
To: Zhentao Guo <zhentao.guo@amlogic.com>, Rob Herring <robh@kernel.org>
Cc: Jerome Brunet <jbrunet@baylibre.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Neil Armstrong <neil.armstrong@linaro.org>,
Kevin Hilman <khilman@baylibre.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
devicetree@vger.kernel.org, Conor Dooley <conor+dt@kernel.org>,
linux-amlogic@lists.infradead.org, linux-media@vger.kernel.org,
Krzysztof Kozlowski <krzk+dt@kernel.org>
Subject: Re: [PATCH RFC v2 0/3] Add Amlogic stateless H.264 video decoder for S4
Date: Tue, 25 Nov 2025 12:29:48 +0100 [thread overview]
Message-ID: <ae1fe925-3e3b-428d-9bae-a587ca5e37f6@kernel.org> (raw)
In-Reply-To: <5faeb411-91d0-42e2-9bf8-3051045ff42c@amlogic.com>
On 25/11/2025 04:24, Zhentao Guo wrote:
>> (or use b4 which does this automatically)
>>
>> New warnings running 'make CHECK_DTBS=y for arch/arm64/boot/dts/amlogic/' for 20251124-b4-s4-vdec-upstream-v2-0-bdbbce3f11a6@amlogic.com:
>>
>> arch/arm64/boot/dts/amlogic/meson-s4-s805x2-aq222.dtb: video-codec@fe320000 (amlogic,s4-vcodec-dec): 'amlogic,canvas' does not match any of the regexes: '^pinctrl-[0-9]+$'
>> from schema $id: http://devicetree.org/schemas/media/amlogic,vcodec-dec.yaml
> Yes, this is a problem. We renamed the dt-binding file and added new
> node to the dts in this patch series, but the dt-binding was not fully
> updated. We'll fix this warning in the next version.
The problem is that you did not test it before sending.
Best regards,
Krzysztof
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next prev parent reply other threads:[~2025-11-25 11:30 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-24 3:32 Zhentao Guo via B4 Relay
2025-11-24 3:32 ` [PATCH RFC v2 1/3] media: dt-bindings: Add Amlogic V4L2 video decoder Zhentao Guo via B4 Relay
2025-11-25 11:31 ` Krzysztof Kozlowski
2025-11-25 11:45 ` Zhentao Guo
2025-12-16 23:43 ` Martin Blumenstingl
2025-12-17 2:38 ` Zhentao Guo
2025-11-24 3:32 ` [PATCH RFC v2 2/3] decoder: Add V4L2 stateless H.264 decoder driver Zhentao Guo via B4 Relay
2025-12-11 19:53 ` Nicolas Dufresne
2025-12-12 4:11 ` Zhentao Guo
2025-12-12 13:51 ` Nicolas Dufresne
2025-12-15 2:15 ` Zhentao Guo
2025-12-15 13:58 ` Nicolas Dufresne
2025-12-16 2:36 ` Zhentao Guo
2025-12-16 2:36 ` Zhentao Guo
2025-11-24 3:32 ` [PATCH RFC v2 3/3] arm64: dts: amlogic: Add video decoder driver support for S4 SOCs Zhentao Guo via B4 Relay
2025-11-24 14:28 ` [PATCH RFC v2 0/3] Add Amlogic stateless H.264 video decoder for S4 Rob Herring
2025-11-25 3:24 ` Zhentao Guo
2025-11-25 11:29 ` Krzysztof Kozlowski [this message]
2025-11-25 11:47 ` Zhentao Guo
2025-11-25 10:55 ` Ferass El Hafidi
2025-11-25 11:15 ` Zhentao Guo
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=ae1fe925-3e3b-428d-9bae-a587ca5e37f6@kernel.org \
--to=krzk@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jbrunet@baylibre.com \
--cc=khilman@baylibre.com \
--cc=krzk+dt@kernel.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=mchehab@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=robh@kernel.org \
--cc=zhentao.guo@amlogic.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