On 21 November 2017 14:08, Adam Thomson wrote:
> Subject: [PATCH] typec: tcpm: fusb302: Resolve out of order messaging events
Sorry. Finger trouble. Will resend with correct 'v3' title
> The expectation in the FUSB302 driver is that a TX_SUCCESS event
> should occur after
The expectation in the FUSB302 driver is that a TX_SUCCESS event
should occur after a message has been sent, but before a GCRCSENT
event is raised to indicate successful receipt of a message from
the partner. However in some circumstances it is possible to see
the hardware raise a GCRCSENT event be
The expectation in the FUSB302 driver is that a TX_SUCCESS event
should occur after a message has been sent, but before a GCRCSENT
event is raised to indicate successful receipt of a message from
the partner. However in some circumstances it is possible to see
the hardware raise a GCRCSENT event be
