diff options
| author | Marek Vasut <marex@denx.de> | 2021-10-17 20:23:36 +0300 |
|---|---|---|
| committer | Tom Rini <trini@konsulko.com> | 2021-10-25 21:33:13 +0300 |
| commit | d11d1becbd6ab67c4cc0c19bda2886b28c1fdc02 (patch) | |
| tree | 3497f7f60e9295745c916315e402c947974410e8 /env/Kconfig | |
| parent | c6855195e4b4dd07d1ae04d9d98ed999f65b7dc3 (diff) | |
| download | u-boot-d11d1becbd6ab67c4cc0c19bda2886b28c1fdc02.tar.xz | |
env: mmc: Add support for redundant env in both eMMC boot partitions
Currently the MMC environment driver supports storing redundant environment
only in one eMMC partition at different offsets. This is sub-optimal, since
if this one boot partition is erased, both copies of environment are lost.
Since the eMMC has two boot partitions, add support for storing one copy of
environment in each of the two boot partitions.
To enable this functionality, select CONFIG_SYS_REDUNDAND_ENVIRONMENT to
indicate redundant environment should be used. Set CONFIG_SYS_MMC_ENV_PART
to 1 to indicate environment should be stored in eMMC boot partition. Set
CONFIG_ENV_OFFSET equal to CONFIG_ENV_OFFSET_REDUND, and both to the offset
from start of eMMC boot partition where the environment should be located.
Signed-off-by: Marek Vasut <marex@denx.de>
Cc: Fabio Estevam <festevam@gmail.com>
Cc: Jaehoon Chung <jh80.chung@samsung.com>
Cc: Peng Fan <peng.fan@nxp.com>
Cc: Stefano Babic <sbabic@denx.de>
Diffstat (limited to 'env/Kconfig')
| -rw-r--r-- | env/Kconfig | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/env/Kconfig b/env/Kconfig index f75f2b1353..06d72bad1d 100644 --- a/env/Kconfig +++ b/env/Kconfig @@ -200,6 +200,11 @@ config ENV_IS_IN_MMC This value may also be positive or negative; this is handled in the same way as CONFIG_ENV_OFFSET. + In case CONFIG_SYS_MMC_ENV_PART is 1 (i.e. environment in eMMC boot + partition) then setting CONFIG_ENV_OFFSET_REDUND to the same value + as CONFIG_ENV_OFFSET makes use of the second eMMC boot partition for + the redundant environment copy. + This value is also in units of bytes, but must also be aligned to an MMC sector boundary. |