summaryrefslogtreecommitdiff
path: root/test
diff options
context:
space:
mode:
authorShawn Nematbakhsh <shawnn@chromium.org>2016-06-28 15:13:21 -0700
committerchrome-bot <chrome-bot@chromium.org>2016-06-29 21:32:03 -0700
commitf15216344cca5ed7ddc12fc38116ae1a3aa6e4b4 (patch)
tree47f0992d3fcfaecd42dd72ac045090ea71fce195 /test
parent978c4961d605a2da7e79396b1f8db3d543db9059 (diff)
downloadchrome-ec-f15216344cca5ed7ddc12fc38116ae1a3aa6e4b4.tar.gz
npcx: shi: Use worst-case logic for applying 256B bypass
SHI_OBUF_VALID_OFFSET may wrap on buffer full, leaving us with an incorrect tally of bytes transmitted. Always assume the worst case, that SHI_OBUF_VALID_OFFSET is at maximum, when deciding to apply 256B bypass. BUG=chrome-os-partner:54566 BRANCH=None TEST=Manual on gru. Verify 'flashrom -p ec -r read.bin' does not produce CRC errors. Signed-off-by: Shawn Nematbakhsh <shawnn@chromium.org> Change-Id: I7c0ccc1b555838854584a3be8ced50057eaea961 Reviewed-on: https://chromium-review.googlesource.com/356771 Commit-Ready: Shawn N <shawnn@chromium.org> Tested-by: Shelley Chen <shchen@chromium.org> Tested-by: Shawn N <shawnn@chromium.org> Reviewed-by: Randall Spangler <rspangler@chromium.org> Reviewed-by: Mulin Chao <mlchao@nuvoton.com>
Diffstat (limited to 'test')
0 files changed, 0 insertions, 0 deletions