arm64: dts: mediatek: Apply all DT overlays at build time

It's a requirement that DT overlays be applied at build time in order to validate them as overlays are not validated on their own.

Add targets for all the Mediatek overlays.

Signed-off-by Rob Herring (Arm) <[email protected]>

---
This will soon be a warning[1].

Note that if it is desired that the combined .dtb is not installed, then the combined .dtb should be added to 'dtb-' variable instead.

[1] https://lore.kernel.org/all/[email protected]/

---
  arch/arm64/boot/dts/mediatek/Makefile | 16 ++++++++++++++++
  1 file changed, 16 insertions(+)

arch/arm64/boot/dts/mediatek/Makefile +16 -0

index a4df4c21399e..4e92bd9f0e53 100644
@@ -15,16 +15,30 @@ dtb-$(CONFIG_ARCH_MEDIATEK) += mt7986a-acelink-ew-7886cax.dtb
  dtb-$(CONFIG_ARCH_MEDIATEK) += mt7986a-bananapi-bpi-r3.dtb
  dtb-$(CONFIG_ARCH_MEDIATEK) += mt7986a-bananapi-bpi-r3-mini.dtb
  dtb-$(CONFIG_ARCH_MEDIATEK) += mt7986a-bananapi-bpi-r3-emmc.dtbo
+mt7986a-bananapi-bpi-r3-emmc-dtbs := mt7986a-bananapi-bpi-r3.dtb mt7986a-bananapi-bpi-r3-emmc.dtbo
+dtb-$(CONFIG_ARCH_MEDIATEK) += mt7986a-bananapi-bpi-r3-emmc.dtb
  dtb-$(CONFIG_ARCH_MEDIATEK) += mt7986a-bananapi-bpi-r3-nand.dtbo
+mt7986a-bananapi-bpi-r3-nand-dtbs := mt7986a-bananapi-bpi-r3.dtb mt7986a-bananapi-bpi-r3-nand.dtbo
+dtb-$(CONFIG_ARCH_MEDIATEK) += mt7986a-bananapi-bpi-r3-nand.dtb
  dtb-$(CONFIG_ARCH_MEDIATEK) += mt7986a-bananapi-bpi-r3-nor.dtbo
+mt7986a-bananapi-bpi-r3-nor-dtbs := mt7986a-bananapi-bpi-r3.dtb mt7986a-bananapi-bpi-r3-nor.dtbo
+dtb-$(CONFIG_ARCH_MEDIATEK) += mt7986a-bananapi-bpi-r3-nor.dtb
  dtb-$(CONFIG_ARCH_MEDIATEK) += mt7986a-bananapi-bpi-r3-sata.dtbo
+mt7986a-bananapi-bpi-r3-sata-dtbs := mt7986a-bananapi-bpi-r3.dtb mt7986a-bananapi-bpi-r3-sata.dtbo
+dtb-$(CONFIG_ARCH_MEDIATEK) += mt7986a-bananapi-bpi-r3-sata.dtb
  dtb-$(CONFIG_ARCH_MEDIATEK) += mt7986a-bananapi-bpi-r3-sd.dtbo
+mt7986a-bananapi-bpi-r3-sd-dtbs := mt7986a-bananapi-bpi-r3.dtb mt7986a-bananapi-bpi-r3-sd.dtbo
+dtb-$(CONFIG_ARCH_MEDIATEK) += mt7986a-bananapi-bpi-r3-sd.dtb
  dtb-$(CONFIG_ARCH_MEDIATEK) += mt7986a-rfb.dtb
  dtb-$(CONFIG_ARCH_MEDIATEK) += mt7986b-rfb.dtb
  dtb-$(CONFIG_ARCH_MEDIATEK) += mt7988a-bananapi-bpi-r4.dtb
  dtb-$(CONFIG_ARCH_MEDIATEK) += mt7988a-bananapi-bpi-r4-2g5.dtb
  dtb-$(CONFIG_ARCH_MEDIATEK) += mt7988a-bananapi-bpi-r4-emmc.dtbo
+mt7988a-bananapi-bpi-r4-emmc-dtbs := mt7988a-bananapi-bpi-r4.dtb mt7988a-bananapi-bpi-r4-emmc.dtbo
+dtb-$(CONFIG_ARCH_MEDIATEK) += mt7988a-bananapi-bpi-r4-emmc.dtb
  dtb-$(CONFIG_ARCH_MEDIATEK) += mt7988a-bananapi-bpi-r4-sd.dtbo
+mt7988a-bananapi-bpi-r4-sd-dtbs := mt7988a-bananapi-bpi-r4.dtb mt7988a-bananapi-bpi-r4-sd.dtbo
+dtb-$(CONFIG_ARCH_MEDIATEK) += mt7988a-bananapi-bpi-r4-sd.dtb
  dtb-$(CONFIG_ARCH_MEDIATEK) += mt8167-pumpkin.dtb
  dtb-$(CONFIG_ARCH_MEDIATEK) += mt8173-elm.dtb
  dtb-$(CONFIG_ARCH_MEDIATEK) += mt8173-elm-hana.dtb

@@ -104,6 +118,8 @@ dtb-$(CONFIG_ARCH_MEDIATEK) += mt8390-genio-700-evk.dtb
  dtb-$(CONFIG_ARCH_MEDIATEK) += mt8395-kontron-3-5-sbc-i1200.dtb
  dtb-$(CONFIG_ARCH_MEDIATEK) += mt8395-radxa-nio-12l.dtb
  dtb-$(CONFIG_ARCH_MEDIATEK) += mt8395-radxa-nio-12l-8-hd-panel.dtbo
+mt8395-radxa-nio-12l-8-hd-panel-dtbs := mt8395-radxa-nio-12l.dtb mt8395-radxa-nio-12l-8-hd-panel.dtbo
+dtb-$(CONFIG_ARCH_MEDIATEK) += mt8395-radxa-nio-12l-8-hd-panel.dtb
  dtb-$(CONFIG_ARCH_MEDIATEK) += mt8516-pumpkin.dtb
 
  # Device tree overlays support

Il 17/11/25 22:13, Rob Herring (Arm) ha scritto:

Quoted 12 lines

It's a requirement that DT overlays be applied at build time in order to validate them as overlays are not validated on their own.

Add targets for all the Mediatek overlays.

Signed-off-by Rob Herring (Arm) <[email protected]>

---
This will soon be a warning[1].

Note that if it is desired that the combined .dtb is not installed, then the combined .dtb should be added to 'dtb-' variable instead.

Uhm, sorry, can't we do something such that we don't generate a DTB with a preapplied overlay?

Even something like generating those and deleting before build finalization could work, I guess, though that'd be hacky maybe.

I don't know if this is the case, but I'm worried that various people have scripts to copy DTBs somewhere (in some partition) or embed those in images, and if they get the preapplied overlay dtbs in the same place, havoc could happen as the bootloaders might be selecting wrong dtbs (as a plus, there is no dtbo that varies machine compatible strings, rightfully).

Cheers,
Angelo

Quoted 49 lines

[1] https://lore.kernel.org/all/[email protected]/

---
  arch/arm64/boot/dts/mediatek/Makefile | 16 ++++++++++++++++
  1 file changed, 16 insertions(+)

arch/arm64/boot/dts/mediatek/Makefile +16 -0

index a4df4c21399e..4e92bd9f0e53 100644
@@ -15,16 +15,30 @@ dtb-$(CONFIG_ARCH_MEDIATEK) += mt7986a-acelink-ew-7886cax.dtb
  dtb-$(CONFIG_ARCH_MEDIATEK) += mt7986a-bananapi-bpi-r3.dtb
  dtb-$(CONFIG_ARCH_MEDIATEK) += mt7986a-bananapi-bpi-r3-mini.dtb
  dtb-$(CONFIG_ARCH_MEDIATEK) += mt7986a-bananapi-bpi-r3-emmc.dtbo
+mt7986a-bananapi-bpi-r3-emmc-dtbs := mt7986a-bananapi-bpi-r3.dtb mt7986a-bananapi-bpi-r3-emmc.dtbo
+dtb-$(CONFIG_ARCH_MEDIATEK) += mt7986a-bananapi-bpi-r3-emmc.dtb
  dtb-$(CONFIG_ARCH_MEDIATEK) += mt7986a-bananapi-bpi-r3-nand.dtbo
+mt7986a-bananapi-bpi-r3-nand-dtbs := mt7986a-bananapi-bpi-r3.dtb mt7986a-bananapi-bpi-r3-nand.dtbo
+dtb-$(CONFIG_ARCH_MEDIATEK) += mt7986a-bananapi-bpi-r3-nand.dtb
  dtb-$(CONFIG_ARCH_MEDIATEK) += mt7986a-bananapi-bpi-r3-nor.dtbo
+mt7986a-bananapi-bpi-r3-nor-dtbs := mt7986a-bananapi-bpi-r3.dtb mt7986a-bananapi-bpi-r3-nor.dtbo
+dtb-$(CONFIG_ARCH_MEDIATEK) += mt7986a-bananapi-bpi-r3-nor.dtb
  dtb-$(CONFIG_ARCH_MEDIATEK) += mt7986a-bananapi-bpi-r3-sata.dtbo
+mt7986a-bananapi-bpi-r3-sata-dtbs := mt7986a-bananapi-bpi-r3.dtb mt7986a-bananapi-bpi-r3-sata.dtbo
+dtb-$(CONFIG_ARCH_MEDIATEK) += mt7986a-bananapi-bpi-r3-sata.dtb
  dtb-$(CONFIG_ARCH_MEDIATEK) += mt7986a-bananapi-bpi-r3-sd.dtbo
+mt7986a-bananapi-bpi-r3-sd-dtbs := mt7986a-bananapi-bpi-r3.dtb mt7986a-bananapi-bpi-r3-sd.dtbo
+dtb-$(CONFIG_ARCH_MEDIATEK) += mt7986a-bananapi-bpi-r3-sd.dtb
  dtb-$(CONFIG_ARCH_MEDIATEK) += mt7986a-rfb.dtb
  dtb-$(CONFIG_ARCH_MEDIATEK) += mt7986b-rfb.dtb
  dtb-$(CONFIG_ARCH_MEDIATEK) += mt7988a-bananapi-bpi-r4.dtb
  dtb-$(CONFIG_ARCH_MEDIATEK) += mt7988a-bananapi-bpi-r4-2g5.dtb
  dtb-$(CONFIG_ARCH_MEDIATEK) += mt7988a-bananapi-bpi-r4-emmc.dtbo
+mt7988a-bananapi-bpi-r4-emmc-dtbs := mt7988a-bananapi-bpi-r4.dtb mt7988a-bananapi-bpi-r4-emmc.dtbo
+dtb-$(CONFIG_ARCH_MEDIATEK) += mt7988a-bananapi-bpi-r4-emmc.dtb
  dtb-$(CONFIG_ARCH_MEDIATEK) += mt7988a-bananapi-bpi-r4-sd.dtbo
+mt7988a-bananapi-bpi-r4-sd-dtbs := mt7988a-bananapi-bpi-r4.dtb mt7988a-bananapi-bpi-r4-sd.dtbo
+dtb-$(CONFIG_ARCH_MEDIATEK) += mt7988a-bananapi-bpi-r4-sd.dtb
  dtb-$(CONFIG_ARCH_MEDIATEK) += mt8167-pumpkin.dtb
  dtb-$(CONFIG_ARCH_MEDIATEK) += mt8173-elm.dtb
  dtb-$(CONFIG_ARCH_MEDIATEK) += mt8173-elm-hana.dtb

@@ -104,6 +118,8 @@ dtb-$(CONFIG_ARCH_MEDIATEK) += mt8390-genio-700-evk.dtb
  dtb-$(CONFIG_ARCH_MEDIATEK) += mt8395-kontron-3-5-sbc-i1200.dtb
  dtb-$(CONFIG_ARCH_MEDIATEK) += mt8395-radxa-nio-12l.dtb
  dtb-$(CONFIG_ARCH_MEDIATEK) += mt8395-radxa-nio-12l-8-hd-panel.dtbo
+mt8395-radxa-nio-12l-8-hd-panel-dtbs := mt8395-radxa-nio-12l.dtb mt8395-radxa-nio-12l-8-hd-panel.dtbo
+dtb-$(CONFIG_ARCH_MEDIATEK) += mt8395-radxa-nio-12l-8-hd-panel.dtb
  dtb-$(CONFIG_ARCH_MEDIATEK) += mt8516-pumpkin.dtb
 
  # Device tree overlays support

Il 17/11/25 22:13, Rob Herring (Arm) ha scritto:

Quoted 12 lines

It's a requirement that DT overlays be applied at build time in order to validate them as overlays are not validated on their own.

Add targets for all the Mediatek overlays.

Signed-off-by Rob Herring (Arm) <[email protected]>

---
This will soon be a warning[1].

Note that if it is desired that the combined .dtb is not installed, then the combined .dtb should be added to 'dtb-' variable instead.

Uhm, sorry, can't we do something such that we don't generate a DTB with a preapplied overlay?

Even something like generating those and deleting before build finalization could work, I guess, though that'd be hacky maybe.

I don't know if this is the case, but I'm worried that various people have scripts to copy DTBs somewhere (in some partition) or embed those in images, and if they get the preapplied overlay dtbs in the same place, havoc could happen as the bootloaders might be selecting wrong dtbs (as a plus, there is no dtbo that varies machine compatible strings, rightfully).

Gesendet: Dienstag, 18. November 2025 um 13:31
Von: "Rob Herring" <[email protected]>
An: "AngeloGioacchino Del Regno" <[email protected]>
CC: "Matthias Brugger" <[email protected]>, "Krzysztof Kozlowski" <[email protected]>, "Conor Dooley" <[email protected]>, [email protected], [email protected], [email protected], [email protected]
Betreff: Re: [PATCH] arm64: dts: mediatek: Apply all DT overlays at build time

Quoted 18 lines · AngeloGioacchino Del Regno

Il 17/11/25 22:13, Rob Herring (Arm) ha scritto:

Quoted 12 lines

It's a requirement that DT overlays be applied at build time in order to validate them as overlays are not validated on their own.

Add targets for all the Mediatek overlays.

Signed-off-by Rob Herring (Arm) <[email protected]>

---
This will soon be a warning[1].

Note that if it is desired that the combined .dtb is not installed, then the combined .dtb should be added to 'dtb-' variable instead.

Uhm, sorry, can't we do something such that we don't generate a DTB with a preapplied overlay?

Quoted 8 lines

Even something like generating those and deleting before build finalization could work, I guess, though that'd be hacky maybe.

I don't know if this is the case, but I'm worried that various people have scripts to copy DTBs somewhere (in some partition) or embed those in images, and if they get the preapplied overlay dtbs in the same place, havoc could happen as the bootloaders might be selecting wrong dtbs (as a plus, there is no dtbo that varies machine compatible strings, rightfully).

If they aren't using dtbs_install for that, then that is their problem. When we moved all the arm32 DTs to vendor directories, dtbs_install maintained the old structure which seemed sufficient to not break folks. The same should apply here.

Rob

Hi,

this looks similar to my attempt i did here

https://patchwork.kernel.org/project/linux-mediatek/patch/[email protected]/

But in my case i added full dtb with 2 overlays as there can be 2 devices (1 mmc + 1 spi) at one time. So usable as dtb for bootloader config without overlays, not only for validation...

regards Frank

Quoted 43 lines

Gesendet: Dienstag, 18. November 2025 um 13:31
Von: "Rob Herring" <[email protected]>
An: "AngeloGioacchino Del Regno" <[email protected]>
CC: "Matthias Brugger" <[email protected]>, "Krzysztof Kozlowski" <[email protected]>, "Conor Dooley" <[email protected]>, [email protected], [email protected], [email protected], [email protected]
Betreff: Re: [PATCH] arm64: dts: mediatek: Apply all DT overlays at build time

Quoted 18 lines · AngeloGioacchino Del Regno

Il 17/11/25 22:13, Rob Herring (Arm) ha scritto:

Quoted 12 lines

It's a requirement that DT overlays be applied at build time in order to validate them as overlays are not validated on their own.

Add targets for all the Mediatek overlays.

Signed-off-by Rob Herring (Arm) <[email protected]>

---
This will soon be a warning[1].

Note that if it is desired that the combined .dtb is not installed, then the combined .dtb should be added to 'dtb-' variable instead.

Uhm, sorry, can't we do something such that we don't generate a DTB with a preapplied overlay?

Quoted 8 lines

Even something like generating those and deleting before build finalization could work, I guess, though that'd be hacky maybe.

I don't know if this is the case, but I'm worried that various people have scripts to copy DTBs somewhere (in some partition) or embed those in images, and if they get the preapplied overlay dtbs in the same place, havoc could happen as the bootloaders might be selecting wrong dtbs (as a plus, there is no dtbo that varies machine compatible strings, rightfully).

If they aren't using dtbs_install for that, then that is their problem. When we moved all the arm32 DTs to vendor directories, dtbs_install maintained the old structure which seemed sufficient to not break folks. The same should apply here.

Rob

Il 18/11/25 18:02, Frank Wunderlich ha scritto:

Quoted 4 lines

Hi,

this looks similar to my attempt i did here

Quoted 5 lines

https://patchwork.kernel.org/project/linux-mediatek/patch/[email protected]/

But in my case i added full dtb with 2 overlays as there can be 2 devices (1 mmc + 1 spi) at one time. So usable as dtb for bootloader config without overlays, not only for validation...

Please don't top post :-)

That said, for the target of what is done here, I think yours is nicer to the eye compared to Rob's (not his fault at all, most of the times overlays cannot be applied together, he can't possibly know if that is possible in this case).

If there is really no other solution to that... well, at this point I prefer to have something nicer to the eye, with all of the necessary "evil" that comes with it.

P.S.: Strong words contained in this reply are meant to be lighter than they appear

Cheers,
Angelo

Am 19. November 2025 09:39:07 MEZ schrieb AngeloGioacchino Del Regno <[email protected]>:

Quoted 7 lines

Il 18/11/25 18:02, Frank Wunderlich ha scritto:

Quoted 6 lines

Hi,

this looks similar to my attempt i did here

https://patchwork.kernel.org/project/linux-mediatek/patch/[email protected]/

Quoted 5 lines

Quoted 3 lines

But in my case i added full dtb with 2 overlays as there can be 2 devices (1 mmc + 1 spi) at one time. So usable as dtb for bootloader config without overlays, not only for validation...

Please don't top post :-)

Sorry for that :(

Quoted 7 lines

That said, for the target of what is done here, I think yours is nicer to the eye compared to Rob's (not his fault at all, most of the times overlays cannot be applied together, he can't possibly know if that is possible in this case).

If there is really no other solution to that... well, at this point I prefer to have something nicer to the eye, with all of the necessary "evil" that comes with it.

If my version is ok for rob (afair he did not replied on that yet),i would resend it again with similar for R4 and R4Pro.