Searched full:schema (Results 1 – 25 of 216) sorted by relevance
123456789
3 Writing DeviceTree Bindings in json-schema6 Devicetree bindings are written using json-schema vocabulary. Schema files are11 Schema Contents14 Each schema doc is a structured json-schema which is defined by a set of16 top-level json-schema properties used are:19 A json-schema unique identifier string. The string must be a valid20 URI typically containing the binding's filename and path. For DT schema, it must22 references to other files specified in schema "$ref" properties. A $ref values25 of the current schema file's '$id' value. A URL is used even for local files,28 $schema[all …]
5 # All the top-level keys are standard json-schema keywords except for10 $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 details29 # 'select' is a schema applied to a DT node to determine if this binding30 # schema should be applied to the node. It is optional and by default the33 # In this case, a 'false' schema will never match.36 # A dictionary of DT properties for this binding schema38 # More complicated schema can use oneOf (XOR), anyOf (OR), or allOf (AND)[all …]
4 DT_MK_SCHEMA ?= dt-mk-schema14 DT_TMP_SCHEMA := processed-schema.yaml17 quiet_cmd_mk_schema = SCHEMA $@
2 processed-schema.yaml
5 $schema: http://devicetree.org/meta-schemas/core.yaml#14 # The dt-schema tools will generate a select statement first by using
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
