diff options
author | Diego Santa Cruz <Diego.SantaCruz@spinetix.com> | 2014-12-23 10:50:27 +0100 |
---|---|---|
committer | Pantelis Antoniou <pantelis.antoniou@konsulko.com> | 2015-01-19 17:04:48 +0200 |
commit | 8a0cf4901021b09c283f172d4d29d0d05721b0ba (patch) | |
tree | 7ca5956ce0f1187a02c3ae99ad940e65f40ac221 /drivers/mmc/rpmb.c | |
parent | b0361526d5dc3b09d16fbb8f36fbf999cc064640 (diff) | |
download | u-boot-imx-8a0cf4901021b09c283f172d4d29d0d05721b0ba.zip u-boot-imx-8a0cf4901021b09c283f172d4d29d0d05721b0ba.tar.gz u-boot-imx-8a0cf4901021b09c283f172d4d29d0d05721b0ba.tar.bz2 |
mmc: eMMC partitioning data is not effective till partitioning completed
The eMMC spec says that partitioning is only effective after the
PARTITION_SETTING_COMPLETED is set in EXT_CSD (and a power cycle was done,
but that we cannot know). Thus the partition sizes and attributes should
be ignored when that bit is not set, otherwise the various capacities
are not coherent (e.g., the user data capacity will be that of the
unpartitioned device while partition sizes would be non-zero).
Prescence of non-zero partitioning data is nevertheless still used to
activate the high-capacity size definitions (EXT_CSD_ERASE_GROUP_DEF)
as it is necessary to set that to write any of the partitioning fields
in EXT_CSD, so having partitioning data means someone previously
activated that and we should keep it activated.
Signed-off-by: Diego Santa Cruz <Diego.SantaCruz@spinetix.com>
Diffstat (limited to 'drivers/mmc/rpmb.c')
0 files changed, 0 insertions, 0 deletions