arm: dts: k3: binman: Fix DM firmware selection
authorAndrew Davis <afd@ti.com>
Fri, 25 Apr 2025 22:54:03 +0000 (17:54 -0500)
committerTom Rini <trini@konsulko.com>
Fri, 2 May 2025 21:32:45 +0000 (15:32 -0600)
commitc492a55fe40cb9d86b0e99c160e21e5f8f4edcdc
tree0525139c840abf6aa184f1d4e2fd0e81e0f63475
parent78c0f7e3eb0dc96df163cd5ec51de80a28fb31e7
arm: dts: k3: binman: Fix DM firmware selection

Just like TF-A and OP-TEE, the documentation states a custom path for DM
can be provided at build time by setting TI_DM. This should then set
ti-dm-path which updates ti-dm node filenames in binman.

Two issues prevent this from functioning for most K3 boards. One is when
then DM firmware name is inside a blob-ext node instead of a ti-dm node.

The second is when the filename in the ti-dm node is a pointer to a
blob-ext node. In this case even though the filename is updated, the
filename in the blob-ext is not, so build can fail if the default
file in the blob-ext cannot be found, even if the updated ti-dm file
does exist.

Fix both of these for all K3 by removing any indirect ti-dm nodes and
making sure all DM nodes are labeled with "ti-dm".

Signed-off-by: Andrew Davis <afd@ti.com>
Reviewed-by: Bryan Brattlof <bb@ti.com>
Reviewed-by: Neha Malcom Francis <n-francis@ti.com>
17 files changed:
arch/arm/dts/k3-am625-beagleplay-u-boot.dtsi
arch/arm/dts/k3-am625-phycore-som-binman.dtsi
arch/arm/dts/k3-am625-sk-binman.dtsi
arch/arm/dts/k3-am625-verdin-wifi-dev-binman.dtsi
arch/arm/dts/k3-am62a-phycore-som-binman.dtsi
arch/arm/dts/k3-am62a-sk-binman.dtsi
arch/arm/dts/k3-am62p-sk-binman.dtsi
arch/arm/dts/k3-am67a-beagley-ai-u-boot.dtsi
arch/arm/dts/k3-am69-sk-u-boot.dtsi
arch/arm/dts/k3-j7200-binman.dtsi
arch/arm/dts/k3-j721e-beagleboneai64-u-boot.dtsi
arch/arm/dts/k3-j721e-binman.dtsi
arch/arm/dts/k3-j721s2-binman.dtsi
arch/arm/dts/k3-j722s-binman.dtsi
arch/arm/dts/k3-j742s2-evm-u-boot.dtsi
arch/arm/dts/k3-j784s4-binman.dtsi
arch/arm/dts/k3-j784s4-evm-u-boot.dtsi