From: Simon Horman <horms@verge.net.au>
To: Rob Herring <robh+dt@kernel.org>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
Magnus Damm <magnus.damm@gmail.com>,
Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org,
"open list:MEDIA DRIVERS FOR RENESAS - FCP"
<linux-renesas-soc@vger.kernel.org>,
"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] dt-bindings: arm: renesas: Convert 'renesas,prr' to json-schema
Date: Fri, 6 Sep 2019 13:48:57 +0200 [thread overview]
Message-ID: <20190906114857.4mgunm4feehakc4u@verge.net.au> (raw)
In-Reply-To: <CAL_JsqLvU4=kaQ-nSwMuh4VXX67U5URZAPvVJohfKzQsQdFTrA@mail.gmail.com>
On Fri, Sep 06, 2019 at 12:21:58PM +0100, Rob Herring wrote:
> On Fri, Sep 6, 2019 at 12:14 PM Simon Horman <horms+renesas@verge.net.au> wrote:
> >
> > Convert Renesas Product Register bindings documentation to json-schema.
> >
> > Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
> > ---
> > Based on v5.3-rc1
> > Tested using:
> > make dtbs_check DT_SCHEMA_FILES=Documentation/devicetree/bindings/arm/renesas,prr.yaml
> > ---
> > .../devicetree/bindings/arm/renesas,prr.txt | 20 ------------
> > .../devicetree/bindings/arm/renesas,prr.yaml | 36 ++++++++++++++++++++++
> > 2 files changed, 36 insertions(+), 20 deletions(-)
> > delete mode 100644 Documentation/devicetree/bindings/arm/renesas,prr.txt
> > create mode 100644 Documentation/devicetree/bindings/arm/renesas,prr.yaml
> >
> > diff --git a/Documentation/devicetree/bindings/arm/renesas,prr.txt b/Documentation/devicetree/bindings/arm/renesas,prr.txt
> > deleted file mode 100644
> > index 08e482e953ca..000000000000
> > --- a/Documentation/devicetree/bindings/arm/renesas,prr.txt
> > +++ /dev/null
> > @@ -1,20 +0,0 @@
> > -Renesas Product Register
> > -
> > -Most Renesas ARM SoCs have a Product Register or Boundary Scan ID Register that
> > -allows to retrieve SoC product and revision information. If present, a device
> > -node for this register should be added.
> > -
> > -Required properties:
> > - - compatible: Must be one of:
> > - "renesas,prr"
> > - "renesas,bsid"
> > - - reg: Base address and length of the register block.
> > -
> > -
> > -Examples
> > ---------
> > -
> > - prr: chipid@ff000044 {
> > - compatible = "renesas,prr";
> > - reg = <0 0xff000044 0 4>;
> > - };
> > diff --git a/Documentation/devicetree/bindings/arm/renesas,prr.yaml b/Documentation/devicetree/bindings/arm/renesas,prr.yaml
> > new file mode 100644
> > index 000000000000..9df003041456
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/arm/renesas,prr.yaml
> > @@ -0,0 +1,36 @@
> > +# SPDX-License-Identifier: GPL-2.0
> > +%YAML 1.2
> > +---
> > +$id: http://devicetree.org/schemas/arm/renesas,prr.yaml#
> > +$schema: http://devicetree.org/meta-schemas/core.yaml#
> > +
> > +title: Renesas Product Register
> > +
> > +maintainers:
> > + - Geert Uytterhoeven <geert+renesas@glider.be>
> > + - Magnus Damm <magnus.damm@gmail.com>
> > +
> > +description: |
> > + Most Renesas ARM SoCs have a Product Register or Boundary Scan ID
> > + Register that allows to retrieve SoC product and revision information.
> > + If present, a device node for this register should be added.
> > +
> > +properties:
> > + compatible:
> > + oneOf:
> > + - const: "renesas,prr"
> > + - const: "renesas,bsid"
>
> enum is better than oneOf+const and drop the quotes. oneOf/allOf/anyOf
> result in terrible error messages.
Thanks Rob,
Like this?
compatible:
enum:
- renesas,prr
- renesas,bsid
> > + reg:
> > + items:
> > + - description: Base address and length of the register block.
>
> That's what 'reg' *always* is... Just 'maxItems: 1' is sufficient when
> there is" only 1 entry.
And this?
reg:
maxItems: 1
> > +
> > +required:
> > + - compatible
> > + - reg
> > +
> > +examples:
> > + - |
> > + prr: chipid@ff000044 {
> > + compatible = "renesas,prr";
> > + reg = <0 0xff000044 0 4>;
> > + };
> > --
> > 2.11.0
> >
>
next prev parent reply other threads:[~2019-09-06 11:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-06 11:14 [PATCH] dt-bindings: arm: renesas: Convert 'renesas,prr' to json-schema Simon Horman
2019-09-06 11:21 ` Rob Herring
2019-09-06 11:48 ` Simon Horman [this message]
2019-09-06 12:54 ` Rob Herring
2019-09-08 12:06 ` Simon Horman
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=20190906114857.4mgunm4feehakc4u@verge.net.au \
--to=horms@verge.net.au \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=mark.rutland@arm.com \
--cc=robh+dt@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).