Lines Matching full:properties

15 top-level properties. Generally, there is one binding defined per file. The
16 top-level json-schema properties used are:
22   references to other files specified in schema "$ref" properties. A $ref value
54  properties
55   A set of sub-schema defining all the DT properties for the
56   binding. The exact schema syntax depends on whether properties are known,
57   common properties (e.g. 'interrupts') or are binding/vendor specific properties.
59 A property can also define a child DT node with child properties defined
62 For more details on properties sections, see 'Property Schema' section.
65   Optional. Similar to 'properties', but names are regex.
68   A list of DT properties from the 'properties' section that
75 Unless noted otherwise, all properties are required.
80 The 'properties' section of the schema contains all the DT properties for a
82 vocabulary for that property. The properties schemas are what is used for
85 For common properties, only additional constraints not covered by the common
89 Vendor specific properties will typically need more detailed schema. With the
90 exception of boolean properties, they should have a reference to a type in
101 size is desired in most cases, so these properties are added based on the