From: Krzysztof Kozlowski <krzk@kernel.org>
To: "Linus Walleij" <linusw@kernel.org>, "Lee Jones" <lee@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"William Zhang" <william.zhang@broadcom.com>,
"Anand Gore" <anand.gore@broadcom.com>,
"Kursad Oney" <kursad.oney@broadcom.com>,
"Florian Fainelli" <florian.fainelli@broadcom.com>,
"Rafał Miłecki" <rafal@milecki.pl>,
"Broadcom internal kernel review list"
<bcm-kernel-feedback-list@broadcom.com>,
"Philipp Zabel" <p.zabel@pengutronix.de>
Cc: mfd@lists.linux.dev, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH RFC 1/5] dt-bindings: mfd: Describe the BCM6846 PMC complex
Date: Fri, 16 Oct 2026 16:19:50 +0200 [thread overview]
Message-ID: <ddfe83b7-d4b8-4d56-a295-fde63519bdde@kernel.org> (raw)
In-Reply-To: <20261014-xg6846b-bcmbca-xrdp-reset-v1-1-daf5d177e113@kernel.org>
On 14/10/2026 11:48, Linus Walleij wrote:
> The third generation Platform Management Controller (PMC3) has
> different subdevices.
>
> Identify the parent with Broadcom's "brcm,bca-pmc-3-1" compatible
> for the version 3.1 complex.
>
> Describe the complex as a simple-mfd with two system-controller children
> and a bus child, each owning its register resource.
That's RFC, but I skimmed cover letter and did not find what you
actually ask us for and why this is not ready for review, thus few
things to spare you one more cycle when this is ready for review:
>
> Assisted-by: LLM
> Signed-off-by: Linus Walleij <linusw@kernel.org>
> ---
> .../devicetree/bindings/mfd/brcm,bcm6846-pmc.yaml | 98 ++++++++++++++++++++++
> 1 file changed, 98 insertions(+)
>
> 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 000000000000..7ddf84b561aa
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/mfd/brcm,bcm6846-pmc.yaml
> @@ -0,0 +1,98 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/mfd/brcm,bcm6846-pmc.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Broadcom BCM6846 Platform Management Controller
> +
> +maintainers:
> + - Linus Walleij <linusw@kernel.org>
> +
> +description: |
Drop |
> + The third generation Platform Management Controller (PMC3) contains
> + separate register banks for PMC control and message queues, the
> + Processor Monitor Bus (PMB) interface within Procmon, and the Maestro
> + processor control registers. Each child owns its register bank. The
> + parent provides address translation and does not own a register bank.
> +
> +properties:
> + compatible:
> + items:
> + - const: brcm,bca-pmc-3-1
This should be rather SoC specific.
> + - const: simple-mfd
> +
> + "#address-cells":
> + const: 1
> +
> + "#size-cells":
> + const: 1
> +
> + ranges:
> + maxItems: 1
> +
> +patternProperties:
> + '^system-controller@[0-9a-f]+$':
> + type: object
> + additionalProperties: false
> + description:
> + PMC control and message queue registers, or Maestro processor
> + control, status and interrupt registers
> +
> + properties:
> + compatible:
> + enum:
> + - brcm,bcm6846-pmc-control
> + - brcm,bcm6846-pmc-maestro
> +
> + reg:
> + maxItems: 1
> +
> + required:
> + - compatible
> + - reg
No resources here except address space, so I question whether these are
really separate devices. I guess address space is at least big enough to
mark this as really separate device?
> +
> + '^bus@[0-9a-f]+$':
> + $ref: /schemas/soc/bcm/brcm,bcm6846-pmb.yaml#
No such file. Are you sure this passes tests?
> + description: PMB configuration, keyhole and address mapping registers
> +
> +required:
> + - compatible
> + - '#address-cells'
> + - '#size-cells'
> + - ranges
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + system-controller@ffb00000 {
> + /* Broadcom BCA Platform Management Complex version 3.1 */
> + compatible = "brcm,bca-pmc-3-1", "simple-mfd";
> + #address-cells = <1>;
> + #size-cells = <1>;
> + ranges = <0x0 0xffb00000 0x21000>;
ranges should be the second.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-10-16 14:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-14 9:48 [PATCH RFC 0/5] BCMBCA PMB reset controller Linus Walleij
2026-10-14 9:48 ` [PATCH RFC 1/5] dt-bindings: mfd: Describe the BCM6846 PMC complex Linus Walleij
2026-10-16 14:19 ` Krzysztof Kozlowski [this message]
2026-10-14 9:48 ` [PATCH RFC 2/5] dt-bindings: soc: Describe the BCM6846 Processor Monitor Bus Linus Walleij
2026-10-16 14:20 ` Krzysztof Kozlowski
2026-10-14 9:48 ` [PATCH RFC 3/5] dt-bindings: reset: Describe the BCMBCA PMB reset controller Linus Walleij
2026-10-14 10:23 ` Philipp Zabel
2026-10-14 9:48 ` [PATCH RFC 4/5] bus: Add a shared BCMBCA PMC3 PMB transport Linus Walleij
2026-10-14 9:48 ` [PATCH RFC 5/5] reset: Add BCMBCA block resets through the PMB Linus Walleij
2026-10-14 11:13 ` Philipp Zabel
2026-10-15 6:42 ` [PATCH RFC 0/5] BCMBCA PMB reset controller William Zhang
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=ddfe83b7-d4b8-4d56-a295-fde63519bdde@kernel.org \
--to=krzk@kernel.org \
--cc=anand.gore@broadcom.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=florian.fainelli@broadcom.com \
--cc=krzk+dt@kernel.org \
--cc=kursad.oney@broadcom.com \
--cc=lee@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mfd@lists.linux.dev \
--cc=p.zabel@pengutronix.de \
--cc=rafal@milecki.pl \
--cc=robh@kernel.org \
--cc=william.zhang@broadcom.com \
/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