summaryrefslogtreecommitdiff
path: root/board/amazon
diff options
context:
space:
mode:
authorJean-Jacques Hiblot <jjhiblot@ti.com>2017-02-01 10:39:14 (GMT)
committerTom Rini <trini@konsulko.com>2017-03-20 02:17:14 (GMT)
commitd5abcf94c7123167725fc22ace342f0d455093c1 (patch)
treeca1d964a4d7d798c498a3b6b409c3d68dad4a7da /board/amazon
parent02ccab1908c405fe1449457d4a0d343784a30acb (diff)
downloadu-boot-d5abcf94c7123167725fc22ace342f0d455093c1.tar.xz
ti: boot: Register the MMC controllers in SPL in the same way as in u-boot
To keep a consistent MMC device mapping in SPL and in u-boot, let's register the MMC controllers the same way in u-boot and in the SPL. In terms of boot time, it doesn't hurt to register more controllers than needed because the MMC device is initialized only prior being accessed for the first time. Having the same device mapping in SPL and u-boot allows us to use the environment in SPL whatever the MMC boot device. Signed-off-by: Jean-Jacques Hiblot <jjhiblot@ti.com>
Diffstat (limited to 'board/amazon')
-rw-r--r--board/amazon/kc1/kc1.c2
1 files changed, 0 insertions, 2 deletions
diff --git a/board/amazon/kc1/kc1.c b/board/amazon/kc1/kc1.c
index 469a83e..b3fa789 100644
--- a/board/amazon/kc1/kc1.c
+++ b/board/amazon/kc1/kc1.c
@@ -166,12 +166,10 @@ int fb_set_reboot_flag(void)
return omap_reboot_mode_store("b");
}
-#ifndef CONFIG_SPL_BUILD
int board_mmc_init(bd_t *bis)
{
return omap_mmc_init(1, 0, 0, -1, -1);
}
-#endif
void board_mmc_power_init(void)
{