From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Grant Likely <grant.likely@arm.com>
Cc: Rob Herring <robh@kernel.org>,
Frank Rowand <frowand.list@gmail.com>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
devicetree-spec@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Linus Walleij <linus.walleij@linaro.org>,
Thierry Reding <thierry.reding@gmail.com>,
Mark Brown <broonie@kernel.org>, Shawn Guo <shawnguo@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Arnd Bergmann <arnd@arndb.de>, Stephen Boyd <sboyd@kernel.org>,
Jonathan Cameron <jic23@kernel.org>
Subject: Re: [RFC PATCH] dt-bindings: add a jsonschema binding example
Date: Mon, 23 Apr 2018 18:49:59 +0200 [thread overview]
Message-ID: <CAMuHMdU8q0VUxw-EXDqjjYbjeCwCkKuDJUjO0vSaCVrYLXqX4A@mail.gmail.com> (raw)
In-Reply-To: <d2ed3578-ca09-15a6-e688-ffb9a097c2aa@arm.com>
Hi Grant,
On Mon, Apr 23, 2018 at 4:47 PM, Grant Likely <grant.likely@arm.com> wrote:
> On 21/04/2018 02:28, Rob Herring wrote:
>> On Fri, Apr 20, 2018 at 4:00 PM, Frank Rowand <frowand.list@gmail.com>
>> wrote:
>>>> + interrupts:
>>>> + # Either 1 or 2 interrupts can be present
>>>> + minItems: 1
>>>> + maxItems: 2
>>>> + items:
>>>> + - description: tx or combined interrupt
>>>> + - description: rx interrupt
>>>> +
>>>> + description: |
>>>> + A variable number of interrupts warrants a description of what
>>>> conditions
>>>> + affect the number of interrupts. Otherwise, descriptions on
>>>> standard
>>>> + properties are not necessary.
>>>> +
>>>> + interrupt-names:
>>>> + # minItems must be specified here because the default would be 2
>>>> + minItems: 1
>>>
>>> Why the difference between the interrupts property and the
>>> interrupt-names
>>> property (specifying maxItems for interrupt, but not interrupt-names)?
>>
>> I should probably have maxItems here too.
>>
>>> Others have already commented on a desire to have a way to specify that
>>> number of interrupts should match number of interrupt-names.
>>
>> Yeah, but I don't see a way to do that. You could stick the array size
>> constraints in a common definition and have a $ref to that definition
>> from both, but that doesn't really save you too much.
>
>
> There has been discussions in the jsonschema community regarding
> referencing data in the document when applying the schema.
>
> https://github.com/json-schema-org/json-schema-spec/issues/549
>
> However, those discussions are ongoing and have been pushed back to
> after draft-8 (the current release is draft-7). We can instead define
> DT-specific keywords and extend the validator to make it do what we
> want. We need to do something very similar to validate that the length
> of tuples in 'reg', 'interrupts', and '*gpios' match the '#*-cells' values.
Checking that property lengths match the corresponding #*-cells cannot
be done for a schema, but only for the final DTS, as #*-cells is a property
of the target node, right?
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2018-04-23 16:50 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-18 22:29 [RFC PATCH] dt-bindings: add a jsonschema binding example Rob Herring
2018-04-20 16:47 ` Stephen Boyd
2018-04-20 18:15 ` Rob Herring
2018-04-20 19:53 ` Frank Rowand
2018-04-20 23:41 ` Stephen Boyd
2018-04-21 1:34 ` Rob Herring
2018-04-23 14:01 ` Grant Likely
2018-04-23 14:38 ` Rob Herring
2018-04-23 14:49 ` Grant Likely
2018-04-20 16:59 ` Mark Brown
2018-04-20 18:47 ` Rob Herring
2018-04-20 21:00 ` Frank Rowand
2018-04-21 1:28 ` Rob Herring
2018-04-23 7:25 ` Geert Uytterhoeven
2018-04-23 14:47 ` Grant Likely
2018-04-23 16:49 ` Geert Uytterhoeven [this message]
2018-04-25 10:15 ` Grant Likely
2018-04-25 0:33 ` Frank Rowand
2018-11-14 19:39 ` jonsmirl
2018-11-15 23:42 ` Rob Herring
2018-11-16 1:34 ` jonsmirl
2018-04-20 21:47 ` Bjorn Andersson
2018-04-23 16:51 ` Rob Herring
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=CAMuHMdU8q0VUxw-EXDqjjYbjeCwCkKuDJUjO0vSaCVrYLXqX4A@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=arnd@arndb.de \
--cc=bjorn.andersson@linaro.org \
--cc=broonie@kernel.org \
--cc=devicetree-spec@vger.kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=geert+renesas@glider.be \
--cc=grant.likely@arm.com \
--cc=jic23@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh@kernel.org \
--cc=sboyd@kernel.org \
--cc=shawnguo@kernel.org \
--cc=thierry.reding@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).