mirror of
https://github.com/Telecominfraproject/OpenCellular.git
synced 2025-12-28 02:35:28 +00:00
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>
This commit is contained in:
committed by
chrome-internal-fetch
parent
61dedac2fa
commit
f862275b9d
@@ -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)
|
||||
|
||||
Reference in New Issue
Block a user