summaryrefslogtreecommitdiff
path: root/board/eve/board.h
diff options
context:
space:
mode:
authorDuncan Laurie <dlaurie@google.com>2017-07-23 00:28:09 -0700
committerCommit Bot <commit-bot@chromium.org>2020-08-26 14:58:51 +0000
commit1bc6436fce086c992805ca2fa366bf31a5d24b77 (patch)
tree741949dbb2538df722e646388882ef6682aa3683 /board/eve/board.h
parent430960724dcfda8e13db95632aba68607e27db3f (diff)
downloadchrome-ec-1bc6436fce086c992805ca2fa366bf31a5d24b77.tar.gz
eve: Remove CONFIG_BATTERY_REVIVE_DISCONNECT
Since Eve has a custom battery presence function we do not need the disconnect behavior as it will recover better by letting the state machine handle it with precharge directly. Without this change I would sometimes see the first boot after a cut-off battery get stuck with "battery found in disconnect state" and not able to boot up the AP. BUG=b:63957122 BRANCH=eve TEST=manual testing on Eve with cut-off batteries shows more consistent behavior to boot the AP after plugging in adapter. Change-Id: I2d115788c1f9f6171a01525970285abb9f3467a2 Signed-off-by: Duncan Laurie <dlaurie@google.com> Reviewed-on: https://chromium-review.googlesource.com/582538 Reviewed-by: Scott Collyer <scollyer@chromium.org> Reviewed-by: Furquan Shaikh <furquan@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/2319998 Tested-by: Patryk Duda <pdk@semihalf.com> Reviewed-by: Jett Rink <jettrink@chromium.org> Commit-Queue: Patryk Duda <pdk@semihalf.com>
Diffstat (limited to 'board/eve/board.h')
-rw-r--r--board/eve/board.h1
1 files changed, 0 insertions, 1 deletions
diff --git a/board/eve/board.h b/board/eve/board.h
index 2274fa0d5d..7365286b23 100644
--- a/board/eve/board.h
+++ b/board/eve/board.h
@@ -76,7 +76,6 @@
#define CONFIG_BATTERY_CUT_OFF
#define CONFIG_BATTERY_DEVICE_CHEMISTRY "LION"
#define CONFIG_BATTERY_PRESENT_CUSTOM
-#define CONFIG_BATTERY_REVIVE_DISCONNECT
#define CONFIG_BATTERY_SMART
/* Charger */