summaryrefslogtreecommitdiff
path: root/util
diff options
context:
space:
mode:
authorDuncan Laurie <dlaurie@chromium.org>2014-01-09 10:10:15 -0800
committerKyösti Mälkki <kyosti.malkki@gmail.com>2014-05-13 21:01:38 +0200
commitb376ea632f1498174d86fa8f8b78848607492055 (patch)
treeedf48e1c9ebfba602eac02c80f6302395d28814d /util
parentdec0148100cb05f5675c4f5127753cd32035930d (diff)
downloadcoreboot-b376ea632f1498174d86fa8f8b78848607492055.tar.xz
baytrail: dptf: Add disable trip point methods
Added a method in each temp sensor to disable the aux trip points and then a wrapper function to call this method for each enabled temperature sensor. The event handler function is changed to not use a switch statement so it does not need to be serialized. This was causing issues with nested locking between the global lock and the EC PATM mutex. Some unused code in temp sensors that was added earlier is removed and instead a critical threshold is specified in _CRT. The top level DPTF device _OSC method is expanded to check for the passive policy UUID and initialize thermal devices. This is done for both enable and disable steps to ensure that the EC thermal thresholds are reset in both cases. Additionally the priority based _TRT is specified with TRTR=1. BUG=chrome-os-partner:17279 BRANCH=rambi TEST=build and boot on rambi, load esif_lf kernel drivers and start esif_uf application. Observe that temperature thresholds are set properly when running 'appstart Dptf' and that they are disabled after running 'appstop Dptf' Change-Id: Ia15824ca42164dadae2011d4e364b70905e36f85 Signed-off-by: Duncan Laurie <dlaurie@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/182024 Reviewed-by: Aaron Durbin <adurbin@chromium.org> Signed-off-by: Aaron Durbin <adurbin@chromium.org> Reviewed-on: http://review.coreboot.org/5037 Tested-by: build bot (Jenkins) Reviewed-by: Kyösti Mälkki <kyosti.malkki@gmail.com>
Diffstat (limited to 'util')
0 files changed, 0 insertions, 0 deletions