summaryrefslogtreecommitdiff
path: root/power
diff options
context:
space:
mode:
authorFurquan Shaikh <furquan@chromium.org>2017-02-17 10:36:23 -0800
committerchrome-bot <chrome-bot@chromium.org>2017-02-18 03:11:00 -0800
commitbb184acdccff14a526b67eed9a8eae9dfb7431b6 (patch)
tree0f253f8e7af11cd81e6a78718ae1a371446c883e /power
parent38188d322ea6949e26f1309f5be5e41fa8261cf8 (diff)
downloadchrome-ec-bb184acdccff14a526b67eed9a8eae9dfb7431b6.tar.gz
power/skylake: Use power_get_signals instead of power_has_signals
In chipset_handle_espi_reset_assert, check the state of SLP_SUS# signal using power_get_signals instead of power_has_signals since we do not care if the check fails. This avoids unwanted "power lost input" prints on the EC console. BUG=chrome-os-partner:63033 BRANCH=None TEST=Verified that entry into S3 does not result in any "power lost input" messages on EC console. Change-Id: I88bc76a90b48e7c565423235f6e8431176ed4872 Signed-off-by: Furquan Shaikh <furquan@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/444262 Reviewed-by: Aaron Durbin <adurbin@chromium.org>
Diffstat (limited to 'power')
-rw-r--r--power/skylake.c3
1 files changed, 2 insertions, 1 deletions
diff --git a/power/skylake.c b/power/skylake.c
index 02db88a79a..505c7439a8 100644
--- a/power/skylake.c
+++ b/power/skylake.c
@@ -100,7 +100,8 @@ void chipset_handle_espi_reset_assert(void)
* event). In this case, check if shutdown was being forced by pressing
* power button. If yes, release power button.
*/
- if (power_has_signals(IN_PCH_SLP_SUS_DEASSERTED) && forcing_shutdown) {
+ if ((power_get_signals() & IN_PCH_SLP_SUS_DEASSERTED) &&
+ forcing_shutdown) {
power_button_pch_release();
forcing_shutdown = 0;
}