<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - hdmi audio: spec violation for >=uhd-4k TMDS clock frequencies, no audio out in worst case"
href="https://bugs.freedesktop.org/show_bug.cgi?id=90776#c1">Comment # 1</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - hdmi audio: spec violation for >=uhd-4k TMDS clock frequencies, no audio out in worst case"
href="https://bugs.freedesktop.org/show_bug.cgi?id=90776">bug 90776</a>
from <span class="vcard"><a class="email" href="mailto:jani.nikula@intel.com" title="Jani Nikula <jani.nikula@intel.com>"> <span class="fn">Jani Nikula</span></a>
</span></b>
<pre>At a glance, looks like the spec has been clarified, and what we currently do
(let the hardware figure out the N/CTS values based on the HDMI pixel clock)
might only work reliably for CEA modes.
At the second glance, looks like we got ourselves a nice little catch-22 here.
When we enable an audio capable output, we notify the audio driver about this
(through hardware). At this point we don't know or care what the audio driver
does about it. We go on enabling the output. However if the audio driver is in
control of the sampling rate, and the N/CTS values need to be adjusted based on
that, we'd need to disable the transcoder to make the change...</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>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>