Hi Andre,
On Mon, 12 Jul 2021 at 04:07, Andre Przywara andre.przywara@arm.com wrote:
Platforms can overwrite the weak definition of spl_mmc_boot_mode() to determine where to load U-Boot proper from. For most of them this is a trivial decision based on Kconfig variables, but it might be desirable the probe the actual device to answer this question.
Pass the pointer to the mmc struct to that function, so implementations can make use of that.
Compile-tested for all users changed.
Signed-off-by: Andre Przywara andre.przywara@arm.com Reviewed-by: Stefano Babic sbabic@denx.de Reviewed-by: Ley Foon Tan ley.foon.tan@inte.com (for SoCFPGA) Acked-by: Lokesh Vutla lokeshvutla@ti.com (for OMAP and K3)
(resent to also include forgotten U-Boot list)
arch/arm/mach-imx/spl.c | 2 +- arch/arm/mach-k3/am6_init.c | 2 +- arch/arm/mach-k3/j721e_init.c | 2 +- arch/arm/mach-omap2/boot-common.c | 2 +- arch/arm/mach-rockchip/spl.c | 2 +- arch/arm/mach-socfpga/spl_a10.c | 2 +- arch/arm/mach-socfpga/spl_gen5.c | 2 +- arch/arm/mach-stm32mp/spl.c | 2 +- arch/arm/mach-uniphier/mmc-boot-mode.c | 5 +---- common/spl/spl_mmc.c | 4 ++-- include/spl.h | 3 ++- 11 files changed, 13 insertions(+), 15 deletions(-)
Reviewed-by: Simon Glass sjg@chromium.org
But I think this should come from a sysinfo driver.
Regards, Simon