summaryrefslogtreecommitdiff
path: root/src/device/gpio.c
diff options
context:
space:
mode:
authorPeter Marheine <pmarheine@chromium.org>2024-05-31 09:34:38 +1000
committerFelix Held <felix-coreboot@felixheld.de>2024-07-08 13:01:39 +0000
commitb97ec4f0166b1b878d8d9a8d2bd82f6f0a47407c (patch)
tree2f71107db92a9aa292afe491d7d033a8087cfed1 /src/device/gpio.c
parent4a8d73d6a4af625f97af908911478d481b95b461 (diff)
chromeec: support reading long battery strings
The Chrome EC currently supports two ways to read battery strings on ACPI platforms: * Read up to 8 bytes from EC shared memory BMFG, BMOD, ... * Send a EC_CMD_BATTERY_GET_STATIC host command and read strings from the response. This is assumed to be exclusively controlled by the OS, because host commands' use of buffers is prone to race conditions. To support readout of longer strings via ACPI mechanisms, this change adds support for EC_ACPI_MEM_STRINGS_FIFO (https://crrev.com/c/5581473) and allows ACPI firmware to read strings of arbitrary length (currently limited to 64 characters in the implementation) from the EC and to determine whether this function is supported by the EC (falling back to shared memory if not). BUG=b:339171261 TEST=on yaviks, the EC console logs FIFO readout messages when used in ACPI and correct strings are shown in the OS. If EC support is removed, correct strings are still shown in the OS. BRANCH=nissa Change-Id: Ia29cacb7d86402490f9ac458f0be50e3f2192b04 Signed-off-by: Peter Marheine <pmarheine@chromium.org> Reviewed-on: https://review.coreboot.org/c/coreboot/+/82775 Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Reviewed-by: Subrata Banik <subratabanik@google.com>
Diffstat (limited to 'src/device/gpio.c')
0 files changed, 0 insertions, 0 deletions