diff options
author | Randall Spangler <rspangler@chromium.org> | 2014-05-08 15:35:34 -0700 |
---|---|---|
committer | chrome-internal-fetch <chrome-internal-fetch@google.com> | 2014-05-09 04:41:58 +0000 |
commit | 6803674335d88f7ce1b3f61b2b19b88f55464116 (patch) | |
tree | 8b9f0c7504d5109bd5387fb378e2b7e8e3a35982 /power/tegra.c | |
parent | 315631c871c3977b9f109081410f9a6651d55298 (diff) | |
download | chrome-ec-6803674335d88f7ce1b3f61b2b19b88f55464116.tar.gz |
stm32: Re-enable spi transfers after a sysjump
If we sysjump to EC-RW, that sets enabled=0. enabled is only set back
to 1 when the chipset resumes. But on an AP-requested sysjump, the
chipset is already on, and so the resume hook never gets called.
So, in spi init, check if the AP is already on. If it is, enable spi
transfers right away.
This probably also affects Pit/Pi. That may need an additional fix in
power/gaia.c, if it returns an incorrect chipset state after a sysjump
(I didn't test that.)
BUG=chrome-os-partner:28249
BRANCH=nyan,pit
TEST=Power+Refresh boot system with RONormal disabled, so that the AP
tells the EC to jump to EC-RW. Confirm EC communication still works
after that.
Change-Id: I588ef6d841040cf05d5527f645f122d5708b16ad
Signed-off-by: Randall Spangler <rspangler@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/198869
Reviewed-by: Yung-chieh Lo <yjlou@chromium.org>
Reviewed-by: David Hendricks <dhendrix@chromium.org>
Commit-Queue: Yung-chieh Lo <yjlou@chromium.org>
Tested-by: Yung-chieh Lo <yjlou@chromium.org>
Tested-by: Gabe Black <gabeblack@chromium.org>
Diffstat (limited to 'power/tegra.c')
0 files changed, 0 insertions, 0 deletions