Hi Judith,
On 9/11/25 12:45 AM, Judith Mendez wrote:
For all K3 SoC's eMMC boot and MMCSD boot modes are supported. The macros
however, mix MMC device with the two bootmodes. Decouple the two types
of macros so that bootmodes can be identified with:
- BOOT_DEVICE_MMCSD
- BOOT_DEVICE_EMMC
according to devstat parsed boot mode values and on-board devices can be
identified with:
- BOOT_DEVICE_MMC1
- BOOT_DEVICE_MMC2
- BOOT_DEVICE_MMC2_2
according to arbitrary numbers mainly used to differentiate between eMMC
and SD card.
Signed-off-by: Judith Mendez <j...@ti.com>
---
<snip>
+++ b/arch/arm/mach-k3/include/mach/am62_spl.h
@@ -17,7 +17,7 @@
#define BOOT_DEVICE_ETHERNET_RMII 0x05
#define BOOT_DEVICE_I2C 0x06
#define BOOT_DEVICE_UART 0x07
-#define BOOT_DEVICE_MMC 0x08
+#define BOOT_DEVICE_MMCSD 0x08
#define BOOT_DEVICE_EMMC 0x09
#define BOOT_DEVICE_USB 0x2A
@@ -29,16 +29,16 @@
/* U-Boot used aliases */
#define BOOT_DEVICE_ETHERNET 0x04
-#define BOOT_DEVICE_MMC2 0x08
-#define BOOT_DEVICE_MMC1 0x09
+#define BOOT_DEVICE_MMC1 0xFF0
+#define BOOT_DEVICE_MMC2 0xFF1
How did you end up using 0xFF0? Is it simply to make the difference
between modes more clear? It probably does not matter because it is a
u-boot-only representation.
Regards,
Wadim
