devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Michael Turquette <mturquette@baylibre.com>,
	linux-renesas-soc@vger.kernel.org,
	Stephen Boyd <sboyd@kernel.org>,
	devicetree@vger.kernel.org, linux-clk@vger.kernel.org,
	Rob Herring <robh+dt@kernel.org>
Subject: Re: [PATCH v2] dt-bindings: clock: renesas: cpg: Convert to json-schema
Date: Thu, 28 May 2020 14:34:19 -0600	[thread overview]
Message-ID: <20200528203419.GA631266@bogus> (raw)
In-Reply-To: <20200518081644.23683-1-geert+renesas@glider.be>

On Mon, 18 May 2020 10:16:44 +0200, Geert Uytterhoeven wrote:
> Convert the Renesas Clock Pulse Generator (CPG) Device Tree
> binding documentation to json-schema, combining support for:
>   - R-Mobile APE6 (R8A73A4) and A1 (R8A7740),
>   - R-Car M1 (R8A7778) and H1 (R8A7779),
>   - RZ/A1 (R7S72100),
>   - SH-Mobile AG5 (SH73A0).
> 
> Keep the example for R-Mobile A1, which shows most properties.
> Drop the consumer examples, as they do not belong here.
> 
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> ---
> v2:
>   - Remove unneeded 'allOf' container around '$ref',
> 
> To be queued in clk-renesas-for-v5.8.
> 
> For a clean dtbs_check, this depends on commit e47cb97f153193d4 ("ARM:
> dts: r8a7740: Add missing extal2 to CPG node") in v5.7-rc6.
> 
> As these bindings are very similar, I merged them into a single
> document.  SoC-specific differences are mostly limited to the "clocks"
> and "clock-output-names" properties, and "#power-domain-cells" for clock
> domain providers.
> 
> JFYI, the diffstat for the individual conversions would look like:
>      .../clock/renesas,r8a73a4-cpg-clocks.txt      | 33 --------
>      .../clock/renesas,r8a73a4-cpg-clocks.yaml     | 70 ++++++++++++++++
>      .../clock/renesas,r8a7740-cpg-clocks.txt      | 41 ----------
>      .../clock/renesas,r8a7740-cpg-clocks.yaml     | 81 +++++++++++++++++++
>      .../clock/renesas,r8a7778-cpg-clocks.txt      | 47 -----------
>      .../clock/renesas,r8a7778-cpg-clocks.yaml     | 64 +++++++++++++++
>      .../clock/renesas,r8a7779-cpg-clocks.txt      | 49 -----------
>      .../clock/renesas,r8a7779-cpg-clocks.yaml     | 65 +++++++++++++++
>      .../bindings/clock/renesas,rz-cpg-clocks.txt  | 53 ------------
>      .../bindings/clock/renesas,rz-cpg-clocks.yaml | 66 +++++++++++++++
>      .../clock/renesas,sh73a0-cpg-clocks.txt       | 35 --------
>      .../clock/renesas,sh73a0-cpg-clocks.yaml      | 69 ++++++++++++++++
>      12 files changed, 415 insertions(+), 258 deletions(-)
>      delete mode 100644 Documentation/devicetree/bindings/clock/renesas,r8a73a4-cpg-clocks.txt
>      create mode 100644 Documentation/devicetree/bindings/clock/renesas,r8a73a4-cpg-clocks.yaml
>      delete mode 100644 Documentation/devicetree/bindings/clock/renesas,r8a7740-cpg-clocks.txt
>      create mode 100644 Documentation/devicetree/bindings/clock/renesas,r8a7740-cpg-clocks.yaml
>      delete mode 100644 Documentation/devicetree/bindings/clock/renesas,r8a7778-cpg-clocks.txt
>      create mode 100644 Documentation/devicetree/bindings/clock/renesas,r8a7778-cpg-clocks.yaml
>      delete mode 100644 Documentation/devicetree/bindings/clock/renesas,r8a7779-cpg-clocks.txt
>      create mode 100644 Documentation/devicetree/bindings/clock/renesas,r8a7779-cpg-clocks.yaml
>      delete mode 100644 Documentation/devicetree/bindings/clock/renesas,rz-cpg-clocks.txt
>      create mode 100644 Documentation/devicetree/bindings/clock/renesas,rz-cpg-clocks.yaml
>      delete mode 100644 Documentation/devicetree/bindings/clock/renesas,sh73a0-cpg-clocks.txt
>      create mode 100644 Documentation/devicetree/bindings/clock/renesas,sh73a0-cpg-clocks.yaml
> ---
>  .../bindings/clock/renesas,cpg-clocks.yaml    | 241 ++++++++++++++++++
>  .../clock/renesas,r8a73a4-cpg-clocks.txt      |  33 ---
>  .../clock/renesas,r8a7740-cpg-clocks.txt      |  41 ---
>  .../clock/renesas,r8a7778-cpg-clocks.txt      |  47 ----
>  .../clock/renesas,r8a7779-cpg-clocks.txt      |  49 ----
>  .../bindings/clock/renesas,rz-cpg-clocks.txt  |  53 ----
>  .../clock/renesas,sh73a0-cpg-clocks.txt       |  35 ---
>  7 files changed, 241 insertions(+), 258 deletions(-)
>  create mode 100644 Documentation/devicetree/bindings/clock/renesas,cpg-clocks.yaml
>  delete mode 100644 Documentation/devicetree/bindings/clock/renesas,r8a73a4-cpg-clocks.txt
>  delete mode 100644 Documentation/devicetree/bindings/clock/renesas,r8a7740-cpg-clocks.txt
>  delete mode 100644 Documentation/devicetree/bindings/clock/renesas,r8a7778-cpg-clocks.txt
>  delete mode 100644 Documentation/devicetree/bindings/clock/renesas,r8a7779-cpg-clocks.txt
>  delete mode 100644 Documentation/devicetree/bindings/clock/renesas,rz-cpg-clocks.txt
>  delete mode 100644 Documentation/devicetree/bindings/clock/renesas,sh73a0-cpg-clocks.txt
> 

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

      parent reply	other threads:[~2020-05-28 20:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-18  8:16 [PATCH v2] dt-bindings: clock: renesas: cpg: Convert to json-schema Geert Uytterhoeven
2020-05-26 23:25 ` Stephen Boyd
2020-05-28 20:34 ` Rob Herring [this message]

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=20200528203419.GA631266@bogus \
    --to=robh@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=geert+renesas@glider.be \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=robh+dt@kernel.org \
    --cc=sboyd@kernel.org \
    /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).