diff options
| author | Alec Berg <alecaberg@chromium.org> | 2014-08-22 09:40:53 -0700 |
|---|---|---|
| committer | chrome-internal-fetch <chrome-internal-fetch@google.com> | 2014-08-26 01:06:31 +0000 |
| commit | f862275b9dfe375a4c4a2e5b09ad5d2eebabd69f (patch) | |
| tree | f2e468153c1def901b50650baa36a0416f9b3a6d | |
| parent | 61dedac2fab0288e070fcb6d11e26ed23115d492 (diff) | |
| download | chrome-ec-f862275b9dfe375a4c4a2e5b09ad5d2eebabd69f.tar.gz | |
samus: change input current limit to the real limit
Remove the hack to set the input current limit to 2/3 of the
real limit. This was a hardware limitation of p2b systems. This
change will only work on EVT.
BUG=chrome-os-partner:28532
BRANCH=none
TEST=loaded onto a samus with all of the charging circuit reworks
and tested with an EVT zinger to make sure we don't OCP the
zinger. We limit current to 2944mA and zinger reads current draw
as 3150mA. The discrepancy is a hardware problem on zinger side
measuring current, but is still comfortably below 3.6A OCP limit.
Change-Id: Ia6adc79a0c6c7599ded76fb8f48de1479f021fe1
Signed-off-by: Alec Berg <alecaberg@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/213772
Reviewed-by: Duncan Laurie <dlaurie@chromium.org>
| -rw-r--r-- | common/host_command_pd.c | 7 |
1 files changed, 0 insertions, 7 deletions
diff --git a/common/host_command_pd.c b/common/host_command_pd.c index 82d58f79aa..5f57c83305 100644 --- a/common/host_command_pd.c +++ b/common/host_command_pd.c @@ -50,13 +50,6 @@ static void pd_exchange_status(void) } /* Set input current limit */ -#ifdef BOARD_SAMUS - /* - * TODO(crosbug.com/p/28532): Remove this workaround for Samus p2b - * boards which cannot correctly limit input current. - */ - pd_status.curr_lim_ma = pd_status.curr_lim_ma * 2 / 3; -#endif rv = charge_set_input_current_limit(MAX(pd_status.curr_lim_ma, CONFIG_CHARGER_INPUT_CURRENT)); if (rv < 0) |