From: sashiko-bot@kernel.org
To: "Linus Walleij" <linusw@kernel.org>
Cc: mfd@lists.linux.dev, devicetree@vger.kernel.org,
linux-clk@vger.kernel.org, linux-hwmon@vger.kernel.org,
robh@kernel.org, conor+dt@kernel.org, lee@kernel.org
Subject: Re: [PATCH v2 1/7] dt-bindings: mfd: Describe the BCM6846 PMC complex
Date: Sun, 01 Nov 2026 22:24:42 +0000 [thread overview]
Message-ID: <sashiko-outbox-192711@kernel.org> (raw)
In-Reply-To: <20261101-xg6846b-bcmbca-xrdp-reset-v2-1-455fe9eed5ee@kernel.org>
Thank you for your contribution! Sashiko AI review found 3 potential issue(s) to consider:
- [Low] dt-bindings: mfd: brcm,bcm6846-pmc references files added in next patch
- [Low] dt-bindings: mfd: brcm,bcm6846-pmc example child nodes out of name order
- [Low] MAINTAINERS: missing S: status field in BROADCOM BCMBCA PMC3 PMB DRIVER
--
commit 39aa42d4e944629fc1763b294af564d34ce88b86
Author: Linus Walleij <linusw@kernel.org>
dt-bindings: mfd: Describe the BCM6846 PMC complex
This commit adds the Device Tree binding schema for the Broadcom BCM6846
Power Management Controller (PMC3) complex and adds a corresponding
entry in MAINTAINERS.
> diff --git a/Documentation/devicetree/bindings/mfd/brcm,bcm6846-pmc.yaml b/Documentation/devicetree/bindings/mfd/brcm,bcm6846-pmc.yaml
> new file mode 100644
> index 0000000000000..78aef68bc3183
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/mfd/brcm,bcm6846-pmc.yaml
> @@ -0,0 +1,82 @@
[ ... ]
> +patternProperties:
> + '^bus@[0-9a-f]+$':
> + $ref: /schemas/soc/bcm/brcm,bcm6846-pmb.yaml#
> + description: PMB configuration, keyhole and address mapping registers
> +
> +required:
> + - compatible
> + - ranges
> + - '#address-cells'
> + - '#size-cells'
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + #include <dt-bindings/clock/brcm,bcm6846-pmb.h>
> + #include <dt-bindings/reset/brcm,bcm6846-pmb.h>
[Severity: Low]
As reported by Krzysztof Kozlowski on RFC [1], does running
make dt_binding_check fail at this commit because patternProperties
references /schemas/soc/bcm/brcm,bcm6846-pmb.yaml# and the example
includes dt-bindings/clock/brcm,bcm6846-pmb.h and
dt-bindings/reset/brcm,bcm6846-pmb.h before they exist in the tree?
Those headers, the referenced schema, and the child compatibles
(brcm,bcm6846-pmb, brcm,bcm6846-pmb-clock, brcm,bcm6846-pmb-reset, and
brcm,bcm6846-pmb-pvtmon) are only introduced in the subsequent patch,
commit 44e16c21f8b2 ("dt-bindings: soc: Describe the BCM6846 Processor
Monitor Bus"). Should that patch be ordered before this one so that
schema validation and example compilation succeed at every commit in the
series?
> +
> + system-controller@ffb00000 {
> + /* Broadcom BCM6846 Power Management Controller complex */
> + compatible = "brcm,bcm6846-pmc", "simple-mfd";
> + ranges = <0x0 0xffb00000 0x21000>;
> + #address-cells = <1>;
> + #size-cells = <1>;
> +
> + /* Called PMB Processor Monitor Bus in vendor tree */
> + bus@20100 {
> + compatible = "brcm,bcm6846-pmb";
> + reg = <0x20100 0x200>;
> +
> + pmb_clk: clock-controller {
> + compatible = "brcm,bcm6846-pmb-clock";
> + clocks = <&osc50m>;
> + clock-names = "ref";
> + #clock-cells = <1>;
> + };
> +
> + pmb_reset: reset-controller {
> + compatible = "brcm,bcm6846-pmb-reset";
> + #reset-cells = <1>;
> + };
> +
> + hwmon {
> + compatible = "brcm,bcm6846-pmb-pvtmon";
[Severity: Low]
Should the hwmon node be placed before pmb_reset: reset-controller in
the bus@20100 example node?
For child nodes without unit addresses, DTS coding style requires
alpha-numerical ordering by node name, and check_child_name_order() in
scripts/dtc/dt-check-style --mode=strict warns when hwmon appears after
reset-controller.
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 93abbb315065d..eb4b3b631e82c 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -5444,6 +5444,10 @@ N: bcm[9]?6856
> N: bcm[9]?6858
> N: bcm[9]?6878
>
> +BROADCOM BCMBCA PMC3 PMB DRIVER
> +M: Linus Walleij <linusw@kernel.org>
> +F: Documentation/devicetree/bindings/mfd/brcm,bcm6846-pmc.yaml
[Severity: Low]
Is this new MAINTAINERS entry missing an S: status line (such as
S: Maintained)? Without it, scripts/get_maintainer.pl
--self-test=sections reports a section without status warning.
[1] https://lore.kernel.org/r/ddfe83b7-d4b8-4d56-a295-fde63519bdde@kernel.org
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261101-xg6846b-bcmbca-xrdp-reset-v2-0-455fe9eed5ee@kernel.org?part=1
next prev parent reply other threads:[~2026-11-01 22:24 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-01 22:14 [PATCH v2 0/7] BCMBCA PMB clock, reset and hardware monitoring support Linus Walleij
2026-11-01 22:14 ` [PATCH v2 1/7] dt-bindings: mfd: Describe the BCM6846 PMC complex Linus Walleij
2026-11-01 22:24 ` sashiko-bot [this message]
2026-11-01 22:14 ` [PATCH v2 2/7] dt-bindings: soc: Describe the BCM6846 Processor Monitor Bus Linus Walleij
2026-11-01 22:32 ` sashiko-bot
2026-11-01 22:14 ` [PATCH v2 3/7] mfd: Add a shared BCMBCA PMC3 PMB transport Linus Walleij
2026-11-01 22:31 ` sashiko-bot
2026-11-01 22:14 ` [PATCH v2 4/7] reset: Add BCMBCA block resets through the PMB Linus Walleij
2026-11-01 22:20 ` sashiko-bot
2026-11-03 11:28 ` Philipp Zabel
2026-11-01 22:14 ` [PATCH v2 5/7] clk: bcm: Add BCMBCA PMB clocks Linus Walleij
2026-11-01 22:21 ` sashiko-bot
2026-11-01 22:14 ` [PATCH v2 6/7] hwmon: Add Broadcom PMB PVTMON monitoring Linus Walleij
2026-11-01 22:20 ` sashiko-bot
2026-11-02 3:05 ` Guenter Roeck
2026-11-01 22:14 ` [PATCH v2 7/7] ARM: dts: broadcom: Add BCM6846 PMB clocks and hardware monitoring Linus Walleij
2026-11-01 22:24 ` sashiko-bot
2026-11-02 4:32 ` [PATCH v2 0/7] BCMBCA PMB clock, reset and hardware monitoring support William Zhang
2026-11-02 7:50 ` Linus Walleij
2026-11-02 8:35 ` Linus Walleij
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-192711@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=lee@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-hwmon@vger.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.