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.
53   include other schemas the binding conforms to. This may be schemas for a
58   binding. The exact schema syntax depends on whether properties are known,
59   common properties (e.g. 'interrupts') or are binding/vendor-specific
83       binding allows subset of properties from other referenced schemas.
86       Used when this binding references other schema whose all properties
95   Optional. A list of one or more DTS hunks implementing this binding only.
97   provider binding, other nodes referenced by phandle.
106 binding. Each property contains a set of constraints using json-schema
111 binding schema need to be defined such as how many values are valid or what
146 binding documents and validate DTS files using the DT schema. The DT schema
164 The DT schema binding documents must be validated using the meta-schema (the
166 binding schema. All of the DT binding documents can be validated using the
175 Note that ``dtbs_check`` will skip any binding schema files with errors. It is
177 binding schema files.