zephyr/scripts/dts/test-bindings/device-on-bar-bus.yaml

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

description: Device on bar bus

compatible: "on-bus"

on-bus: "bar"
scripts: dts: Change 'child/parent: bus: ...' to 'child/parent-bus:' Instead of child: bus: foo parent: bus: bar , have child-bus: foo parent-bus: bar 'bus' is the only key that ever appears under 'child' and 'parent'. Support the old keys for backwards compatibility, with a deprecation warning if they're used. Also add 'child/parent-bus' tests to the edtlib test suite. It was untested before. I also considered putting more stuff under 'child' and 'parent', but there's not much point when there's just a few keys I think. Top-level stuff is cleaner and easier to read. I'm planning to add a 'child-binding' key a bit later (like 'sub-node', but more flexible), and child-* is consistent with that. Also add an unrelated test-bindings/grandchild-3.yaml that was accidentally left out earlier. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no> 2019-09-16 22:42:18 +08:00			`# SPDX-License-Identifier: BSD-3-Clause`

			`description: Device on bar bus`

			`compatible: "on-bus"`

scripts: edtlib: Rename 'child-bus:'/'parent-bus:' to 'bus:'/'on-bus:' I keep mixing these up, so that's probably a sign that the names are bad. The root of the problem is that "parent-bus" can be read as both "this is the parent bus" and as "the parent bus is this". Use 'bus:' for the bus "provider" and 'on-bus:' for nodes on the bus instead, which is less confusing. Support the old keys for backwards compatibility, along with a deprecation warning. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no> 2019-11-27 05:19:55 +08:00			`on-bus: "bar"`