Lines Matching refs: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 on the contents of the binding schema.
38   for maintainers of this binding.
42   information about this binding. It should contain things such as what the block
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
76   binding. Note: YAML doesn't allow leading tabs, so spaces must be used instead.
84 binding. Each property contains a set of constraints using json-schema
89 binding schema need to be defined such as how many values are valid or what
124 binding documents and validate DTS files using the DT schema. The DT schema
142 The DT schema binding documents must be validated using the meta-schema (the
144 binding schema. All of the DT binding documents can be validated using the
153 Note that ``dtbs_check`` will skip any binding schema files with errors. It is
155 binding schema files.