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 <matt.devillier@gmail.com>
Reviewed-on: https://review.coreboot.org/23697
Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
Reviewed-by: Duncan Laurie <dlaurie@chromium.org>
Reviewed-by: Furquan Shaikh <furquan@google.com>
Reviewed-by: Nicolas Boichat <drinkcat@chromium.org>
Reviewed-by: Paul Menzel <paulepanter@users.sourceforge.net>
This commit is contained in:
parent
3be35976d6
commit
047b23fc31
|
@ -17,7 +17,7 @@
|
||||||
// Scope (EC0)
|
// Scope (EC0)
|
||||||
|
|
||||||
/* Mutex for EC battery index interface */
|
/* Mutex for EC battery index interface */
|
||||||
Mutex (BATM, 1)
|
Mutex (BATM, 0)
|
||||||
|
|
||||||
// Wait for desired battery index to be presented in shared memory
|
// Wait for desired battery index to be presented in shared memory
|
||||||
// Arg0 = battery index
|
// Arg0 = battery index
|
||||||
|
|
Loading…
Reference in New Issue