diff options
| author | Daisuke Nojiri <dnojiri@chromium.org> | 2019-02-25 12:56:40 -0800 |
|---|---|---|
| committer | chrome-bot <chrome-bot@chromium.org> | 2019-03-06 06:51:30 -0800 |
| commit | dcd378e1cde499fe3c33efd98bd7e737b034ff77 (patch) | |
| tree | 8f8f022e28de1986e604faae0440d49ca5e7f5c9 /test | |
| parent | f2ea9714253427c81f9d154d0502d0d10124a8d2 (diff) | |
| download | chrome-ec-dcd378e1cde499fe3c33efd98bd7e737b034ff77.tar.gz | |
chgstv2: Make board_critical_shutdown_check specify action on critical soc
Currently, board_critical_shutdown_check is used only in the context
of CONFIG_BATTERY_CRITICAL_SHUTDOWN_CUT_OFF. It returns true to cutoff
the battery or false to take no action.
This patch extends board_critical_shutdown_check to allow it to control
what actions to take on critical battery condition.
With this change, each board can also customize critical battery actions
with more granularity (per OEM, BOARD_VERSION, etc.).
Signed-off-by: Daisuke Nojiri <dnojiri@chromium.org>
BUG=b/123727148
BRANCH=nami
TEST=Verify a battery is cutoff at critical low charge on Scarlet and
DUT wakes up by AC plugin on cros/firmware-scarlet-10388.B.
Change-Id: Id49e860b05e21c3bfa4d75f27c48b55c2a3ad95f
Reviewed-on: https://chromium-review.googlesource.com/1487113
Commit-Ready: ChromeOS CL Exonerator Bot <chromiumos-cl-exonerator@appspot.gserviceaccount.com>
Tested-by: Daisuke Nojiri <dnojiri@chromium.org>
Reviewed-by: Aseda Aboagye <aaboagye@chromium.org>
Diffstat (limited to 'test')
| -rw-r--r-- | test/sbs_charging_v2.c | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/test/sbs_charging_v2.c b/test/sbs_charging_v2.c index e266e59215..a41c8205d5 100644 --- a/test/sbs_charging_v2.c +++ b/test/sbs_charging_v2.c @@ -36,6 +36,11 @@ static void reset_mocks(void) shutdown_warning_time.val = 0ULL; } +int board_cut_off_battery(void) +{ + return EC_SUCCESS; +} + void chipset_force_shutdown(enum chipset_shutdown_reason reason) { is_shutdown = 1; |