Lines Matching full:are

6 Devicetree bindings are written using json-schema vocabulary. Schema files are
18 top-level json-schema properties used are:
47   block. The options are controlled with indicator characters following the key
50   parsed correctly, but are important when the text blocks are rendered to
51   another form. The options are as follows.
54   line breaks and leading whitespace are stripped. Paragraphs are delimited by
58   restrictions are on what the first character can be.
63   breaks on indented lines are also maintained.
78   schema. By default, without 'select', nodes are matched against their possible
88   binding. The exact schema syntax depends on whether properties are known,
89   common properties (e.g. 'interrupts') or are binding/vendor-specific
98   Optional. Similar to 'properties', but names are regex.
109   being objects, are supposed to have one as well.
121       schemas are supposed to be referenced by other schemas, which then use
130 Unless noted otherwise, all properties are required.
137 vocabulary for that property. The properties schemas are what are used for
141 binding schema need to be defined such as how many values are valid or what
142 possible values are valid.
149 dtc. They are simplified to make them more compact and avoid a bunch of
151 validation. There are currently 2 transformations the tools perform.
153 The default for arrays in json-schema is they are variable-sized and allow more
156 size is desired in most cases, so these properties are added based on the
161 is present. Single entries in schemas are fixed up to match this encoding.
187 installed. Ensure they are in your PATH (~/.local/bin by default).
195 schema for the schema) to ensure they are both valid json-schema and valid