Files
OpenCellular/include
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
..
2013-12-17 21:27:53 +00:00
2013-04-05 14:28:42 -07:00
2014-06-23 21:48:33 +00:00
2014-02-08 00:14:48 +00:00
2013-10-25 20:12:49 +00:00
2012-10-26 09:49:38 -07:00
2014-10-29 22:23:43 +00:00
2014-12-19 00:05:16 +00:00
2013-06-26 09:08:23 -07:00
2013-10-21 23:59:38 +00:00
2013-06-18 10:31:09 -07:00
2013-10-30 23:10:13 +00:00
2013-08-07 12:43:48 -07:00
2011-12-07 19:10:02 +00:00
2012-10-25 14:12:11 -07:00
2014-03-06 23:14:07 +00:00
2012-10-25 14:12:10 -07:00
2013-10-30 23:10:10 +00:00
2012-10-25 17:03:44 -07:00
2012-08-09 17:40:37 -07:00
2014-06-26 06:48:37 +00:00
2014-01-06 12:40:45 +00:00
2014-03-01 20:15:59 +00:00
2013-11-21 00:09:09 +00:00
2013-10-21 23:59:38 +00:00
2014-06-19 03:28:43 +00:00