From 047b23fc31e069c0cb372748e980da194ad59b95 Mon Sep 17 00:00:00 2001 From: Matt DeVillier Date: Sun, 11 Feb 2018 16:07:12 -0600 Subject: ec/chromeec: Fix battery ACPI mutex level Commit 07fe618 [chromeec: Add support for reading second battery info] added a mutex as part of the ACPI code to determine battery statuses. Windows is extremely picky about ACPI code, and attempting to acquire a level 1 mutex without first having acquired a level 0 mutex causes Windows to hang on boot. Since there's no reason to use a level 1 mutex here, change it to level 0. Test: Boot Windows on device with ChromeEC without hanging Change-Id: Icfb0817cfe0c49eb4527a12b507362939a6d32c6 Signed-off-by: Matt DeVillier Reviewed-on: https://review.coreboot.org/23697 Tested-by: build bot (Jenkins) Reviewed-by: Duncan Laurie Reviewed-by: Furquan Shaikh Reviewed-by: Nicolas Boichat Reviewed-by: Paul Menzel --- src/ec/google/chromeec/acpi/battery.asl | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'src/ec/google/chromeec') diff --git a/src/ec/google/chromeec/acpi/battery.asl b/src/ec/google/chromeec/acpi/battery.asl index d8056b03b2..0a0caec279 100644 --- a/src/ec/google/chromeec/acpi/battery.asl +++ b/src/ec/google/chromeec/acpi/battery.asl @@ -17,7 +17,7 @@ // Scope (EC0) /* Mutex for EC battery index interface */ -Mutex (BATM, 1) +Mutex (BATM, 0) // Wait for desired battery index to be presented in shared memory // Arg0 = battery index -- cgit v1.2.3