diff options
author | Przemyslaw Marczak <p.marczak@samsung.com> | 2015-02-20 12:29:26 +0100 |
---|---|---|
committer | Pantelis Antoniou <pantelis.antoniou@konsulko.com> | 2015-02-23 19:49:22 +0200 |
commit | 64029f7aeec4e843ab99297c24e0ef4f40267a6e (patch) | |
tree | 4252db0ef69115e4e84b7ddd56be4719fab94537 /board/compulab | |
parent | 1f3e877defc5a073f8e93c04e03f9a75f34dd595 (diff) | |
download | u-boot-imx-64029f7aeec4e843ab99297c24e0ef4f40267a6e.zip u-boot-imx-64029f7aeec4e843ab99297c24e0ef4f40267a6e.tar.gz u-boot-imx-64029f7aeec4e843ab99297c24e0ef4f40267a6e.tar.bz2 |
mmc: exynos dwmmc: check boot mode before init dwmmc
Before this commit, the mmc devices were always registered
in the same order. So dwmmc channel 0 was registered as mmc 0,
channel 1 as mmc 1, etc.
In case of possibility to boot from more then one device,
the CONFIG_SYS_MMC_ENV_DEV should always point to right mmc device.
This can be achieved by init boot device as first, so it will be
always registered as mmc 0. Thanks to this, the 'saveenv' command
will work fine for all mmc boot devices.
Exynos based boards usually uses mmc host channels configuration:
- 0, or 0+1 for 8 bit - as a default boot device (usually eMMC)
- 2 for 4bit - as an optional boot device (usually SD card slot)
And usually the boot order is defined by OM pin configuration,
which can be changed in a few ways, eg.
- Odroid U3 - eMMC card insertion -> first boot from eMMC
- Odroid X2/XU3 - boot priority jumper
By this commit, Exynos dwmmc driver will check the OM pin configuration,
and then try to init the boot device and register it as mmc 0.
Signed-off-by: Przemyslaw Marczak <p.marczak@samsung.com>
Cc: Minkyu Kang <mk7.kang@samsung.com>
Cc: Jaehoon Chung <jh80.chung@samsung.com>
Cc: Pantelis Antoniou <panto@antoniou-consulting.com>
Cc: Simon Glass <sjg@chromium.org>
Cc: Akshay Saraswat <akshay.s@samsung.com>
Diffstat (limited to 'board/compulab')
0 files changed, 0 insertions, 0 deletions