mirror of
https://github.com/zephyrproject-rtos/zephyr
synced 2025-08-08 15:15:33 +00:00
d834b69bd9
Have
include: foo.dts
include: [foo.dts, bar.dts]
instead of
inherits:
!include foo.dts
inherits:
!include [foo.dts, bar.dts]
This is a nicer and shorter and less cryptic syntax, and will make it
possible to get rid of the custom PyYAML constructor for '!include'
later.
'inherits: !include ...' is still supported for backwards compatibility
for now. Later on, I'm planning to mass-replace it, add a deprecation
warning if it's used, and document 'include:'. Then the '!include'
implementation can be removed a bit later.
'!include' has caused issues in the past (see the comment above the
add_constructor() call), gets iffy with multiple EDT instances, and
makes the code harder to follow.
I'm guessing '!include' might've been intended to be useful outside of
'inherits:' originally, but that's the only place where it's used. It's
undocumented that it's possible to put it elsewhere.
To implement the backwards compatibility, the code just transforms
inherits:
!include foo.dts
into
inherits:
- foo.dts
and treats 'inherits:' similarly to 'include:'. Previously, !include
inserted the contents of the included file instead.
Some more sanity checks for 'include:'/'inherits:' are included as well.
Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
|
||
|---|---|---|
| .. | ||
| child.yaml | ||
| clock-1-cell.yaml | ||
| clock-2-cell.yaml | ||
| false-positive.yaml | ||
| fixed-clock.yaml | ||
| gpio-1-cell.yaml | ||
| gpio-2-cell.yaml | ||
| grandchild-1.yaml | ||
| grandchild-2.yaml | ||
| interrupt-1-cell.yaml | ||
| interrupt-2-cell.yaml | ||
| interrupt-3-cell.yaml | ||
| io-channel.yaml | ||
| multidir.yaml | ||
| parent.yaml | ||
| props.yaml | ||
| pwm-1-cell.yaml | ||
| pwm-0-cell.yaml | ||
| sub-node-parent.yaml | ||