From: sashiko-bot@kernel.org
To: "Zhentao Guo" <zhentao.guo@amlogic.com>
Cc: devicetree@vger.kernel.org, conor+dt@kernel.org,
media-ci@linuxtv.org, neil.armstrong@linaro.org,
linux-amlogic@lists.infradead.org, robh@kernel.org
Subject: Re: [PATCH v9 3/6] media: dt-bindings: Add Amlogic V4L2 video decoder
Date: Mon, 14 Sep 2026 08:18:30 +0000 [thread overview]
Message-ID: <20260914081831.12BD21F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260914-b4-s4-vdec-upstream-v9-3-72fdb0d71b02@amlogic.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] Incomplete schema validation constraints for `interrupts` and `interrupt-names`
--
commit 783cc9cba9c938896ba8c6cfc5dc0ca5686d85fb
Author: Zhentao Guo <zhentao.guo@amlogic.com>
media: dt-bindings: Add Amlogic V4L2 video decoder
Describe the initial support for the V4L2 stateless video decoder driver
used with the Amlogic S4 (S805X2) platform.
> 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..d350b3e68a389
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/media/amlogic,s4-vdec.yaml
> [ ... ]
> + reg-names:
> + items:
> + - const: dos
> + - const: dmc
> +
> + interrupts:
> + maxItems: 2
[Severity: Medium]
Does the interrupts property also need minItems: 2? Since maxItems: 2
implicitly allows minItems: 1, the schema allows a single interrupt.
However, the driver explicitly requests index 1. A device tree with a single
interrupt will pass schema validation but cause driver initialization to fail
at runtime.
> +
> + interrupt-names:
> + items:
> + - const: core_hvdec
> + - const: core_vdec
> [ ... ]
> +required:
> + - compatible
> + - reg
> + - reg-names
> + - interrupts
> + - clocks
> + - clock-names
> + - power-domains
> + - power-domain-names
> + - resets
> + - amlogic,canvas
> + - amlogic,secure-monitor
[Severity: Medium]
Is interrupt-names intentionally omitted from the required list?
Other properties like reg-names and clock-names are required. Omitting
interrupt-names makes it optional, which fails to enforce explicit hardware
description for multiple interrupts.
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + #include <dt-bindings/interrupt-controller/arm-gic.h>
> + #include <dt-bindings/clock/amlogic,s4-pll-clkc.h>
> + #include <dt-bindings/clock/amlogic,s4-peripherals-clkc.h>
> + #include <dt-bindings/power/meson-s4-power.h>
> + #include <dt-bindings/reset/amlogic,meson-s4-reset.h>
> + video-codec@fe320000 {
> + compatible = "amlogic,s4-vdec";
> + reg = <0xfe320000 0x10000>,
> + <0xfe036000 0x20>;
> + reg-names = "dos",
> + "dmc";
> + interrupts = <GIC_SPI 91 IRQ_TYPE_EDGE_RISING>,
> + <GIC_SPI 92 IRQ_TYPE_EDGE_RISING>;
> + clocks = <&clkc_periphs CLKID_DOS>,
> + <&clkc_periphs CLKID_VDEC_SEL>,
> + <&clkc_periphs CLKID_HEVCF_SEL>;
[Severity: Medium]
Should interrupt-names be included in this example? Omitting it provides
an incomplete template for device tree authors.
> + clock-names = "dos",
> + "core_v",
> + "core_h";
> + power-domains = <&pwrc PWRC_S4_DOS_VDEC_ID>,
> + <&pwrc PWRC_S4_DOS_HEVC_ID>;
> + power-domain-names = "dos_v",
> + "dos_h";
> + resets = <&reset RESET_DOS>;
> + amlogic,canvas = <&canvas>;
> + amlogic,secure-monitor = <&sm>;
> + };
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260914-b4-s4-vdec-upstream-v9-0-72fdb0d71b02@amlogic.com?part=3
WARNING: multiple messages have this Message-ID (diff)
From: sashiko-bot@kernel.org
To: "Zhentao Guo" <zhentao.guo@amlogic.com>
Cc: devicetree@vger.kernel.org, conor+dt@kernel.org,
media-ci@linuxtv.org, neil.armstrong@linaro.org,
linux-amlogic@lists.infradead.org, robh@kernel.org
Subject: Re: [PATCH v9 3/6] media: dt-bindings: Add Amlogic V4L2 video decoder
Date: Mon, 14 Sep 2026 08:18:30 +0000 [thread overview]
Message-ID: <20260914081831.12BD21F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260914-b4-s4-vdec-upstream-v9-3-72fdb0d71b02@amlogic.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] Incomplete schema validation constraints for `interrupts` and `interrupt-names`
--
commit 783cc9cba9c938896ba8c6cfc5dc0ca5686d85fb
Author: Zhentao Guo <zhentao.guo@amlogic.com>
media: dt-bindings: Add Amlogic V4L2 video decoder
Describe the initial support for the V4L2 stateless video decoder driver
used with the Amlogic S4 (S805X2) platform.
> 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..d350b3e68a389
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/media/amlogic,s4-vdec.yaml
> [ ... ]
> + reg-names:
> + items:
> + - const: dos
> + - const: dmc
> +
> + interrupts:
> + maxItems: 2
[Severity: Medium]
Does the interrupts property also need minItems: 2? Since maxItems: 2
implicitly allows minItems: 1, the schema allows a single interrupt.
However, the driver explicitly requests index 1. A device tree with a single
interrupt will pass schema validation but cause driver initialization to fail
at runtime.
> +
> + interrupt-names:
> + items:
> + - const: core_hvdec
> + - const: core_vdec
> [ ... ]
> +required:
> + - compatible
> + - reg
> + - reg-names
> + - interrupts
> + - clocks
> + - clock-names
> + - power-domains
> + - power-domain-names
> + - resets
> + - amlogic,canvas
> + - amlogic,secure-monitor
[Severity: Medium]
Is interrupt-names intentionally omitted from the required list?
Other properties like reg-names and clock-names are required. Omitting
interrupt-names makes it optional, which fails to enforce explicit hardware
description for multiple interrupts.
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + #include <dt-bindings/interrupt-controller/arm-gic.h>
> + #include <dt-bindings/clock/amlogic,s4-pll-clkc.h>
> + #include <dt-bindings/clock/amlogic,s4-peripherals-clkc.h>
> + #include <dt-bindings/power/meson-s4-power.h>
> + #include <dt-bindings/reset/amlogic,meson-s4-reset.h>
> + video-codec@fe320000 {
> + compatible = "amlogic,s4-vdec";
> + reg = <0xfe320000 0x10000>,
> + <0xfe036000 0x20>;
> + reg-names = "dos",
> + "dmc";
> + interrupts = <GIC_SPI 91 IRQ_TYPE_EDGE_RISING>,
> + <GIC_SPI 92 IRQ_TYPE_EDGE_RISING>;
> + clocks = <&clkc_periphs CLKID_DOS>,
> + <&clkc_periphs CLKID_VDEC_SEL>,
> + <&clkc_periphs CLKID_HEVCF_SEL>;
[Severity: Medium]
Should interrupt-names be included in this example? Omitting it provides
an incomplete template for device tree authors.
> + clock-names = "dos",
> + "core_v",
> + "core_h";
> + power-domains = <&pwrc PWRC_S4_DOS_VDEC_ID>,
> + <&pwrc PWRC_S4_DOS_HEVC_ID>;
> + power-domain-names = "dos_v",
> + "dos_h";
> + resets = <&reset RESET_DOS>;
> + amlogic,canvas = <&canvas>;
> + amlogic,secure-monitor = <&sm>;
> + };
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260914-b4-s4-vdec-upstream-v9-0-72fdb0d71b02@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-09-14 8:18 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-14 8:10 [PATCH v9 0/6] Add Amlogic stateless H.264 video decoder for S4 Zhentao Guo
2026-09-14 8:10 ` Zhentao Guo via B4 Relay
2026-09-14 8:10 ` Zhentao Guo via B4 Relay
2026-09-14 8:10 ` [PATCH v9 1/6] firmware: meson: sm: video firmware loading via secure monitor Zhentao Guo
2026-09-14 8:10 ` Zhentao Guo via B4 Relay
2026-09-14 8:10 ` Zhentao Guo via B4 Relay
2026-09-14 8:10 ` [PATCH v9 2/6] firmware: meson: sm: Add video firmware loading SMC call Zhentao Guo
2026-09-14 8:10 ` Zhentao Guo via B4 Relay
2026-09-14 8:10 ` Zhentao Guo via B4 Relay
2026-09-14 8:22 ` sashiko-bot
2026-09-14 8:22 ` sashiko-bot
2026-09-14 8:10 ` [PATCH v9 3/6] media: dt-bindings: Add Amlogic V4L2 video decoder Zhentao Guo
2026-09-14 8:10 ` Zhentao Guo via B4 Relay
2026-09-14 8:10 ` Zhentao Guo via B4 Relay
2026-09-14 8:18 ` sashiko-bot [this message]
2026-09-14 8:18 ` sashiko-bot
2026-09-16 9:01 ` Krzysztof Kozlowski
2026-09-16 9:01 ` Krzysztof Kozlowski
2026-09-17 3:07 ` Zhentao Guo
2026-09-17 3:07 ` Zhentao Guo
2026-09-17 6:02 ` Krzysztof Kozlowski
2026-09-17 6:02 ` Krzysztof Kozlowski
2026-09-17 6:07 ` Zhentao Guo
2026-09-17 6:07 ` Zhentao Guo
2026-09-14 8:10 ` [PATCH v9 4/6] decoder: Add V4L2 stateless H.264 decoder driver Zhentao Guo
2026-09-14 8:10 ` Zhentao Guo via B4 Relay
2026-09-14 8:10 ` Zhentao Guo via B4 Relay
2026-09-14 8:31 ` sashiko-bot
2026-09-14 8:31 ` sashiko-bot
2026-09-14 8:10 ` [PATCH v9 5/6] arm64: dts: amlogic: Add video decoder driver support for S4 SOCs Zhentao Guo
2026-09-14 8:10 ` Zhentao Guo via B4 Relay
2026-09-14 8:10 ` Zhentao Guo via B4 Relay
2026-09-14 8:10 ` [PATCH v9 6/6] arm64: defconfig: Enable CONFIG_VIDEO_AMLOGIC_VDEC Zhentao Guo
2026-09-14 8:10 ` Zhentao Guo via B4 Relay
2026-09-14 8:10 ` 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=20260914081831.12BD21F000FF@smtp.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.