From: sashiko-bot@kernel.org
To: "Chen-Yu Tsai" <wens@kernel.org>
Cc: devicetree@vger.kernel.org, conor+dt@kernel.org,
linux-sunxi@lists.linux.dev, robh@kernel.org
Subject: Re: [PATCH v3 1/7] dt-bindings: media: sun4i-a10-video-engine: Fix IOMMU count for H6
Date: Sun, 12 Jul 2026 03:08:14 +0000 [thread overview]
Message-ID: <20260712030814.8CE131F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260712030011.3778169-2-wens@kernel.org>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] Validation failure: sun50i-h6.dtsi fails dtbs_check due to the new minItems: 2 constraint.
--
--- Patch [1]: [PATCH v3 1/7] dt-bindings: media: sun4i-a10-video-engine: Fix IOMMU count for H6 ---
commit 17817354e28859038f6eb81e492f4c4b1bc51a02
Author: Chen-Yu Tsai <wens@kernel.org>
dt-bindings: media: sun4i-a10-video-engine: Fix IOMMU count for H6
This commit updates the device tree binding for the sun4i-a10-video-engine to
specify that the H6 SoC requires two IOMMU connections. It adds a conditional
schema block enforcing a minimum of two items for the iommus property on H6
devices.
> diff --git a/Documentation/devicetree/bindings/media/allwinner,sun4i-a10-video-engine.yaml b/Documentation/devicetree/bindings/media/allwinner,sun4i-a10-video-engine.yaml
> index 541325f900a1d..b4c0fabb38211 100644
> --- a/Documentation/devicetree/bindings/media/allwinner,sun4i-a10-video-engine.yaml
> +++ b/Documentation/devicetree/bindings/media/allwinner,sun4i-a10-video-engine.yaml
[ ... ]
> @@ -72,6 +75,22 @@ required:
> - resets
> - allwinner,sram
>
> +allOf:
> + - if:
> + properties:
> + compatible:
> + contains:
> + enum:
> + - allwinner,sun50i-h6-video-engine
> + then:
> + properties:
> + iommus:
> + minItems: 2
[Severity: Low]
Will this strict constraint cause dtbs_check failures for existing device
trees?
Looking at the H6 dtsi file, the video-codec node only provides a single IOMMU
connection:
arch/arm64/boot/dts/allwinner/sun50i-h6.dtsi:video-codec@1c0e000 {
...
iommus = <&iommu 3>;
};
Since this commit enforces minItems: 2 without simultaneously updating the
device tree, will it cause make dtbs_check to report validation errors for the
H6 SoC?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260712030011.3778169-1-wens@kernel.org?part=1
next prev parent reply other threads:[~2026-07-12 3:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-12 3:00 [PATCH v3 0/7] arm64: allwinner: h616: Support Video Engine Chen-Yu Tsai
2026-07-12 3:00 ` [PATCH v3 1/7] dt-bindings: media: sun4i-a10-video-engine: Fix IOMMU count for H6 Chen-Yu Tsai
2026-07-12 3:08 ` sashiko-bot [this message]
2026-07-12 3:00 ` [PATCH v3 2/7] dt-bindings: media: sun4i-a10-video-engine: Fix SRAM " Chen-Yu Tsai
2026-07-12 3:08 ` sashiko-bot
2026-07-12 3:00 ` [PATCH v3 3/7] dt-bindings: media: sun4i-a10-video-engine: Add H616 compatible Chen-Yu Tsai
2026-07-12 3:00 ` [PATCH v3 4/7] staging: media: sunxi: cedrus: add H616 variant Chen-Yu Tsai
2026-07-12 3:00 ` [PATCH v3 5/7] arm64: dts: allwinner: sun50i-h6: Add missing SRAM region for video engine Chen-Yu Tsai
2026-07-12 3:08 ` sashiko-bot
2026-07-12 3:00 ` [PATCH v3 6/7] arm64: dts: allwinner: sun50i-h6: Add missing IOMMU " Chen-Yu Tsai
2026-07-12 3:09 ` sashiko-bot
2026-07-12 3:00 ` [PATCH v3 7/7] arm64: dts: allwinner: sun50i-h616: Add " Chen-Yu Tsai
2026-07-12 3:08 ` sashiko-bot
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=20260712030814.8CE131F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=wens@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