<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO --- - sna: (Haswell) X-server freezes when enabling DP at docking station"
href="https://bugs.freedesktop.org/show_bug.cgi?id=71267#c32">Comment # 32</a>
on <a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO --- - sna: (Haswell) X-server freezes when enabling DP at docking station"
href="https://bugs.freedesktop.org/show_bug.cgi?id=71267">bug 71267</a>
from <span class="vcard"><a class="email" href="mailto:consume.noise@gmail.com" title="Daniel Martin <consume.noise@gmail.com>"> <span class="fn">Daniel Martin</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=71267#c31">comment #31</a>)
<span class="quote">> Jani and I had a conversation about this not-so-very-long ago.
> Unfortunately, the spec is rather vague on the details of AUX_DEFERs.
> There's a little bit more information in there for I2C-over-AUX behavior,
> but nothing directly about native AUX_DEFERs as far as retry timeouts go.
> Essentially the spec just says "the source device can try again later" and
> leaves it at that. There's also an instance in the spec that says "assumes
> the Source repeats request immediately following a DP Sink AUX Defer
> response". Nothing like consistency...
>
> That said, I would think that up to 300us would be a safe value for a retry
> timeout.</span >
I've raised and tested the udelay() from 100 to 300. It doesn't work reliable,
especially when replugging the dp connector. But, a value of 500 did.
<span class="quote">> That should be fine for isolated DEFERs or even a short series of
> them. However, lots of defers with a timeout value like this can stretch AUX
> operations out beyond specified specified time limits (10ms for link
> training for instance), so that's something to keep in mind.</span >
Just for my understanding:
- What are isolated DEFERs?
- Is such a docking station nothing more than an active DP adapter?</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>