[PATCH 0/5] use .dtso for device tree overlay sources
All device tree overlay sources in the kernel tree have been renamed to .dtso and, since v6.5 (commit 81d362732bac), the .dts -> .dtbo rules is gone from linux' Kbuild.
Let's follow the lead of linux and do the renaming, and sooner rather than later to reduce the amount of churn.
This is not quite complete as there are some files under test/ that still need converting, but as they currently rely on being compiled to .dtb (in order to, in turn, be applicable for the .dtb -> .dtb.S -> .dtb.o rules), that's a bit more involved than simple renaming.
Rasmus Villemoes (5): arm: dts: imx8mm-cl-iot-gate: rename overlay sources to .dtso iot2050: rename overlay sources to .dtso arm64: zynqmp: rename overlay sources to .dtso sandbox: rename overlay sources to .dtso doc: use .dtso as extension for device tree overlay sources
...iot-gate-ied-adc0.dts => imx8mm-cl-iot-gate-ied-adc0.dtso} | 0 ...iot-gate-ied-adc1.dts => imx8mm-cl-iot-gate-ied-adc1.dtso} | 0 ...iot-gate-ied-can0.dts => imx8mm-cl-iot-gate-ied-can0.dtso} | 0 ...iot-gate-ied-can1.dts => imx8mm-cl-iot-gate-ied-can1.dtso} | 0 ...iot-gate-ied-tpm0.dts => imx8mm-cl-iot-gate-ied-tpm0.dtso} | 0 ...iot-gate-ied-tpm1.dts => imx8mm-cl-iot-gate-ied-tpm1.dtso} | 0 ...imx8mm-cl-iot-gate-ied.dts => imx8mm-cl-iot-gate-ied.dtso} | 0 ...k3-am6548-iot2050-advanced-m2-bkey-ekey-pcie-overlay.dtso} | 0 ...s => k3-am6548-iot2050-advanced-m2-bkey-usb3-overlay.dtso} | 0 .../{zynqmp-sck-kr-g-revA.dts => zynqmp-sck-kr-g-revA.dtso} | 0 .../{zynqmp-sck-kr-g-revB.dts => zynqmp-sck-kr-g-revB.dtso} | 0 .../{zynqmp-sck-kv-g-revA.dts => zynqmp-sck-kv-g-revA.dtso} | 0 .../{zynqmp-sck-kv-g-revB.dts => zynqmp-sck-kv-g-revB.dtso} | 0 arch/sandbox/dts/{overlay0.dts => overlay0.dtso} | 0 arch/sandbox/dts/{overlay1.dts => overlay1.dtso} | 0 doc/develop/uefi/uefi.rst | 4 ++-- doc/usage/fdt_overlays.rst | 4 ++-- 17 files changed, 4 insertions(+), 4 deletions(-) rename arch/arm/dts/{imx8mm-cl-iot-gate-ied-adc0.dts => imx8mm-cl-iot-gate-ied-adc0.dtso} (100%) rename arch/arm/dts/{imx8mm-cl-iot-gate-ied-adc1.dts => imx8mm-cl-iot-gate-ied-adc1.dtso} (100%) rename arch/arm/dts/{imx8mm-cl-iot-gate-ied-can0.dts => imx8mm-cl-iot-gate-ied-can0.dtso} (100%) rename arch/arm/dts/{imx8mm-cl-iot-gate-ied-can1.dts => imx8mm-cl-iot-gate-ied-can1.dtso} (100%) rename arch/arm/dts/{imx8mm-cl-iot-gate-ied-tpm0.dts => imx8mm-cl-iot-gate-ied-tpm0.dtso} (100%) rename arch/arm/dts/{imx8mm-cl-iot-gate-ied-tpm1.dts => imx8mm-cl-iot-gate-ied-tpm1.dtso} (100%) rename arch/arm/dts/{imx8mm-cl-iot-gate-ied.dts => imx8mm-cl-iot-gate-ied.dtso} (100%) rename arch/arm/dts/{k3-am6548-iot2050-advanced-m2-bkey-ekey-pcie-overlay.dts => k3-am6548-iot2050-advanced-m2-bkey-ekey-pcie-overlay.dtso} (100%) rename arch/arm/dts/{k3-am6548-iot2050-advanced-m2-bkey-usb3-overlay.dts => k3-am6548-iot2050-advanced-m2-bkey-usb3-overlay.dtso} (100%) rename arch/arm/dts/{zynqmp-sck-kr-g-revA.dts => zynqmp-sck-kr-g-revA.dtso} (100%) rename arch/arm/dts/{zynqmp-sck-kr-g-revB.dts => zynqmp-sck-kr-g-revB.dtso} (100%) rename arch/arm/dts/{zynqmp-sck-kv-g-revA.dts => zynqmp-sck-kv-g-revA.dtso} (100%) rename arch/arm/dts/{zynqmp-sck-kv-g-revB.dts => zynqmp-sck-kv-g-revB.dtso} (100%) rename arch/sandbox/dts/{overlay0.dts => overlay0.dtso} (100%) rename arch/sandbox/dts/{overlay1.dts => overlay1.dtso} (100%)
Distinguish more clearly between source files meant for producing .dtb from those meant for producing .dtbo. No functional change, as we currently have rules for producing a foo.dtbo from either foo.dts or foo.dtso.
Note that in the linux tree, all device tree overlay sources have been renamed to .dtso, and the .dts->.dtbo rule is gone since v6.5 (commit 81d362732bac). So this is also a step towards staying closer to linux with respect to both Kbuild and device tree sources.
Signed-off-by: Rasmus Villemoes rasmus.villemoes@prevas.dk --- ...-cl-iot-gate-ied-adc0.dts => imx8mm-cl-iot-gate-ied-adc0.dtso} | 0 ...-cl-iot-gate-ied-adc1.dts => imx8mm-cl-iot-gate-ied-adc1.dtso} | 0 ...-cl-iot-gate-ied-can0.dts => imx8mm-cl-iot-gate-ied-can0.dtso} | 0 ...-cl-iot-gate-ied-can1.dts => imx8mm-cl-iot-gate-ied-can1.dtso} | 0 ...-cl-iot-gate-ied-tpm0.dts => imx8mm-cl-iot-gate-ied-tpm0.dtso} | 0 ...-cl-iot-gate-ied-tpm1.dts => imx8mm-cl-iot-gate-ied-tpm1.dtso} | 0 .../{imx8mm-cl-iot-gate-ied.dts => imx8mm-cl-iot-gate-ied.dtso} | 0 7 files changed, 0 insertions(+), 0 deletions(-) rename arch/arm/dts/{imx8mm-cl-iot-gate-ied-adc0.dts => imx8mm-cl-iot-gate-ied-adc0.dtso} (100%) rename arch/arm/dts/{imx8mm-cl-iot-gate-ied-adc1.dts => imx8mm-cl-iot-gate-ied-adc1.dtso} (100%) rename arch/arm/dts/{imx8mm-cl-iot-gate-ied-can0.dts => imx8mm-cl-iot-gate-ied-can0.dtso} (100%) rename arch/arm/dts/{imx8mm-cl-iot-gate-ied-can1.dts => imx8mm-cl-iot-gate-ied-can1.dtso} (100%) rename arch/arm/dts/{imx8mm-cl-iot-gate-ied-tpm0.dts => imx8mm-cl-iot-gate-ied-tpm0.dtso} (100%) rename arch/arm/dts/{imx8mm-cl-iot-gate-ied-tpm1.dts => imx8mm-cl-iot-gate-ied-tpm1.dtso} (100%) rename arch/arm/dts/{imx8mm-cl-iot-gate-ied.dts => imx8mm-cl-iot-gate-ied.dtso} (100%)
diff --git a/arch/arm/dts/imx8mm-cl-iot-gate-ied-adc0.dts b/arch/arm/dts/imx8mm-cl-iot-gate-ied-adc0.dtso similarity index 100% rename from arch/arm/dts/imx8mm-cl-iot-gate-ied-adc0.dts rename to arch/arm/dts/imx8mm-cl-iot-gate-ied-adc0.dtso diff --git a/arch/arm/dts/imx8mm-cl-iot-gate-ied-adc1.dts b/arch/arm/dts/imx8mm-cl-iot-gate-ied-adc1.dtso similarity index 100% rename from arch/arm/dts/imx8mm-cl-iot-gate-ied-adc1.dts rename to arch/arm/dts/imx8mm-cl-iot-gate-ied-adc1.dtso diff --git a/arch/arm/dts/imx8mm-cl-iot-gate-ied-can0.dts b/arch/arm/dts/imx8mm-cl-iot-gate-ied-can0.dtso similarity index 100% rename from arch/arm/dts/imx8mm-cl-iot-gate-ied-can0.dts rename to arch/arm/dts/imx8mm-cl-iot-gate-ied-can0.dtso diff --git a/arch/arm/dts/imx8mm-cl-iot-gate-ied-can1.dts b/arch/arm/dts/imx8mm-cl-iot-gate-ied-can1.dtso similarity index 100% rename from arch/arm/dts/imx8mm-cl-iot-gate-ied-can1.dts rename to arch/arm/dts/imx8mm-cl-iot-gate-ied-can1.dtso diff --git a/arch/arm/dts/imx8mm-cl-iot-gate-ied-tpm0.dts b/arch/arm/dts/imx8mm-cl-iot-gate-ied-tpm0.dtso similarity index 100% rename from arch/arm/dts/imx8mm-cl-iot-gate-ied-tpm0.dts rename to arch/arm/dts/imx8mm-cl-iot-gate-ied-tpm0.dtso diff --git a/arch/arm/dts/imx8mm-cl-iot-gate-ied-tpm1.dts b/arch/arm/dts/imx8mm-cl-iot-gate-ied-tpm1.dtso similarity index 100% rename from arch/arm/dts/imx8mm-cl-iot-gate-ied-tpm1.dts rename to arch/arm/dts/imx8mm-cl-iot-gate-ied-tpm1.dtso diff --git a/arch/arm/dts/imx8mm-cl-iot-gate-ied.dts b/arch/arm/dts/imx8mm-cl-iot-gate-ied.dtso similarity index 100% rename from arch/arm/dts/imx8mm-cl-iot-gate-ied.dts rename to arch/arm/dts/imx8mm-cl-iot-gate-ied.dtso
On Mon, Sep 25, 2023 at 10:09:05AM +0200, Rasmus Villemoes wrote:
Distinguish more clearly between source files meant for producing .dtb from those meant for producing .dtbo. No functional change, as we currently have rules for producing a foo.dtbo from either foo.dts or foo.dtso.
Note that in the linux tree, all device tree overlay sources have been renamed to .dtso, and the .dts->.dtbo rule is gone since v6.5 (commit 81d362732bac). So this is also a step towards staying closer to linux with respect to both Kbuild and device tree sources.
Signed-off-by: Rasmus Villemoes rasmus.villemoes@prevas.dk
Applied to u-boot/master, thanks!
Distinguish more clearly between source files meant for producing .dtb from those meant for producing .dtbo. No functional change, as we currently have rules for producing a foo.dtbo from either foo.dts or foo.dtso.
Note that in the linux tree, all device tree overlay sources have been renamed to .dtso, and the .dts->.dtbo rule is gone since v6.5 (commit 81d362732bac). So this is also a step towards staying closer to linux with respect to both Kbuild and device tree sources.
Signed-off-by: Rasmus Villemoes rasmus.villemoes@prevas.dk --- ... => k3-am6548-iot2050-advanced-m2-bkey-ekey-pcie-overlay.dtso} | 0 ...y.dts => k3-am6548-iot2050-advanced-m2-bkey-usb3-overlay.dtso} | 0 2 files changed, 0 insertions(+), 0 deletions(-) rename arch/arm/dts/{k3-am6548-iot2050-advanced-m2-bkey-ekey-pcie-overlay.dts => k3-am6548-iot2050-advanced-m2-bkey-ekey-pcie-overlay.dtso} (100%) rename arch/arm/dts/{k3-am6548-iot2050-advanced-m2-bkey-usb3-overlay.dts => k3-am6548-iot2050-advanced-m2-bkey-usb3-overlay.dtso} (100%)
diff --git a/arch/arm/dts/k3-am6548-iot2050-advanced-m2-bkey-ekey-pcie-overlay.dts b/arch/arm/dts/k3-am6548-iot2050-advanced-m2-bkey-ekey-pcie-overlay.dtso similarity index 100% rename from arch/arm/dts/k3-am6548-iot2050-advanced-m2-bkey-ekey-pcie-overlay.dts rename to arch/arm/dts/k3-am6548-iot2050-advanced-m2-bkey-ekey-pcie-overlay.dtso diff --git a/arch/arm/dts/k3-am6548-iot2050-advanced-m2-bkey-usb3-overlay.dts b/arch/arm/dts/k3-am6548-iot2050-advanced-m2-bkey-usb3-overlay.dtso similarity index 100% rename from arch/arm/dts/k3-am6548-iot2050-advanced-m2-bkey-usb3-overlay.dts rename to arch/arm/dts/k3-am6548-iot2050-advanced-m2-bkey-usb3-overlay.dtso
On 25.09.23 10:09, Rasmus Villemoes wrote:
Distinguish more clearly between source files meant for producing .dtb from those meant for producing .dtbo. No functional change, as we currently have rules for producing a foo.dtbo from either foo.dts or foo.dtso.
Note that in the linux tree, all device tree overlay sources have been renamed to .dtso, and the .dts->.dtbo rule is gone since v6.5 (commit 81d362732bac). So this is also a step towards staying closer to linux with respect to both Kbuild and device tree sources.
Signed-off-by: Rasmus Villemoes rasmus.villemoes@prevas.dk
... => k3-am6548-iot2050-advanced-m2-bkey-ekey-pcie-overlay.dtso} | 0 ...y.dts => k3-am6548-iot2050-advanced-m2-bkey-usb3-overlay.dtso} | 0 2 files changed, 0 insertions(+), 0 deletions(-) rename arch/arm/dts/{k3-am6548-iot2050-advanced-m2-bkey-ekey-pcie-overlay.dts => k3-am6548-iot2050-advanced-m2-bkey-ekey-pcie-overlay.dtso} (100%) rename arch/arm/dts/{k3-am6548-iot2050-advanced-m2-bkey-usb3-overlay.dts => k3-am6548-iot2050-advanced-m2-bkey-usb3-overlay.dtso} (100%)
diff --git a/arch/arm/dts/k3-am6548-iot2050-advanced-m2-bkey-ekey-pcie-overlay.dts b/arch/arm/dts/k3-am6548-iot2050-advanced-m2-bkey-ekey-pcie-overlay.dtso similarity index 100% rename from arch/arm/dts/k3-am6548-iot2050-advanced-m2-bkey-ekey-pcie-overlay.dts rename to arch/arm/dts/k3-am6548-iot2050-advanced-m2-bkey-ekey-pcie-overlay.dtso diff --git a/arch/arm/dts/k3-am6548-iot2050-advanced-m2-bkey-usb3-overlay.dts b/arch/arm/dts/k3-am6548-iot2050-advanced-m2-bkey-usb3-overlay.dtso similarity index 100% rename from arch/arm/dts/k3-am6548-iot2050-advanced-m2-bkey-usb3-overlay.dts rename to arch/arm/dts/k3-am6548-iot2050-advanced-m2-bkey-usb3-overlay.dtso
Reviewed-by: Jan Kiszka jan.kiszka@siemens.com
Jan
On Mon, Sep 25, 2023 at 10:09:06AM +0200, Rasmus Villemoes wrote:
Distinguish more clearly between source files meant for producing .dtb from those meant for producing .dtbo. No functional change, as we currently have rules for producing a foo.dtbo from either foo.dts or foo.dtso.
Note that in the linux tree, all device tree overlay sources have been renamed to .dtso, and the .dts->.dtbo rule is gone since v6.5 (commit 81d362732bac). So this is also a step towards staying closer to linux with respect to both Kbuild and device tree sources.
Signed-off-by: Rasmus Villemoes rasmus.villemoes@prevas.dk Reviewed-by: Jan Kiszka jan.kiszka@siemens.com
Applied to u-boot/master, thanks!
Distinguish more clearly between source files meant for producing .dtb from those meant for producing .dtbo. No functional change, as we currently have rules for producing a foo.dtbo from either foo.dts or foo.dtso.
Note that in the linux tree, all device tree overlay sources have been renamed to .dtso, and the .dts->.dtbo rule is gone since v6.5 (commit 81d362732bac). So this is also a step towards staying closer to linux with respect to both Kbuild and device tree sources.
Signed-off-by: Rasmus Villemoes rasmus.villemoes@prevas.dk --- .../dts/{zynqmp-sck-kr-g-revA.dts => zynqmp-sck-kr-g-revA.dtso} | 0 .../dts/{zynqmp-sck-kr-g-revB.dts => zynqmp-sck-kr-g-revB.dtso} | 0 .../dts/{zynqmp-sck-kv-g-revA.dts => zynqmp-sck-kv-g-revA.dtso} | 0 .../dts/{zynqmp-sck-kv-g-revB.dts => zynqmp-sck-kv-g-revB.dtso} | 0 4 files changed, 0 insertions(+), 0 deletions(-) rename arch/arm/dts/{zynqmp-sck-kr-g-revA.dts => zynqmp-sck-kr-g-revA.dtso} (100%) rename arch/arm/dts/{zynqmp-sck-kr-g-revB.dts => zynqmp-sck-kr-g-revB.dtso} (100%) rename arch/arm/dts/{zynqmp-sck-kv-g-revA.dts => zynqmp-sck-kv-g-revA.dtso} (100%) rename arch/arm/dts/{zynqmp-sck-kv-g-revB.dts => zynqmp-sck-kv-g-revB.dtso} (100%)
diff --git a/arch/arm/dts/zynqmp-sck-kr-g-revA.dts b/arch/arm/dts/zynqmp-sck-kr-g-revA.dtso similarity index 100% rename from arch/arm/dts/zynqmp-sck-kr-g-revA.dts rename to arch/arm/dts/zynqmp-sck-kr-g-revA.dtso diff --git a/arch/arm/dts/zynqmp-sck-kr-g-revB.dts b/arch/arm/dts/zynqmp-sck-kr-g-revB.dtso similarity index 100% rename from arch/arm/dts/zynqmp-sck-kr-g-revB.dts rename to arch/arm/dts/zynqmp-sck-kr-g-revB.dtso diff --git a/arch/arm/dts/zynqmp-sck-kv-g-revA.dts b/arch/arm/dts/zynqmp-sck-kv-g-revA.dtso similarity index 100% rename from arch/arm/dts/zynqmp-sck-kv-g-revA.dts rename to arch/arm/dts/zynqmp-sck-kv-g-revA.dtso diff --git a/arch/arm/dts/zynqmp-sck-kv-g-revB.dts b/arch/arm/dts/zynqmp-sck-kv-g-revB.dtso similarity index 100% rename from arch/arm/dts/zynqmp-sck-kv-g-revB.dts rename to arch/arm/dts/zynqmp-sck-kv-g-revB.dtso
On Mon, Sep 25, 2023 at 10:09:07AM +0200, Rasmus Villemoes wrote:
Distinguish more clearly between source files meant for producing .dtb from those meant for producing .dtbo. No functional change, as we currently have rules for producing a foo.dtbo from either foo.dts or foo.dtso.
Note that in the linux tree, all device tree overlay sources have been renamed to .dtso, and the .dts->.dtbo rule is gone since v6.5 (commit 81d362732bac). So this is also a step towards staying closer to linux with respect to both Kbuild and device tree sources.
Signed-off-by: Rasmus Villemoes rasmus.villemoes@prevas.dk
Applied to u-boot/master, thanks!
Distinguish more clearly between source files meant for producing .dtb from those meant for producing .dtbo. No functional change, as we currently have rules for producing a foo.dtbo from either foo.dts or foo.dtso.
Note that in the linux tree, all device tree overlay sources have been renamed to .dtso, and the .dts->.dtbo rule is gone since v6.5 (commit 81d362732bac). So this is also a step towards staying closer to linux with respect to both Kbuild and device tree sources.
Signed-off-by: Rasmus Villemoes rasmus.villemoes@prevas.dk --- arch/sandbox/dts/{overlay0.dts => overlay0.dtso} | 0 arch/sandbox/dts/{overlay1.dts => overlay1.dtso} | 0 2 files changed, 0 insertions(+), 0 deletions(-) rename arch/sandbox/dts/{overlay0.dts => overlay0.dtso} (100%) rename arch/sandbox/dts/{overlay1.dts => overlay1.dtso} (100%)
diff --git a/arch/sandbox/dts/overlay0.dts b/arch/sandbox/dts/overlay0.dtso similarity index 100% rename from arch/sandbox/dts/overlay0.dts rename to arch/sandbox/dts/overlay0.dtso diff --git a/arch/sandbox/dts/overlay1.dts b/arch/sandbox/dts/overlay1.dtso similarity index 100% rename from arch/sandbox/dts/overlay1.dts rename to arch/sandbox/dts/overlay1.dtso
On Mon, 25 Sept 2023 at 02:10, Rasmus Villemoes rasmus.villemoes@prevas.dk wrote:
Distinguish more clearly between source files meant for producing .dtb from those meant for producing .dtbo. No functional change, as we currently have rules for producing a foo.dtbo from either foo.dts or foo.dtso.
Note that in the linux tree, all device tree overlay sources have been renamed to .dtso, and the .dts->.dtbo rule is gone since v6.5 (commit 81d362732bac). So this is also a step towards staying closer to linux with respect to both Kbuild and device tree sources.
Signed-off-by: Rasmus Villemoes rasmus.villemoes@prevas.dk
arch/sandbox/dts/{overlay0.dts => overlay0.dtso} | 0 arch/sandbox/dts/{overlay1.dts => overlay1.dtso} | 0 2 files changed, 0 insertions(+), 0 deletions(-) rename arch/sandbox/dts/{overlay0.dts => overlay0.dtso} (100%) rename arch/sandbox/dts/{overlay1.dts => overlay1.dtso} (100%)
Reviewed-by: Simon Glass sjg@chromium.org
On Mon, Sep 25, 2023 at 10:09:08AM +0200, Rasmus Villemoes wrote:
Distinguish more clearly between source files meant for producing .dtb from those meant for producing .dtbo. No functional change, as we currently have rules for producing a foo.dtbo from either foo.dts or foo.dtso.
Note that in the linux tree, all device tree overlay sources have been renamed to .dtso, and the .dts->.dtbo rule is gone since v6.5 (commit 81d362732bac). So this is also a step towards staying closer to linux with respect to both Kbuild and device tree sources.
Signed-off-by: Rasmus Villemoes rasmus.villemoes@prevas.dk Reviewed-by: Simon Glass sjg@chromium.org
Applied to u-boot/master, thanks!
Moving towards using .dtso for overlay sources, update the documentation examples to follow that pattern.
Signed-off-by: Rasmus Villemoes rasmus.villemoes@prevas.dk --- doc/develop/uefi/uefi.rst | 4 ++-- doc/usage/fdt_overlays.rst | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/doc/develop/uefi/uefi.rst b/doc/develop/uefi/uefi.rst index a7a41f2fac..34dab3c12c 100644 --- a/doc/develop/uefi/uefi.rst +++ b/doc/develop/uefi/uefi.rst @@ -563,10 +563,10 @@ To insert the lowest supported version into a dtb
.. code-block:: console
- $ dtc -@ -I dts -O dtb -o version.dtbo version.dts + $ dtc -@ -I dts -O dtb -o version.dtbo version.dtso $ fdtoverlay -i orig.dtb -o new.dtb -v version.dtbo
-where version.dts looks like:: +where version.dtso looks like::
/dts-v1/; /plugin/; diff --git a/doc/usage/fdt_overlays.rst b/doc/usage/fdt_overlays.rst index 7f113edae3..81d0d37f3f 100644 --- a/doc/usage/fdt_overlays.rst +++ b/doc/usage/fdt_overlays.rst @@ -43,7 +43,7 @@ traditional binary device-tree. For example:
$ dtc -@ -I dts -O dtb -o base.dtb base.dts
-**overlay.dts** +**overlay.dtso**
::
@@ -63,7 +63,7 @@ traditional binary device-tree. For example:
.. code-block:: console
- $ dtc -@ -I dts -O dtb -o overlay.dtbo overlay.dts + $ dtc -@ -I dts -O dtb -o overlay.dtbo overlay.dtso
Ways to Utilize Overlays in U-Boot ----------------------------------
On Mon, 25 Sept 2023 at 02:10, Rasmus Villemoes rasmus.villemoes@prevas.dk wrote:
Moving towards using .dtso for overlay sources, update the documentation examples to follow that pattern.
Signed-off-by: Rasmus Villemoes rasmus.villemoes@prevas.dk
doc/develop/uefi/uefi.rst | 4 ++-- doc/usage/fdt_overlays.rst | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-)
Reviewed-by: Simon Glass sjg@chromium.org
On Mon, Sep 25, 2023 at 10:09:09AM +0200, Rasmus Villemoes wrote:
Moving towards using .dtso for overlay sources, update the documentation examples to follow that pattern.
Signed-off-by: Rasmus Villemoes rasmus.villemoes@prevas.dk Reviewed-by: Simon Glass sjg@chromium.org
Applied to u-boot/master, thanks!
participants (4)
-
Jan Kiszka -
Rasmus Villemoes -
Simon Glass -
Tom Rini