tree 7ab6b1df62c1b5c9483aa3a1a6ef4f7f70a4d2a5
parent 462a3cadc717201345bd8f74cb7018cd4e60c3e5
author Randall Spangler <rspangler@chromium.org> 1379701088 -0700
committer chrome-internal-fetch <chrome-internal-fetch@google.com> 1392395261 +0000

Fix jumping EC from RO to RW if disable-jump was called on previous boot

It's possible for the AP to get updated and remove the RO-normal flag
without needing to update EC-RW firmware - for example, if it only
needs to update the BIOS.  In this case, the EC doesn't need update,
but does need to jump to its RW firmware.  But if the EC is already
booted RO-normal with jump disabled, it will refuse that request and
go to recovery mode.

The fix is simply to check if the request to jump to RW requires the
EC to cold-boot first, and pass through that error code to the caller.

BUG=chrome-os-partner:22617
BRANCH=none (affects all platforms, but only in this odd case, and this
       is a change to the RW portion of the code)
TEST=pass new unit test which triggers this condition

Orig-Change-Id: Ia8d64dff784a9135ef23f6eb26bbca4ad9df57c3
Signed-off-by: Randall Spangler <rspangler@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/170168
Reviewed-by: Vadim Bendebury <vbendeb@chromium.org>
(cherry picked from commit bbc76063294f4b9fcca6b581d9831595d840a1a3)

Change-Id: Ib4f3ca230d7247b28e639fcd3434445b7d5a7530
Reviewed-on: https://chromium-review.googlesource.com/185962
Commit-Queue: Randall Spangler <rspangler@chromium.org>
Tested-by: Randall Spangler <rspangler@chromium.org>
Reviewed-by: Vadim Bendebury <vbendeb@chromium.org>