diff options
author | Bernard Shyu <bernard_shyu@bizlinktech.com> | 2015-07-08 19:28:01 +0800 |
---|---|---|
committer | ChromeOS Commit Bot <chromeos-commit-bot@chromium.org> | 2015-07-15 20:29:30 +0000 |
commit | c08e3b2113e2c871afa03b84365d06d714ea7228 (patch) | |
tree | a15203a28ffaaa8afa4effb413806aeb39f6bf47 /test/queue.c | |
parent | 0a8c6c039641bc99433870738ae621aa0714d8f5 (diff) | |
download | chrome-ec-c08e3b2113e2c871afa03b84365d06d714ea7228.tar.gz |
pd: finitely sending of SNK_CAP in SRC_READY
Even a decent type-C device SHALL respond SNK_CAP query message when we are in
SRC_READY state, but in the case its mal implementation shouldn't get us being
trapped in an infinite loop of SRC_READY / SRC_GET_SNK_CAP states.
Introduce a counter to give up sending of SNK_CAP and just print a ERR
indication log when the partner device ignores SNK_CAP query.
BUG=none
BRANCH=samus
TEST=make buildall
manual testing against the failing USB-C device
Change-Id: I4c4251b2264230d7dd30bd2b9fc2b56027ff0d5a
Signed-off-by: Bernard Shyu <bernard_shyu@bizlinktech.com>
Reviewed-on: https://chromium-review.googlesource.com/284035
Reviewed-by: Alec Berg <alecaberg@chromium.org>
Commit-Queue: Alec Berg <alecaberg@chromium.org>
Diffstat (limited to 'test/queue.c')
0 files changed, 0 insertions, 0 deletions