Home
last modified time | relevance | path

Searched full:schema (Results 1 – 25 of 3619) sorted by relevance

12345678910>>...145

/Documentation/devicetree/bindings/
Dwriting-schema.rst3 Writing Devicetree Bindings in json-schema
6 Devicetree bindings are written using json-schema vocabulary. Schema files are
11 Also see :ref:`example-schema`.
13 Schema Contents
16 Each schema doc is a structured json-schema which is defined by a set of
18 top-level json-schema properties used are:
21 A json-schema unique identifier string. The string must be a valid
22 URI typically containing the binding's filename and path. For DT schema, it must
24 references to other files specified in schema "$ref" properties. A $ref value
27 components of the current schema file's '$id' value. A URL is used even for
[all …]
Dexample-schema.yaml5 # 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#
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.
[all …]
DMakefile4 DT_MK_SCHEMA ?= dt-mk-schema
29 -name 'processed-schema*' \)
48 quiet_cmd_mk_schema = SCHEMA $@
63 $(obj)/processed-schema.json: $(DT_DOCS) check_dtschema_version FORCE
73 always-y += processed-schema.json
82 dt_compatible_check: $(obj)/processed-schema.json
D.gitignore3 /processed-schema*.yaml
4 /processed-schema*.json
Dwriting-bindings.rst56 https://github.com/devicetree-org/dt-schema/blob/main/dtschema/schemas/property-units.yaml
72 - Properties without schema types (e.g. without standard suffix or not defined
73 by schema) need the type, even if this is an enum.
75 - If schema includes other schema (e.g. /schemas/i2c/i2c-controller.yaml) use
Dsubmitting-patches.rst27 2) DT binding files are written in DT schema format using json-schema
33 See Documentation/devicetree/bindings/writing-schema.rst for more details
34 about schema and tools setup.
Dincomplete-devices.yaml5 $schema: http://devicetree.org/meta-schemas/core.yaml#
19 Following list of devices is an incomplete schema with a goal to pass DT schema
253 unlikely to get converted to DT schema.
259 unlikely to get converted to DT schema.
Dgraph.txt1 This file has moved to graph.yaml in dt-schema repo
Dindex.rst9 writing-schema
/Documentation/devicetree/bindings/clock/
Dclock-bindings.txt1 This file has moved to the clock binding schema:
2 https://github.com/devicetree-org/dt-schema/blob/main/dtschema/schemas/clock/clock.yaml
Dallwinner,sun4i-a10-mod0-clk.yaml5 $schema: http://devicetree.org/meta-schemas/core.yaml#
25 # PRCM's schema. Make sure we only validate standalone nodes.
/Documentation/userspace-api/netlink/
Dspecs.rst24 This document describes details of the schema.
34 There are four schema levels for Netlink specs, from the simplest used
42 customization of define and enum type and value names; this schema should
45 - ``genetlink-legacy`` - Generic Netlink catch all schema supporting quirks of
47 - ``netlink-raw`` - catch all schema supporting pre-Generic Netlink protocols
53 Schema structure
56 YAML schema has the following conceptual sections:
64 Most properties in the schema accept (or in fact require) a ``doc``
68 schema. See the documentation of :doc:`genetlink-c <c-code-gen>`
92 The schema level, default is ``genetlink``, which is the only value
/Documentation/devicetree/bindings/memory-controllers/
Dmc-peripheral-props.yaml5 $schema: http://devicetree.org/meta-schemas/core.yaml#
16 should go in their own separate schema that should be referenced
/Documentation/devicetree/bindings/reset/
Dallwinner,sun6i-a31-clock-reset.yaml5 $schema: http://devicetree.org/meta-schemas/core.yaml#
25 # PRCM's schema. Make sure we only validate standalone nodes.
/Documentation/devicetree/bindings/soc/renesas/
Drenesas-soc.yaml5 $schema: http://devicetree.org/meta-schemas/core.yaml#
66 # schema hits all compatibles that have at lest one Renesas compatible
68 # that don't match the schema select pattern. For example,
/Documentation/devicetree/bindings/interrupt-controller/
Dintel,ce4100-ioapic.yaml5 $schema: http://devicetree.org/meta-schemas/core.yaml#
26 This schema defines bindings for I/O APIC interrupt controller.
Dintel,ce4100-lapic.yaml5 $schema: http://devicetree.org/meta-schemas/core.yaml#
26 This schema defines bindings for local APIC interrupt controller.
/Documentation/devicetree/bindings/memory-controllers/ddr/
Djedec,lpddr-props.yaml5 $schema: http://devicetree.org/meta-schemas/core.yaml#
12 reused for each type. Nodes using this schema should generally be nested under
/Documentation/devicetree/bindings/iio/adc/
Dingenic,adc.yaml6 $schema: http://devicetree.org/meta-schemas/core.yaml#
18 https://github.com/devicetree-org/dt-schema/blob/master/schemas/iio/iio-consumer.yaml,
/Documentation/devicetree/bindings/net/
Dqcom,bam-dmux.yaml5 $schema: http://devicetree.org/meta-schemas/core.yaml#
18 Note that this schema does not directly describe a hardware block but rather
Dlantiq,pef2256.yaml5 $schema: http://devicetree.org/meta-schemas/core.yaml#
93 lantiq,channel-phase = 2, the interleave schema with unused time-slots
98 interleave schema is
102 lantiq,channel-phase = 1, the interleave schema is
/Documentation/devicetree/bindings/arm/
Ddigicolor.yaml5 $schema: http://devicetree.org/meta-schemas/core.yaml#
/Documentation/devicetree/bindings/ata/
Dsnps,dwc-ahci-common.yaml5 $schema: http://devicetree.org/meta-schemas/core.yaml#
13 This document defines device tree schema for the generic Synopsys DWC
/Documentation/devicetree/bindings/sound/
Ddai-common.yaml5 $schema: http://devicetree.org/meta-schemas/core.yaml#
/Documentation/devicetree/bindings/arm/bcm/
Dbrcm,bcm23550.yaml5 $schema: http://devicetree.org/meta-schemas/core.yaml#

12345678910>>...145