Lines Matching +full:reg +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
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.
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:
61 - const: vendor,soc1-ip
63 reg:
64 # The core schema already checks that reg values are numbers, so device
67 # the number of reg entries.
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
87 clock-names:
89 - const: bus
95 - description: tx or combined interrupt
96 - description: rx interrupt
104 interrupt-names:
108 - const: tx irq
109 - const: rx irq
111 # Property names starting with '#' must be quoted
112 '#interrupt-cells':
117 interrupt-controller: true
121 clock-frequency:
122 # The type is set in the core schema. Per-device schema only need to set
126 # The value that should be used if the property is not present
129 foo-gpios:
133 # *-supply is always a single phandle, so nothing more to define.
134 foo-supply: true
136 # Vendor-specific properties
138 # Vendor-specific properties have slightly different schema requirements than
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
165 vendor,int-array-variable-length-and-constrained-values:
168 $ref: /schemas/types.yaml#/definitions/uint32-array
175 child-node:
176 description: Child nodes are just another property from a json-schema
180 vendor,a-child-node-property:
186 - vendor,a-child-node-property
190 # 'vendor,bool-property' is only allowed when 'vendor,string-array-property'
192 vendor,bool-property: [ 'vendor,string-array-property' ]
195 vendor,string-array-property: [ 'vendor,bool-property' ]
198 - compatible
199 - reg
200 - interrupts
201 - interrupt-controller
203 # if/then schema can be used to handle conditions on a property affecting
204 # another property. A typical case is a specific 'compatible' value changes the
212 - if:
216 const: vendor,soc2-ip
219 - foo-supply
221 # If otherwise the property is not allowed:
223 foo-supply: false
226 - if:
228 - vendor,bool-property
231 vendor,int-property:
236 # 'pinctrl-*' which are added automatically by the tooling.
248 # Examples have a default #address-cells and #size-cells value of 1. This can
252 # Any includes used have to be explicitly included. Use 4-space indentation.
253 - |
255 compatible = "vendor,soc4-ip", "vendor,soc1-ip";
256 reg = <0x1000 0x80>,
258 reg-names = "core", "aux";
260 interrupt-controller;