diff options
author | Furquan Shaikh <furquan@chromium.org> | 2016-11-14 13:49:56 -0800 |
---|---|---|
committer | Furquan Shaikh <furquan@google.com> | 2016-11-15 22:21:07 +0100 |
commit | 0530b299212b4d584571ab588ad1d750ae57e251 (patch) | |
tree | 8a350ed7792b5ffb4a319a98a4483286074ac725 /.gitreview | |
parent | a2f1d1892144b5e7b62055b1387553d839ad6ee8 (diff) | |
download | coreboot-0530b299212b4d584571ab588ad1d750ae57e251.tar.xz |
intel/apollolake: Ensure SPI operations do not cross 256-byte boundary
BIOS needs to ensure that SPI write does not cross 256-byte
boundary. Else, if the write is across 256-byte boundary, then it
corrupts the block by wrapping write to start of current block. Thus,
ensure nuclear_spi_{read,write} operate within a single 256-byte block
only at a time.
BUG=chrome-os-partner:59813
BRANCH=None
TEST=Verified that elog writes do not corrupt the event log when write
is across 256-byte blocks.
Change-Id: I854ca2979d65b9f1232f93182cb84d4dee4f4139
Signed-off-by: Furquan Shaikh <furquan@chromium.org>
Reviewed-on: https://review.coreboot.org/17419
Tested-by: build bot (Jenkins)
Reviewed-by: Aaron Durbin <adurbin@chromium.org>
Diffstat (limited to '.gitreview')
0 files changed, 0 insertions, 0 deletions