Lines Matching +full:a +full:- +full:child +full:- +full:node +full:- +full:property
1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
4 ---
5 # All the top-level keys are standard json-schema keywords except for
8 # $id is a unique identifier based on the filename. There may or may not be a
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#
17 - Rob Herring <robh@kernel.org>
20 A more detailed multi-line description of the binding.
26 begin with a tab character.
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
40 # In this case, it's needed to handle a variable number of values as there
41 # isn't another way to express a constraint of the last string value.
42 # The boolean schema must be a list of schemas.
44 - items:
45 # items is a list of possible values for the property. The number of
51 - enum:
52 - vendor,soc4-ip
53 - vendor,soc3-ip
54 - vendor,soc2-ip
55 - enum:
56 - vendor,soc1-ip
59 - items:
60 # 'const' is just a special case of an enum with a single possible value
61 - const: vendor,soc1-ip
69 - description: core registers
70 - description: aux registers
73 reg-names:
74 # The core schema enforces this (*-names) is a string array
76 - const: core
77 - const: aux
80 # Cases that have only a single entry just need to express that with maxItems
82 description: bus clock. A description is only needed for a single item if
84 The items should have a fixed order, so pattern matching names are
87 clock-names:
89 - const: bus
95 - description: tx or combined interrupt
96 - description: rx interrupt
98 A variable number of interrupts warrants a description of what conditions
101 The items should have a fixed order, so pattern matching names are
104 interrupt-names:
108 - const: tx irq
109 - const: rx irq
111 # Property names starting with '#' must be quoted
112 '#interrupt-cells':
113 # A simple case where the value must always be '2'.
114 # The core schema handles that this must be a single integer.
117 interrupt-controller: true
118 # The core checks this is a boolean, so just have to list it here to be
121 clock-frequency:
126 # The value that should be used if the property is not present
129 foo-gpios:
131 description: A connection of the 'foo' gpio line.
133 # *-supply is always a single phandle, so nothing more to define.
134 foo-supply: true
139 # common properties. They must have at least a type definition and
141 vendor,int-property:
142 description: Vendor specific properties must have a description
146 vendor,bool-property:
147 description: Vendor specific properties must have a description. Boolean
148 properties are one case where the json-schema 'type' keyword can be used
152 vendor,string-array-property:
153 description: Vendor specific properties should reference a type in the
155 $ref: /schemas/types.yaml#/definitions/string-array
157 - enum: [foo, bar]
158 - enum: [baz, boo]
160 vendor,property-in-standard-units-microvolt:
161 description: Vendor specific properties having a standard unit suffix
162 don't need a type.
165 child-node:
166 description: Child nodes are just another property from a json-schema
170 vendor,a-child-node-property:
171 description: Child node properties have all the same schema
176 - vendor,a-child-node-property
180 # 'vendor,bool-property' is only allowed when 'vendor,string-array-property'
182 vendor,bool-property: [ 'vendor,string-array-property' ]
185 vendor,string-array-property: [ 'vendor,bool-property' ]
188 - compatible
189 - reg
190 - interrupts
191 - interrupt-controller
193 # if/then schema can be used to handle conditions on a property affecting
194 # another property. A typical case is a specific 'compatible' value changes the
202 - if:
206 const: vendor,soc2-ip
209 - foo-supply
212 - if:
214 - vendor,bool-property
217 vendor,int-property:
221 # present are allowed. There's a few common properties such as 'status' and
222 # 'pinctrl-*' which are added automatically by the tooling.
227 # appear, "unevaluatedProperties: false" could be used. A typical example is
234 # Examples have a default #address-cells and #size-cells value of 1. This can
235 # be overridden or an appropriate parent bus node should be shown (such as on
239 - |
240 node@1000 {
241 compatible = "vendor,soc4-ip", "vendor,soc1-ip";
244 reg-names = "core", "aux";
246 interrupt-controller;