From: Simon Glass <sjg@chromium.org> This should be handled by driver model now. In any case there is nothing special about MMC which indicates that it should be inited and announced at startup. Drop it. Signed-off-by: Simon Glass <sjg@chromium.org> --- common/board_r.c | 12 ------------ 1 file changed, 12 deletions(-) diff --git a/common/board_r.c b/common/board_r.c index de28079a0c5..d60cc7aac70 100644 --- a/common/board_r.c +++ b/common/board_r.c @@ -381,15 +381,6 @@ static int initr_onenand(void) } #endif -#ifdef CONFIG_MMC -static int initr_mmc(void) -{ - puts("MMC: "); - mmc_initialize(gd->bd); - return 0; -} -#endif - #ifdef CONFIG_PVBLOCK static int initr_pvblock(void) { @@ -667,9 +658,6 @@ static void initcall_run_r(void) #if CONFIG_IS_ENABLED(CMD_ONENAND) INITCALL(initr_onenand); #endif -#if CONFIG_IS_ENABLED(MMC) - INITCALL(initr_mmc); -#endif #if CONFIG_IS_ENABLED(XEN) INITCALL(xen_init); #endif -- 2.43.0