devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: "Michael Turquette" <mturquette@baylibre.com>,
	"Stephen Boyd" <sboyd@kernel.org>, "Ray Jui" <rjui@broadcom.com>,
	"Scott Branden" <sbranden@broadcom.com>,
	"Maxime Ripard" <maxime@cerno.tech>,
	"Florian Fainelli" <f.fainelli@gmail.com>,
	"Álvaro Fernández Rojas" <noltari@gmail.com>,
	"Nathan Chancellor" <nathan@kernel.org>,
	linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
	bcm-kernel-feedback-list@broadcom.com,
	"Rafał Miłecki" <rafal@milecki.pl>
Subject: Re: [PATCH V2] dt-bindings: clock: brcm,iproc-clocks: convert to the json-schema
Date: Fri, 23 Apr 2021 13:14:03 -0500	[thread overview]
Message-ID: <20210423181403.GA1344607@robh.at.kernel.org> (raw)
In-Reply-To: <20210421165633.13299-1-zajec5@gmail.com>

On Wed, Apr 21, 2021 at 06:56:33PM +0200, Rafał Miłecki wrote:
> From: Rafał Miłecki <rafal@milecki.pl>
> 
> This helps validating DTS files.
> 
> Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
> ---
> V2: Fix typo s/clocks/clock-output-names/
> ---
>  .../bindings/clock/brcm,iproc-clocks.txt      | 313 --------------
>  .../bindings/clock/brcm,iproc-clocks.yaml     | 398 ++++++++++++++++++
>  2 files changed, 398 insertions(+), 313 deletions(-)
>  delete mode 100644 Documentation/devicetree/bindings/clock/brcm,iproc-clocks.txt
>  create mode 100644 Documentation/devicetree/bindings/clock/brcm,iproc-clocks.yaml


> diff --git a/Documentation/devicetree/bindings/clock/brcm,iproc-clocks.yaml b/Documentation/devicetree/bindings/clock/brcm,iproc-clocks.yaml
> new file mode 100644
> index 000000000000..a1b9613f7c68
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/clock/brcm,iproc-clocks.yaml
> @@ -0,0 +1,398 @@
> +# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/clock/brcm,iproc-clocks.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Broadcom iProc Family Clocks
> +
> +maintainers:
> +  - Ray Jui <rjui@broadcom.com>
> +  - Scott Branden <sbranden@broadcom.com>
> +
> +description: |
> +  This binding uses the common clock binding:
> +      Documentation/devicetree/bindings/clock/clock-bindings.txt

I think we can drop this statement.

> +
> +  The iProc clock controller manages clocks that are common to the iProc family.
> +  An SoC from the iProc family may have several PPLs, e.g., ARMPLL, GENPLL,

s/PPLs/PLLs/

Otherwise,

Reviewed-by: Rob Herring <robh@kernel.org>

  reply	other threads:[~2021-04-23 18:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-21 16:39 [PATCH] dt-bindings: clock: brcm,iproc-clocks: convert to the json-schema Rafał Miłecki
2021-04-21 16:56 ` [PATCH V2] " Rafał Miłecki
2021-04-23 18:14   ` Rob Herring [this message]
2021-04-24 20:23   ` [PATCH V3] " Rafał Miłecki
2021-05-07  4:12     ` 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=20210423181403.GA1344607@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-clk@vger.kernel.org \
    --cc=maxime@cerno.tech \
    --cc=mturquette@baylibre.com \
    --cc=nathan@kernel.org \
    --cc=noltari@gmail.com \
    --cc=rafal@milecki.pl \
    --cc=rjui@broadcom.com \
    --cc=sboyd@kernel.org \
    --cc=sbranden@broadcom.com \
    --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).