From: david@gibson•dropbear.id.au (David Gibson)
To: linux-arm-kernel@lists•infradead.org
Subject: [RFC 00/15] Device Tree schemas and validation
Date: Wed, 2 Oct 2013 23:52:21 +1000 [thread overview]
Message-ID: <20131002135220.GG6506@voom.fritz.box> (raw)
In-Reply-To: <524ACB76.1010001@gmail.com>
On Tue, Oct 01, 2013 at 08:17:42AM -0500, Rob Herring wrote:
> On 10/01/2013 03:06 AM, Benoit Cousson wrote:
> > + more DT maintainers folks
> >
> > Hi all,
> >
> > I know this is mostly boring user space code, but I was expecting a
> > little bit of comments about at least the bindings syntax:-(
> >
> > I'd like to know if this is the right direction and if it worth pursuing
> > in that direction.
> >
> > The idea was to have at least some base for further discussion during
> > ARM KS 2013.
> >
> > I feel alone :-(
> >
> > If you have any comment, go ahead!
>
> Thanks for taking this on!
>
> This is interesting approach using the dts syntax, but I worry that the
> validation will only be as good as the schema written and the review of
> the schema. I think the schema needs to define the binding rather than
> define the checks. Then the schema can feed the validation checks. This
> format does not seem to me as easily being able to generate
> documentation from the schema which I believe is one of the goals. I for
> one don't care to review the documentation and the schema for every binding.
Hrm. I'm less optimistic about entirely replacing human-readable
bindings with machine-readable schemas. But I do think the schema
language needs to be substantially more flexible than the draft
presented here.
While I think a schema syntax which mirrors dts syntax makes a lot of
sense, actually defining schemas as "device" trees doesn't seem quite
right to me.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20131002/83f7e873/attachment.sig>
next prev parent reply other threads:[~2013-10-02 13:52 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-24 16:52 [RFC 00/15] Device Tree schemas and validation Benoit Cousson
2013-10-01 8:06 ` Benoit Cousson
2013-10-01 13:17 ` Rob Herring
2013-10-01 15:06 ` Benoit Cousson
2013-10-01 15:17 ` Jon Loeliger
2013-10-02 8:24 ` David Gibson
2013-10-02 9:25 ` Benoit Cousson
2013-10-02 13:22 ` Jon Loeliger
2013-10-01 20:54 ` Rob Herring
2013-10-02 13:54 ` David Gibson
2013-10-02 18:08 ` Mark Brown
2013-10-02 23:38 ` David Gibson
2013-10-03 6:52 ` Benoit Cousson
2013-10-02 13:52 ` David Gibson [this message]
2013-10-01 22:22 ` Stephen Warren
2013-10-02 14:29 ` David Gibson
2013-10-03 13:53 ` Benoit Cousson
2013-10-06 3:02 ` Chaiken, Alison
2013-10-03 13:17 ` Benoit Cousson
[not found] ` <1380041541-17529-2-git-send-email-bcousson@baylibre.com>
2013-10-02 12:59 ` [RFC 01/15] scripts/dtc: fix most memory leaks in dtc David Gibson
[not found] ` <CAOwMV_zAZG3vvWS6pkyK-FbOEg_32KRO-k1SmFSh-pc9+0JiPA@mail.gmail.com>
2013-10-03 14:26 ` Fabien Parent
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=20131002135220.GG6506@voom.fritz.box \
--to=david@gibson$(echo .)dropbear.id.au \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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