diff options
author | Scott Collyer <scollyer@google.com> | 2019-08-29 14:14:33 -0700 |
---|---|---|
committer | Commit Bot <commit-bot@chromium.org> | 2019-10-17 06:14:32 +0000 |
commit | 9e271aeb78c7f8bc21cd52b66305217d0770ac46 (patch) | |
tree | 8acb27cc928ebe2f72eb72361f5184dd3dbd1aec /test/sha256_unrolled.tasklist | |
parent | 3db43fe342f4423cb450cb9fb14e69d1bc0a7b56 (diff) | |
download | chrome-ec-9e271aeb78c7f8bc21cd52b66305217d0770ac46.tar.gz |
pd: Extend READY_HOLD_OFF_US timer value for SRC
The READY_HOLD_OFF_US was set to 200 msec for both SNK and SRC
connections. However, in the case of SRC, there can be a race
condition with charge through hubs that initiate a power swap request
and the SRC port sending the VDM discover idenity message.
This CL makes the holdoff timer delay longer for SRC connections and
prefixes READY_HOLD_OFF_US with SNK/SRC to differentiate the two timer
values.
BUG=b:140092163
BRANCH=None
TEST=Tested with the AA-AM1N95W charge through hub. Verfied
that this can be attached to Kohaku with external power already
connected and successfully power role swap into source to charge the
kohaku port. Tested 20-25 connections with no failures. Prior to this
change the failure rate was 1 out of 3 attempts.
Change-Id: I375415fec96baf44ecd4592033e8b44ed4616011
Signed-off-by: Scott Collyer <scollyer@google.com>
Signed-off-by: Tim Wawrzynczak <twawrzynczak@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/1776844
Tested-by: Scott Collyer <scollyer@chromium.org>
Tested-by: Jongpil Jung <jongpil19.jung@samsung.corp-partner.google.com>
Diffstat (limited to 'test/sha256_unrolled.tasklist')
0 files changed, 0 insertions, 0 deletions