u-boot.git/common/env_mmc.c, branch master

Move environment files from common/ to env/

2017-08-15T12:18:45+00:00

About a quarter of the files in common/ relate to the environment. It
seems better to put these into their own subdirectory and remove the
prefix.

Signed-off-by: Simon Glass 
Reviewed-by: Tom Rini

env: Switch env_nand, env_mmc and env_ubi to env_import_redund

2017-07-22T19:36:17+00:00

The env_nand, env_mmc and env_ubi implementations all implement
redundancy using an identical serial-number scheme. This commit
migrates them to use the implementation in env_common, which is
functionally identical.

Signed-off-by: Fiach Antaw 
Reviewed-by: Tom Rini

dm: mmc: Ensure that block device is probed

2017-06-09T11:25:16+00:00

Make sure that we probe the block device before using it when reading
the environment.

Signed-off-by: Simon Glass 
Reviewed-by: Tom Rini

dm: mmc: Don't re-init when accessing environment

2017-06-01T13:03:04+00:00

With driver model MMC is probed automatically when needed. We should not
re-init MMC each time.

Signed-off-by: Simon Glass

env_mmc: configure environment offsets via device tree

2017-05-29T08:28:52+00:00

This introduces the ability to override the environment offets from the
device tree by setting the following nodes in '/config':
	'u-boot,mmc-env-offset' - overrides CONFIG_ENV_OFFSET
	'u-boot,mmc-env-offset-redundant'
				- overrides CONFIG_ENV_OFFSET_REDUND

To keep with the previous logic, the CONFIG_* defines still need to
be available and the statically defined values become the defaults,
when the corresponding properties are not set in the device-tree.

Signed-off-by: Philipp Tomsich 
Acked-by: Simon Glass

env_mmc: Allow SPL to use any MMC device to load/save the environment

2017-04-08T13:26:44+00:00

SPL has been restricted to use only dev 0 based on the assumption that only
one MMC device is registered. This is not always the case and many
platforms now register several devices as expected by the spl mmc boot code
For those platform SPL_ENV_SUPPORT is broken if dev is forced to 0.

A word of warning: this commit may break SPL_ENV_SUPPORT on platforms that
do not register the same MMC controllers in SPL and in u-boot (mostly iMX6
based platforms). Fortunately none of those activate SPL_ENV_SUPPORT in
their default configuration.

Signed-off-by: Jean-Jacques Hiblot

dm: env: mmc: Convert env_mmc to support CONFIG_BLK

2016-05-27T16:23:08+00:00

Update the MMC environment code so that it works with driver-model enabled
for block devices.

Signed-off-by: Simon Glass

dm: mmc: Use the new select_hwpart() API

2016-05-17T15:54:43+00:00

Avoid calling directly into the MMC code - use the new API call instead.

Signed-off-by: Simon Glass

env_mmc: support overriding mmc dev from board code

2016-01-25T15:39:46+00:00

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 
Cc: Stephen Warren 
Cc: Tim Harvey 
Cc: Simon Glass 
Cc: Hans de Goede 

Signed-off-by: Clemens Gruber 
Reviewed-by: Stephen Warren 
Reviewed-by: Tom Rini

mmc: store hwpart in the block device

2016-01-14T02:05:19+00:00

This will allow us to have multiple block device structs each referring
to the same eMMC device, yet different HW partitions.

For now, there is still a single block device per eMMC device. As before,
this block device always accesses whichever HW partition was most recently
selected. Clients wishing to make use of multiple block devices referring
to different HW partitions can simply take a copy of this block device
once it points at the correct HW partition, and use each one as they wish.
This feature will be used by the next patch.

In the future, perhaps get_device() could be enhanced to return a
dynamically allocated block device struct, to avoid the client needing to
copy it in order to maintain multiple block devices. However, this would
require all users to be updated to free those block device structs at some
point, which is rather a large change.

Most callers of mmc_switch_part() wish to permanently switch the default
MMC block device's HW partition. Enhance mmc_switch_part() so that it does
this. This removes the need for callers to do this. However,
common/env_mmc.c needs to save and restore the current HW partition. Make
it do this more explicitly.

Replace use of mmc_switch_part() with mmc_select_hwpart() in order to
remove duplicate code that skips the call if that HW partition is already
selected.

Signed-off-by: Stephen Warren 
Reviewed-by: Tom Rini