summaryrefslogtreecommitdiff
path: root/common/host_command.c
diff options
context:
space:
mode:
authorShawn Nematbakhsh <shawnn@chromium.org>2015-03-23 18:27:22 -0700
committerChromeOS Commit Bot <chromeos-commit-bot@chromium.org>2015-03-25 20:09:52 +0000
commit6ee7b1e34eecd585074b4aae0347ed12f632ead0 (patch)
treeace73f958495a83b836505941318325fa71c71e7 /common/host_command.c
parent0f18989ef58a77800c1b393cf8223455f793d543 (diff)
downloadchrome-ec-6ee7b1e34eecd585074b4aae0347ed12f632ead0.tar.gz
ACPI: Support accessing memmap data over ACPI CMD / DATA portsstabilize-6915.B
Some platforms are unable to access the 900h-9ffh region over LPC and must instead access memmap data through the ACPI CMD / DATA ports. To avoid racing with data updates, disallow changes to multi-byte memmap data while in burst mode. Linux currently enables burst mode when accessing multi-byte data and disables it immediately afterward, though the ACPI spec defines burst mode in a more general way. BUG=chrome-os-partner:38224 TEST=Manual on Samus. Undefine LPC_MEMMAP and modify asl to move memmap data to ERAM at offset 0x20. Verify system boots cleanly and battery status is updated immediately on plug / unplug. BRANCH=None Change-Id: Ib848bdb491fdfece96ad0cee7a44ba85b4a1a50b Signed-off-by: Shawn Nematbakhsh <shawnn@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/262072 Reviewed-by: Randall Spangler <rspangler@chromium.org> Reviewed-by: Duncan Laurie <dlaurie@chromium.org>
Diffstat (limited to 'common/host_command.c')
-rw-r--r--common/host_command.c12
1 files changed, 12 insertions, 0 deletions
diff --git a/common/host_command.c b/common/host_command.c
index 51d1a9cf97..0a6226b59e 100644
--- a/common/host_command.c
+++ b/common/host_command.c
@@ -81,6 +81,18 @@ uint8_t *host_get_memmap(int offset)
#endif
}
+static struct mutex memmap_write_mutex;
+
+void host_lock_memmap()
+{
+ mutex_lock(&memmap_write_mutex);
+}
+
+void host_unlock_memmap()
+{
+ mutex_unlock(&memmap_write_mutex);
+}
+
int host_get_vboot_mode(void)
{
return g_vboot_mode;