All of lore.kernel.org
 help / color / mirror / Atom feed
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: Fri, 02 May 2014 21:08:22 +0000	[thread overview]
Message-ID: <bug-75241-2300-Uil5VAh42U@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-75241-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=75241

--- Comment #5 from Clemens Ladisch <clemens@ladisch.de> ---
It's an Eizo S2100, but this should not matter because the clocks seen by the
monitor are always about the same (162MHz/75kHz/60Hz).  If some were out of
range, the monitor would show an error message, but with the PLL problem, the
monitor does not appear to detect even an out-of-range signal.   I'd guess the
PLL itself cannot handle the parameters.

The largest working ref_div_max limit is 131.

with 131:  162000 - 161990, pll dividers - fb: 1425.4 ref: 21, post 6

with 132:  162000 - 162000, pll dividers - fb: 1493.3 ref: 22, post 6

avivo_reduce_ratio does not change these values.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2014-05-02 21:08 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 [this message]
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
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-Uil5VAh42U@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.