linux-kernel - Re: The future of DT binding maintainership

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 23 Jul 2013 08:52:40 -0700
From:	Stephen Warren <swarren@...dotorg.org>
To:	"Chaiken, Alison" <Alison_Chaiken@...tor.com>
CC:	Tomasz Figa <tomasz.figa@...il.com>,
	Grant Likely <grant.likely@...retlab.ca>,
	Wolfram Sang <w.sang@...gutronix.de>,
	Mark Rutland <mark.rutland@....com>,
	Ian Campbell <ian.campbell@...rix.com>,
	Pawel Moll <pawel.moll@....com>,
	"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
	"devicetree-discuss@...ts.ozlabs.org" 
	<devicetree-discuss@...ts.ozlabs.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Rob Herring <rob.herring@...xeda.com>,
	Olof Johansson <olof@...om.net>,
	Mark Brown <broonie@...nsource.wolfsonmicro.com>,
	Linus Walleij <linus.walleij@...aro.org>
Subject: Re: The future of DT binding maintainership

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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/