On Mon, Jul 04, 2022 at 04:01:23PM +0000, Murthy, Arun R wrote:
> > On Mon, Jul 04, 2022 at 12:53:52PM +0530, Arun R Murthy wrote:
> > > On linktraining error/timeout before retry need to wait for 400usec as
> > > per the DP CTS spec1.2
> >
> > s/CTS//
> >
> > > Under section 2.7.2 AUX Transaction Response/Reply Time-outs AUX
> > > Replier (the uPacket RX) must start sending the reply back to the AUX
> > > requester (the uPacket TX) within the response period of 300μs. The
> > > timer for Response Time-out starts ticking after the uPacket RX has
> > > finished receiving the AUX STOP condition which ends the AUX Request
> > transaction.
> > > The timer is reset either when the Response Time-out period has
> > > elapsed or when the uPacket RX has started to send the AUX Sync
> > > pattern (which follows
> > > 10 to 16 active pre-charge pulses) for the Reply transaction. If the
> > > uPacket TX does not receive a reply from the uPacket RX it must wait
> > > for a Reply Time-out period of 400us before initiating the next AUX
> > > Request transaction. The timer for the Reply Time-out starts ticking
> > > after the uPacket TX has finished sending the AUX STOP condition.
> > >
> > > The patch with commit 74ebf294a1dd ("drm/i915: Add a delay in
> > > Displayport AUX transactions for compliance testing") removes this
> > > delay mentioning the hardware already meets this requirement, but as
> > > per the spec the delay mentioned in the spec specifies how long to
> > > wait for the receiver response before timeout. So the delay here to
> > > wait for timeout and not a delay after timeout. The DP spec specifies
> > > a delay after timeout and hence adding this delay.
> >
> > Not sure what you're saying here. The spec states the reply timeout should
> > start counting once the TX has sent the AUX STOP, and gets reset when the
> > reply AUX SYNC is detected.
> >
> Copying the above said spec for quick reference "AUX Replier (the
> uPacket RX) must start sending the reply back to the AUX requester
> (the uPacket TX) within the response period of 300μs. The timer for
> Response Time-out starts ticking after the uPacket RX has finished
> receiving the AUX STOP condition which ends the AUX Request
> transaction. The timer is reset either when the Response Time-out
> period has elapsed or when the uPacket RX has started to send the AUX
> Sync pattern"
>
> The timer that is reference in the 1st line above is 300usec. The line
> just above says this timer should be reset when the response time-out
> has elapsed, my understanding over here is this 300usec time should be
> reset on timeout.
>
> Now coming back to the last few lines of the spec referenced above, "
> If the uPacket TX does not receive a reply from the uPacket RX it must
> wait for a Reply Time-out period of 400us before initiating the next
> AUX Request transaction" My understanding on this is if the TX did not
> receive the reply, which means the timeout has occurred in that case
> before initiating a new request again, we should wait for 400usec.
>
> So in the above referenced part of the code, there are two timers
> involved. One is 300usec and the other is 400usec. The 300usec is the
> timer for hardware timeout to occur and the 400usec is the timer that
> the software has to wait on timeout/error before retry.
300 usec is a timeout used by RX. After this expires RX should not
transmit anything (rather it should switch to listen mode) to avoid a
collision with TX. 400 usec is a timeout used by TX (starting from the
last bit of the packet it transmitted) for the same reason.
Based on the above not sure why an additional 400 usec delay would be
needed after a timeout error (which took 400 usec at least). I suppose
TX might incorrectly signal timeouts too early, this could be confirmed
from the retransmit timestamps.
> Thanks and Regards,
> Arun R Murthy
> --------------------
