Files
OpenCellular/common
Alec Berg 5348dff126 pd: Add NoResponseTimer to disconnect after no response
Add NoResponseTimer to go to disconnected state after some number
of hard resets with the port partner non-responsive. This only takes
affect when the port partner is known to be PD capable, i.e. has sent
us PD communications in the past. This is useful as a last resort to
attempt to restore PD communications with a port partner.

BUG=chrome-os-partner:34976
BRANCH=samus
TEST=load onto two samus', connect with C to C cable, and let them
form a PD contract, then on one side disable PD comms with "pd enable 0"
and from the other side initiate some PD traffic, such as "pd 1 soft".
See that the side with PD communications enabled sends two hard resets
and then goes to disconnected state, then goes to discovery state and
acts as if a non-PD capable device is attached.

Change-Id: Id40ce7eb05b8b7ae6a4f70b9d08ce6cad0d471fe
Signed-off-by: Alec Berg <alecaberg@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/238300
Reviewed-by: Vincent Palatin <vpalatin@chromium.org>
2015-01-06 22:19:22 +00:00
..
2014-05-21 20:32:17 +00:00
2013-12-20 05:07:58 +00:00
2014-05-21 20:32:17 +00:00
2014-05-21 20:32:17 +00:00
2014-05-21 20:32:17 +00:00
2014-05-21 20:32:17 +00:00
2014-03-06 21:32:57 +00:00
2014-07-17 00:40:23 +00:00
2013-10-25 20:12:49 +00:00
2014-05-21 20:32:17 +00:00
2014-05-21 20:32:17 +00:00
2013-12-19 00:12:28 +00:00
2014-05-21 20:32:17 +00:00
2014-03-06 21:33:09 +00:00
2014-05-21 20:32:17 +00:00
2014-01-14 09:19:45 +00:00
2014-05-21 20:32:17 +00:00
2014-05-21 20:32:17 +00:00
2013-12-19 00:12:28 +00:00
2014-05-17 20:14:17 +00:00
2013-12-19 00:12:28 +00:00
2014-05-21 20:32:17 +00:00
2014-05-21 20:32:17 +00:00
2014-05-21 20:32:17 +00:00