diff options
author | Aaron Durbin <adurbin@chromium.org> | 2013-10-04 11:11:52 -0500 |
---|---|---|
committer | Aaron Durbin <adurbin@google.com> | 2014-02-05 05:24:03 +0100 |
commit | fd039f7f4d84b1c04dba81874068f8ea94620f87 (patch) | |
tree | 3ec3629760d53a10a4f9977907e646d190147d5a /util/msrtool/README | |
parent | a64ef62ca4da18f0b6c8f6949c659c81fb68c418 (diff) |
baytrail: disable tco timer
The TCO timer always starts ticking out of reset.
However, depending on microcode loading and punit
initialization the TCO timing out has a different
impact on the sytem. Without loading microcode
or initializing the punit the tco times out and
nothing happens. However, when microcode is loaded
a timeout will reset the system. Lastly, if the
punit is initialized but the microcode isn't loaded
the TCO timeout will shut down the system.
To fix all the weird symptoms disable the TCO.
BUG=chrome-os-partner:22858
BRANCH=None
TEST=Built and booted with microcode loading. Reset doesn't
occur.
Change-Id: I49cd62f510726a96bf734ae728a352c671d1561e
Signed-off-by: Aaron Durbin <adurbin@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/171860
Reviewed-by: Shawn Nematbakhsh <shawnn@chromium.org>
Reviewed-on: http://review.coreboot.org/4862
Tested-by: build bot (Jenkins)
Reviewed-by: Stefan Reinauer <stefan.reinauer@coreboot.org>
Diffstat (limited to 'util/msrtool/README')
0 files changed, 0 insertions, 0 deletions