RFC Device Tree schemas and validation
Get series with b4
b4 am [email protected]Versions newest first
- v1 RFC Latest0 of 15 patches 0 repliesNew
Patches in v1 No applies recorded yet
None of the 15 patches the cover letter announces are in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [RFC 00/15] Device Tree schemas and validation
Quoted 13 lines · Mark Brown
Quoted 11 lines · David Gibson
Quoted 3 lines · Rob Herring
I would expect the schema to replace
Documentation/devicetree/bindings/*over time. I think the thing that needs to be worked out here is how to add free form multi-line text.I'm not convinced that's a realistic goal. As I see it, the fundamental difference between a binding document and a formal schema is that a binding defines both the syntax required of a node, and its semantics, whereas a schema defines only syntax - the semantics still need to be defined somewhere.
Quoted 3 lines
So long as the schema lets you include free form text to define the semantics I'm not sure there's an incompatibility there - the same document can cover both.
True, there's no reason the machine-readable schema and human-readable documentation can't be contained in the same file.
Signature · 4 lines
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