summaryrefslogtreecommitdiff
path: root/src/soc/intel/broadwell/Kconfig
diff options
context:
space:
mode:
authorDaisuke Nojiri <dnojiri@chromium.org>2015-09-04 14:32:49 -0700
committerPatrick Georgi <pgeorgi@google.com>2015-09-17 14:14:58 +0000
commit914a21ed9ceb403b178c30bedbc354e816b98e92 (patch)
treef66751ebc99bff39dcd026106549db7cd0227e56 /src/soc/intel/broadwell/Kconfig
parent4a69562d01cc4fc716dcf25500d1de2b7ddb3ee5 (diff)
vbnv: check alignment of nvram in advance
Currently, erase operation only works if the region is sector-aligned. These asserts ensure we can erase the region when it's all used up. Erase operation can be updated to handle unaligned erases by read, update, write-back cycle. However, these asserts will still remain useful in case the adjacent region contains critical data and mis-updating it can cause a critical failure. Additionaly we should write a FAFT test but it's more reliable to catch it here since FAFT can fail in many ways. BUG=none BRANCH=master TEST=tested on samus using misaligned nvram region Change-Id: I3add4671ed354d9763e21bf96616c8aeca0cb777 Signed-off-by: Patrick Georgi <pgeorgi@chromium.org> Original-Commit-Id: fc001a4d3446cf96b76367dde492c3453aa948c6 Original-Change-Id: Ib4df8f620bf7531b345364fa4c3e274aba09f677 Original-Signed-off-by: Daisuke Nojiri <dnojiri@chromium.org> Original-Reviewed-on: https://chromium-review.googlesource.com/297801 Reviewed-on: http://review.coreboot.org/11654 Tested-by: build bot (Jenkins) Reviewed-by: Patrick Georgi <pgeorgi@google.com>
Diffstat (limited to 'src/soc/intel/broadwell/Kconfig')
0 files changed, 0 insertions, 0 deletions