From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 75241] radeon_compute_pll_avivo broken in 3.15-rc3
Date: Sat, 02 Jul 2016 10:21:36 +0000 [thread overview]
Message-ID: <bug-75241-2300-aXzghAbiEY@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-75241-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=75241
Benjamin Herrenschmidt <benh@kernel.crashing.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |benh@kernel.crashing.org
--- Comment #30 from Benjamin Herrenschmidt <benh@kernel.crashing.org> ---
Your latest change broke it for me, sorry for the delay in noticing, that
combination of machine & monitor was stuck in the dark ages for a while...
The combo is Radeon R9 290 (from Sapphire) and good old Apple Cinema Display
23" (1920x1200x60 fixed resolution display) on DVI.
I get a black screen with radeon. It works with Alex's amdgpu. The one liner
that fixes it is in the PLL calculation:
-ref_div_max = max(min(100 / post_div, ref_div_max), 1u);
+ref_div_max = max(min(128 / post_div, ref_div_max), 1u);
I noticed other differences though, the max fb div is 2047 with radeon and 4095
with amdgpu but the above is the key.
This is a trace of amdgpu calculation (which works) after I sprinkled printk's
around:
[ 3.471131] fb_div_min/max=4/4095 pll_flags=400
[ 3.471132] by 10 ! fb_div_min/max=40/40950
[ 3.471133] ref_div_min=2 (from 0/2)
[ 3.471133] ref_div_max=1023 (from 0/1023)
[ 3.471134] vco_min/max=600000/1200000
[ 3.471134] post_div_min/max=4/7
[ 3.471135] initial nom=153970, den=2700
[ 3.471136] reduced nom=15397, den=270
[ 3.471136] - trying post_div 4, ref_div_max=32
[ 3.471137] tentative ref_div=32m, fb_div=7299
[ 3.471137] adjusted ref_div=32m, fb_div=7299
[ 3.471138] diff=7, diff_best=-1
[ 3.471138] - trying post_div 5, ref_div_max=25
[ 3.471139] tentative ref_div=25m, fb_div=7128
[ 3.471139] adjusted ref_div=25m, fb_div=7128
[ 3.471139] diff=6, diff_best=7
[ 3.471140] - trying post_div 6, ref_div_max=21
[ 3.471140] tentative ref_div=21m, fb_div=7185
[ 3.471141] adjusted ref_div=21m, fb_div=7185
[ 3.471141] diff=6, diff_best=6
[ 3.471141] - trying post_div 7, ref_div_max=18
[ 3.471142] tentative ref_div=18m, fb_div=7185
[ 3.471142] adjusted ref_div=18m, fb_div=7185
[ 3.471150] diff=6, diff_best=6
[ 3.471150] post_div_best=7
[ 3.471151] - trying post_div 7, ref_div_max=18
[ 3.471151] tentative ref_div=18m, fb_div=7185
[ 3.471152] adjusted ref_div=18m, fb_div=7185
[ 3.471153] [drm:amdgpu_pll_compute] 153970 - 153960, pll dividers - fb:
239.5 ref: 6, post 7
Now this is with radeon *NOTE: I have bumped the max fb div to the same as AMD
GPU when taking that trace but that had no effect:
[ 4.718126] fb_div_min/max=4/4095 pll_flags=410
[ 4.718126] by 10 ! fb_div_min/max=40/40950
[ 4.718127] ref_div_min=2 (from 0/2)
[ 4.718128] ref_div_max=1023 (from 0/1023)
[ 4.718128] vco_min/max=600000/1200000
[ 4.718129] post_div_min/max=4/7
[ 4.718129] initial nom=153970, den=2700
[ 4.718130] reduced nom=15397, den=270
[ 4.718130] - trying post_div 4, ref_div_max=25
[ 4.718131] tentative ref_div=25m, fb_div=5703
[ 4.718131] adjusted ref_div=25m, fb_div=5703
[ 4.718132] diff=11, diff_best=-1
[ 4.718133] - trying post_div 5, ref_div_max=20
[ 4.718133] tentative ref_div=20m, fb_div=5703
[ 4.718133] adjusted ref_div=20m, fb_div=5703
[ 4.718134] diff=11, diff_best=11
[ 4.718134] - trying post_div 6, ref_div_max=16
[ 4.718135] tentative ref_div=16m, fb_div=5474
[ 4.718135] adjusted ref_div=16m, fb_div=5474
[ 4.718136] diff=14, diff_best=11
[ 4.718136] - trying post_div 7, ref_div_max=14
[ 4.718136] tentative ref_div=14m, fb_div=5589
[ 4.718137] adjusted ref_div=14m, fb_div=5589
[ 4.718137] diff=12, diff_best=11
[ 4.718138] post_div_best=5
[ 4.718138] - trying post_div 5, ref_div_max=20
[ 4.718139] tentative ref_div=20m, fb_div=5703
[ 4.718139] adjusted ref_div=20m, fb_div=5703
[ 4.718141] [drm:radeon_compute_pll_avivo] 153970 - 153980, pll dividers -
fb: 570.3 ref: 20, post 5
The modeline is:
Modeline 55:"1920x1200" 60 153970 1920 1968 2000 2080 1200 1203 1209 1235 0x48
0x9
And is consistent between the 2 drivers.
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-07-02 10:21 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-01 13:51 [Bug 75241] New: radeon_compute_pll_avivo broken in 3.15-rc3 bugzilla-daemon
2014-05-01 14:48 ` [Bug 75241] " bugzilla-daemon
2014-05-01 17:02 ` bugzilla-daemon
2014-05-01 19:24 ` bugzilla-daemon
2014-05-02 12:37 ` bugzilla-daemon
2014-05-02 21:08 ` bugzilla-daemon
2014-05-03 11:25 ` bugzilla-daemon
2014-05-15 15:14 ` bugzilla-daemon
2014-05-15 15:26 ` bugzilla-daemon
2014-05-15 15:33 ` bugzilla-daemon
2014-05-15 16:58 ` bugzilla-daemon
2014-05-15 17:57 ` bugzilla-daemon
2014-05-15 17:58 ` bugzilla-daemon
2014-05-15 17:59 ` bugzilla-daemon
2014-05-16 19:51 ` bugzilla-daemon
2014-05-20 13:20 ` bugzilla-daemon
2014-05-20 15:25 ` bugzilla-daemon
2014-05-20 15:26 ` bugzilla-daemon
2014-05-20 15:27 ` bugzilla-daemon
2014-05-20 15:51 ` bugzilla-daemon
2014-05-20 18:56 ` bugzilla-daemon
2014-05-21 18:07 ` bugzilla-daemon
2014-05-21 18:23 ` bugzilla-daemon
2014-05-23 17:16 ` bugzilla-daemon
2014-06-01 8:37 ` bugzilla-daemon
2014-07-02 7:32 ` bugzilla-daemon
2014-07-04 13:43 ` bugzilla-daemon
2014-07-06 18:37 ` bugzilla-daemon
2014-07-07 12:41 ` bugzilla-daemon
2014-08-06 6:00 ` bugzilla-daemon
2016-07-02 10:21 ` bugzilla-daemon [this message]
2016-07-02 10:58 ` bugzilla-daemon
2016-07-02 10:59 ` bugzilla-daemon
2016-07-02 16:16 ` bugzilla-daemon
2016-07-02 21:47 ` bugzilla-daemon
2016-07-05 9:04 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-75241-2300-aXzghAbiEY@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox