From: sashiko-bot@kernel.org
To: "Rob Herring (Arm)" <robh@kernel.org>
Cc: mfd@lists.linux.dev, devicetree@vger.kernel.org,
conor+dt@kernel.org, lee@kernel.org
Subject: Re: [PATCH 5/9] arm64: dts: marvell: Fix node names
Date: Thu, 12 Nov 2026 00:21:41 +0000 [thread overview]
Message-ID: <sashiko-outbox-209904@kernel.org> (raw)
In-Reply-To: <20261111-dtbs-marvell-v1-5-938788aff3ae@kernel.org>
Thank you for your contribution! Sashiko AI review found 1 potential
issue to consider:
- [Low] arm64: dts: marvell: ac5: dma-bus@0 unit-address mismatches
ranges parent addr
--
commit d32f1cd6738013623bd9cd4b37c287a2b69edbf8
Author: Rob Herring (Arm) <robh@kernel.org>
arm64: dts: marvell: Fix node names
This commit updates node names across several Marvell device tree files to
use standard naming conventions.
> diff --git a/arch/arm64/boot/dts/marvell/ac5-98dx25xx.dtsi b/arch/arm64/boot/dts/marvell/ac5-98dx25xx.dtsi
> index 4878773883c95..814b8a2e8ea93 100644
> --- a/arch/arm64/boot/dts/marvell/ac5-98dx25xx.dtsi
> +++ b/arch/arm64/boot/dts/marvell/ac5-98dx25xx.dtsi
> @@ -231,7 +231,7 @@ sdhci: mmc@805c0000 {
> * Dedicated section for devices behind 32bit controllers so we
> * can configure specific DMA mapping for them
> */
> - behind-32bit-controller@7f000000 {
> + dma-bus@0 {
> compatible = "simple-bus";
> #address-cells = <0x2>;
> #size-cells = <0x2>;
[Severity: Low]
Should this node be named dma-bus@7f000000 instead of dma-bus@0?
This node has no reg property and defines:
ranges = <0x0 0x0 0x0 0x7f000000 0x0 0x1000000>;
In check_simple_bus_reg(), dtc skips the 2-cell child address (0x0 0x0) and
matches the unit-address against the parent /soc bus address (0x0 0x7f000000),
so building DTBs with W=1 warns:
Warning (simple_bus_reg): /soc/dma-bus@0: simple-bus unit address format error, expected "7f000000"
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261111-dtbs-marvell-v1-0-938788aff3ae@kernel.org?part=5
next prev parent reply other threads:[~2026-11-12 0:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-11 22:42 [PATCH 0/9] arm64: dts: marvell: DT warning fixes Rob Herring (Arm)
2026-11-11 22:42 ` [PATCH 1/9] dt-bindings: mfd: Add Marvell AP806/CP110 system controller schema Rob Herring (Arm)
2026-11-12 0:21 ` sashiko-bot
2026-11-11 22:42 ` [PATCH 2/9] arm64: dts: marvell: Add AP806/CP110 syscon compatibles Rob Herring (Arm)
2026-11-12 0:21 ` sashiko-bot
2026-11-11 22:43 ` [PATCH 3/9] arm64: dts: marvell: Drop unused USB connector PHY supplies Rob Herring (Arm)
2026-11-12 0:19 ` sashiko-bot
2026-11-11 22:43 ` [PATCH 4/9] arm64: dts: marvell: Drop SPI max frequency Rob Herring (Arm)
2026-11-11 22:43 ` [PATCH 5/9] arm64: dts: marvell: Fix node names Rob Herring (Arm)
2026-11-12 0:21 ` sashiko-bot [this message]
2026-11-11 22:43 ` [PATCH 6/9] arm64: dts: marvell: Fix w25q32 compatible strings Rob Herring (Arm)
2026-11-11 22:43 ` [PATCH 7/9] arm64: dts: marvell: Drop unused USB 'phy-names' Rob Herring (Arm)
2026-11-11 22:43 ` [PATCH 8/9] arm64: dts: marvell: cn9131-cf-solidwan: Drop st,m41t80 reset-gpios Rob Herring (Arm)
2026-11-11 22:43 ` [PATCH 9/9] arm64: dts: marvell: armada-3720-gl-mv1000: Add switch fixed-link Rob Herring (Arm)
2026-11-12 0:17 ` 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=sashiko-outbox-209904@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=lee@kernel.org \
--cc=mfd@lists.linux.dev \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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.