<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [SKL] "testdisplay -a" *ERROR* mismatch in base.adjusted_mode.crtc_clock (expected 13500, found 27000)"
href="https://bugs.freedesktop.org/show_bug.cgi?id=90237#c5">Comment # 5</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [SKL] "testdisplay -a" *ERROR* mismatch in base.adjusted_mode.crtc_clock (expected 13500, found 27000)"
href="https://bugs.freedesktop.org/show_bug.cgi?id=90237">bug 90237</a>
from <span class="vcard"><a class="email" href="mailto:conselvan2@gmail.com" title="Ander Conselvan de Oliveira <conselvan2@gmail.com>"> <span class="fn">Ander Conselvan de Oliveira</span></a>
</span></b>
<pre>The error in the first log,
*ERROR* mismatch in base.adjusted_mode.crtc_clock (expected 13500, found 27000)
happens when using a mode with DRM_MODE_FLAG_DBLCLK. Because of that flag,
intel_hdmi_compute_config() sets the pipe_config's pixel_multiplier to 2, which
in turns causes intel_modeset_pipe_config() to double the port clock. When we
read back the hardware configuration for state checking, ->get_pipe_config()
reads the port clock as doubled (27000 instead of 13500) and sets
adjusted_mode.crtc_clock to be equal to the port_clock.
In the second log, the mismatch happens with SKL scalers, so they should be
tracked in a separate bug if they still occur.</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>