[Bug 48880] Set mode has different timings than requested on VGA

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Wed Apr 18 18:47:03 PDT 2012


--- Comment #12 from Tvrtko Ursulin <tvrtko.ursulin at onelan.co.uk> 2012-04-19 01:47:03 UTC ---
RADEON_PLL_PREFER_MINM_OVER_MAXP fixes it, monitor now reports the same pixel
clock as from the modeline and locks onto it correctly.

If interesting, I collected before and after clock setup from
radeon_compute_pll_avivo. Without RADEON_PLL_PREFER_MINM_OVER_MAXP:

adjusted_clock=148500, pll_clock=14843, fb_fiv=95, frac_fb_div=0, ref_div=8,


adjusted_clock=148500, pll_clock=14857, fb_fiv=52, frac_fb_div=0, ref_div=7,

Should that be the fix then or I should investigate something else?

I don't understand how without this flag monitor was claiming to be receiving
175.9MHz pixel clock. Then again pll_clock got from radeon_compute_pll_avivo
does not seem to be used later in atombios_crtc_set_pll. So perhaps driver did
attempt to set 175.9MHz pixel clock. Where would I stick some debug to know
what was definitely asked from the hardware? Because if this was true, it would
mean monitors EDID data was not being respected.

Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

More information about the dri-devel mailing list