summaryrefslogtreecommitdiff
path: root/board/cr50/build.mk
diff options
context:
space:
mode:
authorVadim Bendebury <vbendeb@chromium.org>2016-10-07 11:22:16 -0700
committerchrome-bot <chrome-bot@chromium.org>2016-10-08 01:04:48 -0700
commit36b39b5fc92e4857249372cccec099440ba67c66 (patch)
treec117466aac38d4de1468ed4582159732c0aa4d09 /board/cr50/build.mk
parente19c5ab4672649feef976c3036063610540605db (diff)
downloadchrome-ec-36b39b5fc92e4857249372cccec099440ba67c66.tar.gz
cr50: provide means of posting reboot request
Usually CR50 TPM reset happens when the AP reboots, the CR50 RO does not get a chance to run in this case, so the running RW does not change either, Once the idle RW section was updated, the only way to start it is to reboot the CR50 completely, Rebooting CR50 causes the whole system reset, so it should not be happening at random moments in time. This patch introduces a mechanism to delay reboot to the moment when the TPM is reset. The reboot request would be posted in the end of the update, and then the AP would reboot, triggering a TPM reboot, which in turn would trigger the CR50 reset. The USB update handler now posts the reboot request instead of triggering the reboot immediately. BRANCH=none BUG=chrome-os-partner:58226 TEST=with the rest of the patches applied verified that the system gets reset and the new image version kicks in on both gru (over SPI) and reef (over USB). Change-Id: Iff859f2e7a48c5035a27fffd17aefe7e318af569 Signed-off-by: Vadim Bendebury <vbendeb@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/395627 Reviewed-by: Bill Richardson <wfrichar@chromium.org>
Diffstat (limited to 'board/cr50/build.mk')
0 files changed, 0 insertions, 0 deletions