Lines Matching full:schema

5 # All the top-level keys are standard json-schema keywords except for
10 $id: http://devicetree.org/schemas/example-schema.yaml#
11 # $schema is the meta-schema this schema should be validated with.
12 $schema: http://devicetree.org/meta-schemas/core.yaml#
14 title: An example schema annotated with jsonschema details
29   # 'select' is a schema applied to a DT node to determine if this binding
30   # schema should be applied to the node. It is optional and by default the
33   # In this case, a 'false' schema will never match.
36   # A dictionary of DT properties for this binding schema
38     # More complicated schema can use oneOf (XOR), anyOf (OR), or allOf (AND)
42     # The boolean schema must be a list of schemas.
64     # The core schema already checks that reg values are numbers, so device
65     # specific schema don't need to do those checks.
74     # The core schema enforces this (*-names) is a string array
116     # The core schema handles that this must be a single integer.
124     # The type is set in the core schema. Per device schema only need to set
140   # Vendor specific properties have slightly different schema requirements than
150       properties are one case where the json-schema 'type' keyword can be used
156       core schema.
168     description: Child nodes are just another property from a json-schema
173         description: Child node properties have all the same schema
195 # if/then schema can be used to handle conditions on a property affecting
199 # For multiple 'if' schema, group them under an 'allOf'.
202 # the binding into separate schema documents.
212   # Altering schema depending on presence of properties is usually done by
222 # Ideally, the schema should have this line otherwise any other properties
226 # This can't be used in cases where another schema is referenced
228 # If and only if another schema is referenced and arbitrary children nodes can