Devicetree/Bindings: Difference between revisions
No edit summary |
|||
(2 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
{{Navbox devicetree}} | |||
Devicetrees are validated using '''devicetree schema'''; this schema specifies allowed properties for nodes based on their <code>compatible</code> string. Devicetree schema is defined through '''bindings''', YAML files containing schema information (older bindings use TXT format, but this is deprecated). | Devicetrees are validated using '''devicetree schema'''; this schema specifies allowed properties for nodes based on their <code>compatible</code> string. Devicetree schema is defined through '''bindings''', YAML files containing schema information (older bindings use TXT format, but this is deprecated). | ||
Bindings for most Linux components can be found in <code>Documentation/devicetree/bindings</code>; there is also a [https://github.com/devicetree-org/dt-schema core DT schema] defining the most basic components and syntax. | Bindings for most Linux components can be found in <code>Documentation/devicetree/bindings</code>; there is also a [https://github.com/devicetree-org/dt-schema core DT schema] defining the most basic components and syntax. | ||
== | == Validating DT bindings == | ||
The Linux kernel has tools for validating devicetree schema bindings. Getting the DT binding check to pass is required for upstreaming the binding. | The Linux kernel has tools for validating devicetree schema bindings. Getting the DT binding check to pass is required for upstreaming the binding. |