From: sashiko-bot@kernel.org
To: "Zhentao Guo" <zhentao.guo@amlogic.com>
Cc: linux-amlogic@lists.infradead.org, neil.armstrong@linaro.org,
conor+dt@kernel.org, media-ci@linuxtv.org,
devicetree@vger.kernel.org, robh@kernel.org
Subject: Re: [PATCH v11 3/6] media: dt-bindings: Add Amlogic V4L2 video decoder
Date: Mon, 12 Oct 2026 07:13:29 +0000 [thread overview]
Message-ID: <sashiko-outbox-167782@kernel.org> (raw)
In-Reply-To: <20261012-b4-s4-vdec-upstream-v11-3-25939f85ada5@amlogic.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] dt-bindings: media: amlogic,s4-vdec: incomplete validation for interrupts array and names
--
commit 0c8109e65ab164df82b0c800ca621bbe98ed15f7
Author: Zhentao Guo <zhentao.guo@amlogic.com>
media: dt-bindings: Add Amlogic V4L2 video decoder
This patch adds the device tree binding schema for the Amlogic hardware
decoder accelerator. The device supports stateless H.264 decoding on
Amlogic SoCs.
> diff --git a/Documentation/devicetree/bindings/media/amlogic,s4-vdec.yaml b/Documentation/devicetree/bindings/media/amlogic,s4-vdec.yaml
> new file mode 100644
> index 0000000000000..75b9ba3cb08d2
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/media/amlogic,s4-vdec.yaml
> @@ -0,0 +1,114 @@
[ ... ]
> + interrupts:
> + maxItems: 2
> +
> + interrupt-names:
> + items:
> + - const: hvdec
> + - const: vdec
[Severity: Low]
Does the schema need minItems: 2 here for the interrupts array? Without it,
an incomplete node with only 1 interrupt will pass schema checks while still
failing at the driver level when index 1 is requested.
[ ... ]
> +required:
> + - compatible
> + - reg
> + - reg-names
> + - interrupts
> + - clocks
> + - clock-names
> + - power-domains
> + - power-domain-names
> + - resets
> + - amlogic,canvas
> + - amlogic,secure-monitor
[Severity: Low]
Is interrupt-names missing from this required list?
Leaving it out permits incomplete configurations to silently pass schema
validation (dt_binding_check). If the driver fetches the interrupt purely
by index (e.g. platform_get_irq(pdev, IRQ_VDEC) where IRQ_VDEC is enum 1),
omitting interrupt-names from the requirements allows device tree authors
to easily miss the correct ordering or provide only one interrupt, leading
directly to driver probe failures or incorrect interrupt routing at runtime.
[ ... ]
> + reg-names = "dos",
> + "dmc";
> + interrupts = <GIC_SPI 91 IRQ_TYPE_EDGE_RISING>,
> + <GIC_SPI 92 IRQ_TYPE_EDGE_RISING>;
> + clocks = <&clkc_periphs CLKID_DOS>,
[Severity: Low]
Should interrupt-names be included in this example?
The example currently omits interrupt-names completely, demonstrating how a
functionally incomplete node is permitted by the schema.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261012-b4-s4-vdec-upstream-v11-0-25939f85ada5@amlogic.com?part=3
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next prev parent reply other threads:[~2026-10-12 7:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-12 7:06 [PATCH v11 0/6] Add Amlogic stateless H.264 video decoder for S4 Zhentao Guo via B4 Relay
2026-10-12 7:06 ` [PATCH v11 1/6] firmware: meson: sm: video firmware loading via secure monitor Zhentao Guo via B4 Relay
2026-10-12 7:06 ` [PATCH v11 2/6] firmware: meson: sm: Add video firmware loading SMC call Zhentao Guo via B4 Relay
2026-10-12 7:06 ` [PATCH v11 3/6] media: dt-bindings: Add Amlogic V4L2 video decoder Zhentao Guo via B4 Relay
2026-10-12 7:13 ` sashiko-bot [this message]
2026-10-12 7:06 ` [PATCH v11 4/6] decoder: Add V4L2 stateless H.264 decoder driver Zhentao Guo via B4 Relay
2026-10-12 7:20 ` sashiko-bot
2026-10-12 7:06 ` [PATCH v11 5/6] arm64: dts: amlogic: Add video decoder driver support for S4 SOCs Zhentao Guo via B4 Relay
2026-10-12 7:24 ` sashiko-bot
2026-10-12 7:06 ` [PATCH v11 6/6] arm64: defconfig: Enable CONFIG_VIDEO_AMLOGIC_VDEC Zhentao Guo via B4 Relay
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=sashiko-outbox-167782@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=media-ci@linuxtv.org \
--cc=neil.armstrong@linaro.org \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--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
all inboxes | Powered by JetHome®