From: Stephen Warren <swarren@wwwdotorg.org>
To: "Chaiken, Alison" <Alison_Chaiken@mentor.com>
Cc: Tomasz Figa <tomasz.figa@gmail.com>,
Grant Likely <grant.likely@secretlab.ca>,
Wolfram Sang <w.sang@pengutronix.de>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ian.campbell@citrix.com>,
Pawel Moll <pawel.moll@arm.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"devicetree-discuss@lists.ozlabs.org"
<devicetree-discuss@lists.ozlabs.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Rob Herring <rob.herring@calxeda.com>,
Olof Johansson <olof@lixom.net>,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
Linus Walleij <linus.walleij@linaro.org>
Subject: Re: The future of DT binding maintainership
Date: Tue, 23 Jul 2013 08:52:40 -0700 [thread overview]
Message-ID: <51EEA6C8.6090604@wwwdotorg.org> (raw)
In-Reply-To: <60BA5429A0E1584BA3633194F6F993B502B21362@NA-MBX-03.mgc.mentorg.com>
On 07/22/2013 12:59 PM, Chaiken, Alison wrote:
> Grant Likely wrote:
>> Another thing discussed is that we need to start validating DT schema with an extension to dtc.
>
> Is there a schema out there in the wild that exemplifies what you mean?
>
>> Tomasz Figa has volunteered to do this work and has support from his employer
>
> That's great news.
>
>> to have is that the DT schema will get checked as part of the dts build
>> process so that any DT file that doesn't match the documented schema
>> will get flagged, and that the schema files will be human readable and
>> will double as documentation.
>
> No doubt DTS files are already the best documentation available for many targets.
A nit here:
The DTS files document what HW modules are present on a board, and
various associated parameters.
The bindings describe the format of those DTS files.
The validation here is ensuring that the DTS files are actually written
in a format that matches what the binding definition requires.
So, the issue isn't really documentation of the HW, but rather
documentation of the required DT format, and validating that the DTS
matches that.
next prev parent reply other threads:[~2013-07-23 15:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CACxGe6vtJPbbqwpH8Th5S36Hx50f39j1P4OpLb-Um9xQie6Lng@mail.gmail.com>
2013-07-20 3:46 ` The future of DT binding maintainership Grant Likely
2013-07-20 13:49 ` Tomasz Figa
2013-07-22 19:59 ` Chaiken, Alison
2013-07-22 20:09 ` Tomasz Figa
2013-07-22 21:34 ` Jon Loeliger
2013-07-22 21:57 ` Tomasz Figa
2013-07-23 15:55 ` Stephen Warren
2013-07-24 20:28 ` Grant Likely
2013-07-24 20:26 ` Grant Likely
2013-07-23 15:52 ` Stephen Warren [this message]
2013-07-24 14:11 ` Grant Likely
2013-07-25 7:47 ` David Lang
2013-07-25 17:46 ` Stephen Warren
2013-07-21 10:49 ` David Gibson
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=51EEA6C8.6090604@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=Alison_Chaiken@mentor.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@secretlab.ca \
--cc=ian.campbell@citrix.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=olof@lixom.net \
--cc=pawel.moll@arm.com \
--cc=rob.herring@calxeda.com \
--cc=tomasz.figa@gmail.com \
--cc=w.sang@pengutronix.de \
/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