<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [HSW HDMI] Audio with 44.1 khz not working when 1920x1080p screen refreshrate > 30hz"
href="https://bugs.freedesktop.org/show_bug.cgi?id=97442#c16">Comment # 16</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [HSW HDMI] Audio with 44.1 khz not working when 1920x1080p screen refreshrate > 30hz"
href="https://bugs.freedesktop.org/show_bug.cgi?id=97442">bug 97442</a>
from <span class="vcard"><a class="email" href="mailto:Mark_Wilczynski@hotmail.com" title="Mark Wilczynski <Mark_Wilczynski@hotmail.com>"> <span class="fn">Mark Wilczynski</span></a>
</span></b>
<pre>I figured out why I was seeing video frame skipping when playing 59.940 fps
content using <a href="mailto:1920x1080@59.940">1920x1080@59.940</a> video mode.
When the pipeline is configured for regular 8-bit output, the refresh rate
measures 59.94005994. This is virtually perfect for the requested modeline:
Modeline 0:"" 0 148352 1920 2008 2052 2200 1080 1084 1089 1125 0x0 0x5
When the pipeline is configured for 12=bit output, the refresh rate measures
59.89304812. This causes a frame to be skipped every 21.2 seconds
(1/(59.94005994-59.89304812)) in order to stay in sync with the expected 59.940
rate.
I measured the actual vsync rate using the GPU counters in the PIPE_FRMCNT and
PIPE_FRMTMSTMP registers.
In Windows 10, the refresh rate is correct at both 8-bit and 12-bit output so
there must be some error in the Linux driver when setting up the pixel clock or
its dividers.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
<li>You are on the CC list for the bug.</li>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>