From: Michal Simek <michal.simek@amd.com>
Date: Tue, 23 Jun 2026 12:53:42 +0000 (+0200)
Subject: arm64: versal-net: Look up eMMC device in boot_targets_setup()
X-Git-Url: http://git.ipfire.org/gitweb/?a=commitdiff_plain;h=d18ebbf33950d33d2292bd26b597493b66a2a991;p=thirdparty%2Fu-boot.git

arm64: versal-net: Look up eMMC device in boot_targets_setup()

The EMMC_MODE case set bootseq from dev_seq(dev) without ever assigning
dev, so it used an uninitialized pointer and produced a bogus device
sequence in boot_targets.

eMMC is wired to the SD1 controller (mmc@f1050000, see
versal-net-mini-emmc.dts). Look that device up like the SD cases do
before using its sequence number.

Signed-off-by: Michal Simek <michal.simek@amd.com>
Link: https://patch.msgid.link/bf779dcdd30c900d7614c0fa8382cb3f4cb57c20.1782219202.git.michal.simek@amd.com
---

diff --git a/board/xilinx/versal-net/board.c b/board/xilinx/versal-net/board.c
index 687d042d106..9c0490cba98 100644
--- a/board/xilinx/versal-net/board.c
+++ b/board/xilinx/versal-net/board.c
@@ -145,6 +145,11 @@ static int boot_targets_setup(void)
 		break;
 	case EMMC_MODE:
 		puts("EMMC_MODE\n");
+		if (uclass_get_device_by_name(UCLASS_MMC,
+					      "mmc@f1050000", &dev)) {
+			debug("eMMC driver for eMMC device is not present\n");
+			break;
+		}
 		mode = "mmc";
 		bootseq = dev_seq(dev);
 		break;