zephyr/scripts/dts/test-bindings-2/multidir.yaml

# SPDX-License-Identifier: BSD-3-Clause

description: Binding in test-bindings-2/

compatible: "in-dir-2"
scripts: dts: Add test for multiple binding directories Add two bindings test-bindings/multidir.yaml test-bindings-2/multidir.yaml and a new test-multidir.dts with two nodes that use them. Verify that the two bindings were found by checking the Device.binding_path attribute for the two device nodes. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no> 2019-08-03 05:45:51 +08:00			`# SPDX-License-Identifier: BSD-3-Clause`

			`description: Binding in test-bindings-2/`

scripts: dts: Simplify and improve 'compatible' matching Instead of properties: compatible: constraint: "foo" , just have compatible: "foo" at the top level of the binding. For backwards compatibility, the old 'properties: compatible: ...' form is still accepted for now, and is treated the same as a single-element 'compatible:'. The old syntax was inspired by dt-schema (though it isn't dt-schema-compatible), which is in turn a thin wrapper around json-schema (the idea is to transform .dts files into YAML and then verify them). Maybe the idea was to gradually switch the syntax over to dt-schema and then be able to use unmodified dt-schema bindings, but dt-schema is really a different kind of tool (a completely standalone linter), and works very differently from our stuff (see schemas/dt-core.yaml in the dt-schema repo to get an idea of just how differently). Better to keep it simple. This commit also piggybacks some clarifications to the binding template re. '#cells:'. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no> 2019-08-20 02:32:25 +08:00			`compatible: "in-dir-2"`