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 2/9] arm64: dts: marvell: Add AP806/CP110 syscon compatibles
Date: Thu, 12 Nov 2026 00:21:47 +0000 [thread overview]
Message-ID: <sashiko-outbox-209905@kernel.org> (raw)
In-Reply-To: <20261111-dtbs-marvell-v1-2-938788aff3ae@kernel.org>
Thank you for your contribution! Sashiko AI review found 1 potential
issue to consider:
- [Medium] arm64: dts: marvell: ap806-system-controller triggers legacy
clk probe failure
--
commit d5587b2920b1facc3deb1cff76751746477ff106
Author: Rob Herring (Arm) <robh@kernel.org>
arm64: dts: marvell: Add AP806/CP110 syscon compatibles
This commit adds "marvell,ap806-system-controller" and
"marvell,cp110-system-controller" compatibles to the AP806 and CP110
system-controller syscon nodes.
> diff --git a/arch/arm64/boot/dts/marvell/armada-ap80x.dtsi b/arch/arm64/boot/dts/marvell/armada-ap80x.dtsi
> index 40e1469829212..0da13b2cd1fc0 100644
> --- a/arch/arm64/boot/dts/marvell/armada-ap80x.dtsi
> +++ b/arch/arm64/boot/dts/marvell/armada-ap80x.dtsi
> @@ -267,7 +267,8 @@ ap_sdhci0: mmc@6e0000 {
> };
>
> ap_syscon0: system-controller@6f4000 {
> - compatible = "syscon", "simple-mfd";
> + compatible = "marvell,ap806-system-controller",
> + "syscon", "simple-mfd";
> reg = <0x6f4000 0x2000>;
>
> ap_pinctrl: pinctrl {
> @@ -293,7 +294,8 @@ ap_gpio: gpio@1040 {
> };
>
> ap_syscon1: system-controller@6f8000 {
> - compatible = "syscon", "simple-mfd";
> + compatible = "marvell,ap806-system-controller",
> + "syscon", "simple-mfd";
> reg = <0x6f8000 0x1000>;
> #address-cells = <1>;
> #size-cells = <1>;
[Severity: Medium]
Does adding "marvell,ap806-system-controller" to ap_syscon0 and ap_syscon1
cause both nodes to bind to ap806_syscon_legacy_driver and fail probe?
drivers/clk/mvebu/ap806-system-controller.c matches
"marvell,ap806-system-controller" for the deprecated flat-node clock
binding:
drivers/clk/mvebu/ap806-system-controller.c:ap806_syscon_legacy_probe() {
dev_warn(&pdev->dev, FW_WARN "Using legacy device tree binding\n");
dev_warn(&pdev->dev, FW_WARN "Update your device tree:\n");
dev_warn(&pdev->dev, FW_WARN
"This binding won't be supported in future kernel\n");
return ap806_syscon_common_probe(pdev, pdev->dev.of_node);
}
ap806_syscon_common_probe() then reads AP806_SAR_REG (offset 0x400) from
each syscon regmap (including System Controller 1 on ap_syscon1) and
checks pdev->dev.of_node against "marvell,ap806-clock" and
"marvell,ap807-clock". Because pdev->dev.of_node is the parent
system-controller node rather than the clock child node, both devices emit
false FW_WARN messages, log "compatible not supported", and fail probe
with -EINVAL on every boot.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261111-dtbs-marvell-v1-0-938788aff3ae@kernel.org?part=2
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 [this message]
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
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-209905@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox