Message ID | bug-96789-502@http.bugs.freedesktop.org/ (mailing list archive) |
---|---|
State | New, archived |
Headers | show |
https://bugs.freedesktop.org/show_bug.cgi?id=96789 --- Comment #1 from Christian König <deathsimple@vodafone.de> --- Well that is a rather special case. The monitor needs a very precise timing to work reliable and even with the higher ref/post dividers we don't hit it completely correct. Not sure what to do here, cause raising the limit will certainly break others again.
https://bugs.freedesktop.org/show_bug.cgi?id=96789 --- Comment #2 from Benjamin Herrenschmidt <benh@kernel.crashing.org> --- Will it ? I mean, it works with every other driver under the sun ;-) Do you have ways to know what AMD windows driver picks ? That could be a reasonable choice for the Linux one...
https://bugs.freedesktop.org/show_bug.cgi?id=96789 Martin Peres <martin.peres@free.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |MOVED Status|NEW |RESOLVED --- Comment #3 from Martin Peres <martin.peres@free.fr> --- -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/723.
--- a/drivers/gpu/drm/radeon/radeon_display.c +++ b/drivers/gpu/drm/radeon/radeon_display.c @@ -953,7 +953,7 @@ static void avivo_get_fb_ref_div(unsigned nom, unsigned den, unsigned post_div, unsigned *fb_div, unsigned *ref_div) { /* limit reference * post divider to a maximum */ - ref_div_max = max(min(100 / post_div, ref_div_max), 1u); + ref_div_max = max(min(128 / post_div, ref_div_max), 1u); /* get matching reference and feedback divider */