env_mmc: support overriding mmc dev from board code

This enables boards to choose where to/from the environment should be
saved/loaded. They can then for example support using the same device
(dynamically) from which the bootloader was launched to load and save
env data and do not have to define CONFIG_SYS_MMC_ENV_DEV statically.

In my use case, the environment needs to be on the same device I
booted from. It can be the eMMC or an optional SD card.
I therefore would override mmc_get_env_dev in the board code, read the
CPU registers to determine where we booted from and return the
corresponding device index.

Cc: Tom Rini <[email protected]>
Cc: Stephen Warren <[email protected]>
Cc: Tim Harvey <[email protected]>
Cc: Simon Glass <[email protected]>
Cc: Hans de Goede <[email protected]>

Signed-off-by: Clemens Gruber <[email protected]>
Reviewed-by: Stephen Warren <[email protected]>
Reviewed-by: Tom Rini <[email protected]>

0 files changed, 0 insertions, 0 deletions