summaryrefslogtreecommitdiff
path: root/util/kconfig
diff options
context:
space:
mode:
authorDuncan Laurie <dlaurie@chromium.org>2013-08-26 08:33:56 -0700
committerPatrick Georgi <patrick@georgi-clan.de>2014-08-04 09:32:20 +0200
commitcc6b924042a0ca1c2d46e05dbb98c15fd2730d47 (patch)
treeaa14281417ee02501a7c7fe320dfd80ad635c2c9 /util/kconfig
parent1f68880e50a2b847838bbdc6916484f9fd86a681 (diff)
downloadcoreboot-cc6b924042a0ca1c2d46e05dbb98c15fd2730d47.tar.xz
falco: Re-read critical temperatures in ACPI _TMP
There seem to be a significant number of shutdowns during suspend resume tests related to critical temperatures. It is possible that we are getting a bad reading from PECI and shutting down prematurely in some cases. If we get a reading that is above critical then wait for the EC to re-poll and then re-check the temperature in case it was just a bad reading. Also add some ACPI debug messages when this happens. Original-Change-Id: I0ab7bdcc50d133981c0f36fc696b06d4a1d939a7 Signed-off-by: Duncan Laurie <dlaurie@chromium.org> Reviewed-on: https://gerrit.chromium.org/gerrit/66937 Reviewed-by: Aaron Durbin <adurbin@chromium.org> (cherry picked from commit a39d7b11dd7b2af37fc2658542d56b32e3966ed4) Signed-off-by: Duncan Laurie <dlaurie@chromium.org> Change-Id: Ib612266511d90749ec6507f8467c71523ee8fb95 Reviewed-on: https://chromium-review.googlesource.com/66939 Tested-by: Duncan Laurie <dlaurie@chromium.org> Reviewed-by: Aaron Durbin <adurbin@chromium.org> Commit-Queue: Duncan Laurie <dlaurie@chromium.org> (cherry picked from commit e98da983dca7819490464bddf08b9c53f28d2712) Signed-off-by: Isaac Christensen <isaac.christensen@se-eng.com> Reviewed-on: http://review.coreboot.org/6457 Tested-by: build bot (Jenkins) Reviewed-by: Edward O'Callaghan <eocallaghan@alterapraxis.com> Reviewed-by: Patrick Georgi <patrick@georgi-clan.de> Reviewed-by: Paul Menzel <paulepanter@users.sourceforge.net>
Diffstat (limited to 'util/kconfig')
0 files changed, 0 insertions, 0 deletions