Lines Matching full:binding

17 top-level properties. Generally, there is one binding defined per file. The
22   URI typically containing the binding's filename and path. For DT schema, it must
34   A one-line description of the hardware being described in the binding schema.
38   for maintainers of this binding.
83   include other schemas the binding conforms to. This may be schemas for a
88   binding. The exact schema syntax depends on whether properties are known,
89   common properties (e.g. 'interrupts') or are binding/vendor-specific
113       binding allows subset of properties from other referenced schemas.
116       Used when this binding references other schema whose all properties
125   Optional. A list of one or more DTS hunks implementing this binding only.
127   provider binding, other nodes referenced by phandle.
136 binding. Each property contains a set of constraints using json-schema
141 binding schema need to be defined such as how many values are valid or what
176 binding documents and validate DTS files using the DT schema. The DT schema
194 The DT schema binding documents must be validated using the meta-schema (the
196 binding schema. All of the DT binding documents can be validated using the
205 Note that ``dtbs_check`` will skip any binding schema files with errors. It is
207 binding schema files.