From: Rob Herring <robh@kernel.org>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: "Florian Fainelli" <f.fainelli@gmail.com>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
bcm-kernel-feedback-list@broadcom.com,
"Rafał Miłecki" <rafal@milecki.pl>
Subject: Re: [PATCH robh next] dt-bindings: bus: add Broadcom CRU
Date: Wed, 7 Apr 2021 15:58:04 -0500 [thread overview]
Message-ID: <20210407205804.GA10597@robh.at.kernel.org> (raw)
In-Reply-To: <20210309142241.16259-1-zajec5@gmail.com>
On Tue, Mar 09, 2021 at 03:22:41PM +0100, Rafał Miłecki wrote:
> From: Rafał Miłecki <rafal@milecki.pl>
>
> CRU is a block used in Northstar devices. It can be seen in the
> bcm5301x.dtsi and this binding documents its proper usage.
>
> Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
> ---
> .../devicetree/bindings/bus/brcm,cru.yaml | 41 +++++++++++++++++++
> 1 file changed, 41 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/bus/brcm,cru.yaml
>
> diff --git a/Documentation/devicetree/bindings/bus/brcm,cru.yaml b/Documentation/devicetree/bindings/bus/brcm,cru.yaml
> new file mode 100644
> index 000000000000..c3b1ca53a443
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/bus/brcm,cru.yaml
> @@ -0,0 +1,41 @@
> +# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/bus/brcm,cru.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Broadcom CRU
> +
> +maintainers:
> + - Rafał Miłecki <rafal@milecki.pl>
> +
> +description: |
> + Broadcom CRU ("Clock and Reset Unit" or "Central Resource Unit") is a hardware
> + block grouping smaller blocks. It contains e.g. clocks, pinctrl, USB PHY and
Are these really separate blocks? I really need to see a complete
binding for the block.
> + thermal.
> +
> +allOf:
> + - $ref: /schemas/simple-bus.yaml#
I don't think this should be a 'simple-bus'. Maybe 'simple-mfd' instead.
> +
> +properties:
> + compatible:
> + contains:
> + const: brcm,cru
This should be SoC specific.
> +
> + reg:
> + description: CRU registers
> +
> +unevaluatedProperties: false
> +
> +required:
> + - reg
> +
> +examples:
> + - |
> + cru-bus@1800c100 {
> + compatible = "brcm,cru", "simple-bus";
> + reg = <0x1800c100 0x1d0>;
> + ranges;
> + #address-cells = <1>;
> + #size-cells = <1>;
> + };
> --
> 2.26.2
>
next prev parent reply other threads:[~2021-04-07 20:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-09 14:22 [PATCH robh next] dt-bindings: bus: add Broadcom CRU Rafał Miłecki
2021-04-05 22:44 ` Rafał Miłecki
2021-04-07 20:58 ` Rob Herring [this message]
2021-04-07 21:43 ` Florian Fainelli
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=20210407205804.GA10597@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=rafal@milecki.pl \
--cc=zajec5@gmail.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;
as well as URLs for NNTP newsgroup(s).