Lines Matching full:properties
17 top-level properties. Generally, there is one binding defined per file. The
18 top-level json-schema properties used are:
24 references to other files specified in schema "$ref" properties. A $ref value
56 properties
57 A set of sub-schema defining all the DT properties for the
58 binding. The exact schema syntax depends on whether properties are known,
59 common properties (e.g. 'interrupts') or are binding/vendor specific properties.
61 A property can also define a child DT node with child properties defined
64 For more details on properties sections, see 'Property Schema' section.
67 Optional. Similar to 'properties', but names are regex.
70 A list of DT properties from the 'properties' section that
77 Unless noted otherwise, all properties are required.
82 The 'properties' section of the schema contains all the DT properties for a
84 vocabulary for that property. The properties schemas are what is used for
87 For common properties, only additional constraints not covered by the common
91 Vendor specific properties will typically need more detailed schema. With the
92 exception of boolean properties, they should have a reference to a type in
103 size is desired in most cases, so these properties are added based on the