From: sashiko-bot@kernel.org
To: "Chen-Yu Tsai" <wens@kernel.org>
Cc: devicetree@vger.kernel.org, robh@kernel.org,
linux-sunxi@lists.linux.dev, conor+dt@kernel.org
Subject: Re: [PATCH v3 7/7] arm64: dts: allwinner: sun50i-h616: Add video engine
Date: Sun, 12 Jul 2026 03:08:40 +0000 [thread overview]
Message-ID: <20260712030841.0441D1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260712030011.3778169-8-wens@kernel.org>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] The newly added `video-codec` node references an undefined `ve_sram` phandle, causing a device tree compilation error, and a structurally incorrect `sram_c` phandle.
--
--- Patch [7]: [PATCH v3 7/7] arm64: dts: allwinner: sun50i-h616: Add video engine ---
commit 47b5fe1ab74e2eb5363068c14fed457f3e1ad7e1
Author: Jernej Skrabec <jernej.skrabec@gmail.com>
arm64: dts: allwinner: sun50i-h616: Add video engine
This commit adds the video engine node to the sun50i-h616 dtsi file. It
defines the clocks, resets, interrupts, iommus, and SRAM regions required
by the video engine hardware.
> diff --git a/arch/arm64/boot/dts/allwinner/sun50i-h616.dtsi b/arch/arm64/boot/dts/allwinner/sun50i-h616.dtsi
> index bf054869e78be..fc912ed80a3e4 100644
> --- a/arch/arm64/boot/dts/allwinner/sun50i-h616.dtsi
> +++ b/arch/arm64/boot/dts/allwinner/sun50i-h616.dtsi
> @@ -175,6 +175,18 @@ crypto: crypto@1904000 {
> resets = <&ccu RST_BUS_CE>;
> };
>
> + video-codec@1c0e000 {
> + compatible = "allwinner,sun50i-h616-video-engine";
> + reg = <0x01c0e000 0x2000>;
> + clocks = <&ccu CLK_BUS_VE>, <&ccu CLK_VE>,
> + <&ccu CLK_MBUS_VE>;
> + clock-names = "ahb", "mod", "ram";
> + resets = <&ccu RST_BUS_VE>;
> + interrupts = <GIC_SPI 93 IRQ_TYPE_LEVEL_HIGH>;
> + iommus = <&iommu 3>, <&iommu 2>;
> + allwinner,sram = <&ve_sram 1>, <&sram_c 1>;
[Severity: Low]
Will this cause a device tree compilation error? The &ve_sram phandle doesn't
appear to be defined, which could prevent the device tree from building.
Also, does the &sram_c phandle reference the parent mmio-sram node instead
of a valid sram-section child node? If it points to the parent,
sunxi_sram_of_parse() might return -EINVAL during driver probe.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260712030011.3778169-1-wens@kernel.org?part=7
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
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 [this message]
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=20260712030841.0441D1F000E9@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