Devicetree
 help / color / mirror / Atom feed
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 1/9] dt-bindings: mfd: Add Marvell AP806/CP110 system controller schema
Date: Thu, 12 Nov 2026 00:21:58 +0000	[thread overview]
Message-ID: <sashiko-outbox-209906@kernel.org> (raw)
In-Reply-To: <20261111-dtbs-marvell-v1-1-938788aff3ae@kernel.org>

Thank you for your contribution! Sashiko AI review found 1 potential
issue to consider:
- [Medium] dt-bindings: mfd: marvell,ap806-system-controller collides
  with legacy driver
--

commit 4cddea2359377a9e6ae88c719cab7c7efc9634bf
Author: Rob Herring (Arm) <robh@kernel.org>

dt-bindings: mfd: Add Marvell AP806/CP110 system controller schema

This commit adds a dedicated Device Tree binding schema for the Marvell
AP806 and CP110 system controllers and their child devices.

> diff --git a/Documentation/devicetree/bindings/mfd/marvell,ap806-cp110-system-controller.yaml b/Documentation/devicetree/bindings/mfd/marvell,ap806-cp110-system-controller.yaml
> new file mode 100644
> index 0000000000000..4c43986c2c0a3
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/mfd/marvell,ap806-cp110-system-controller.yaml
> @@ -0,0 +1,59 @@
> +# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/mfd/marvell,ap806-cp110-system-controller.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Marvell AP806 and CP110 system controller
> +
> +maintainers:
> +  - Andrew Lunn <andrew@lunn.ch>
> +  - Gregory Clement <gregory.clement@bootlin.com>
> +  - Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
> +
> +properties:
> +  compatible:
> +    items:
> +      - enum:
> +          - marvell,ap806-system-controller
> +          - marvell,cp110-system-controller
> +      - const: syscon
> +      - const: simple-mfd

[Severity: Medium]
Does requiring marvell,ap806-system-controller on the parent simple-mfd
node cause a collision with the built-in legacy clock driver?

Unlike CP110, where cp110_syscon_legacy_of_match matches
marvell,cp110-system-controller0, ap806_syscon_legacy_of_match matches
marvell,ap806-system-controller:

drivers/clk/mvebu/ap806-system-controller.c:
static const struct of_device_id ap806_syscon_legacy_of_match[] = {
	{ .compatible = "marvell,ap806-system-controller", },
	{ }
};

When a device tree conforms to this schema, ap806_syscon_legacy_driver
binds to the parent MFD platform_device at boot.
ap806_syscon_legacy_probe() then logs three false FW_WARN messages about a
legacy binding, performs an unintended regmap_read() of AP806_SAR_REG
(0x400) in ap806_syscon_common_probe(), and fails probe with -EINVAL and
"compatible not supported" because the parent node is not compatible with
marvell,ap806-clock or marvell,ap807-clock.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261111-dtbs-marvell-v1-0-938788aff3ae@kernel.org?part=1

  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 [this message]
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
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-209906@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