On Wed, Apr 18, 2018 at 05:29:05PM -0500, Rob Herring wrote: > The current DT binding documentation format of freeform text is painful > to write, review, validate and maintain. > > This is just an example of what a binding in the schema format looks > like. It's using jsonschema vocabulary in a YAML encoded document. Using > jsonschema gives us access to existing tooling. A YAML encoding gives us > something easy to edit. It'd be useful to see some examples of how things like including by reference other schema work. It feels like something we should be able to use more in a schema based thing but perhaps that's not viable with realistic tooling. In general this looks OK, especially with all the meta comments about the language stripped out. > + description: | > + A variable number of interrupts warrants a description of what conditions Like Stephen said the | looks odd. > + interrupt-names: > + # minItems must be specified here because the default would be 2 > + minItems: 1 > + items: > + - const: "tx irq" > + - const: "rx irq" Any way to relate this to the interrupts property in the schema language (eg, must have the less or equal number of elements)? > + # Property names starting with '#' must be quoted That's awkward :/ Perhaps just by convention quote all property names for simplicity?
Attachment:
signature.asc
Description: PGP signature
