<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Apr 2, 2013 at 11:20 PM, Jesse Barnes <span dir="ltr"><<a href="mailto:jbarnes@virtuousgeek.org" target="_blank">jbarnes@virtuousgeek.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On Thu, 28 Mar 2013 10:42:03 +0100<br>
Daniel Vetter <<a href="mailto:daniel.vetter@ffwll.ch">daniel.vetter@ffwll.ch</a>> wrote:<br>
<br>
> With the exception of hsw, which has dedicated DP clocks which run at<br>
> the fixed frequency already, and vlv, which doesn't have optmized<br>
> pre-defined dp clock parameters (yet).<br>
><br>
<br>
</div>Nice. I think we should do this for common HDMI modes too. We have<br>
some extra clock manipulation regs we can use to tune things, so having<br>
fixed dividers for 720p and 1080p along with the tuning params should<br>
give us better behavior than what we have today.</blockquote></div><br></div><div class="gmail_extra">Imo we still have a few lower-hanging fruit before we need to start doing clock fine-tuning in hdmi-land: Atm we don't really bother with supporting the 1001/1000 modified clocks in the CEA spec at all ... Once we have the support code for that, adding fine-tuned clocks for those modes starts to make sense, so that we really hit them spot-on.<br>
</div><div class="gmail_extra">-Daniel<br>-- <br>Daniel Vetter<br>Software Engineer, Intel Corporation<br>+41 (0) 79 365 57 48 - <a href="http://blog.ffwll.ch" target="_blank">http://blog.ffwll.ch</a>
</div></div>