[U-Boot] [PATCH 3/4] mmc: exynos dwmmc: check boot mode before init dwmmc
Tom Rini
trini at ti.com
Thu Feb 19 15:01:42 CET 2015
On Tue, Feb 17, 2015 at 10:02:03PM -0700, Simon Glass wrote:
> Hi Przemyslaw,
>
> On 17 February 2015 at 06:09, Przemyslaw Marczak <p.marczak at samsung.com> wrote:
> > 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.
>
> I think a better way to do this would be to make
> CONFIG_SYS_MMC_ENV_DEV support an option where the device can be
> selected at run-time.
>
> However that would probably be better done when the drive rmodel
> conversion is complete.
Yes, lets hold off on this until driver model is in and we can do this
more cleanly rather than whack at this problem right now (I've seen
solutions to this kind of problem on am335x for example and it's still
going to be better to wait I think).
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20150219/7a263834/attachment.sig>
More information about the U-Boot
mailing list