From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 82781] Option to disable mclk reclocking with AMD R9 280X (TAHITI) to avoid screen flickering on VGA/CRT
Date: Tue, 19 Aug 2014 18:46:43 +0000 [thread overview]
Message-ID: <bug-82781-2300-N7mjbtstOu@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-82781-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=82781
--- Comment #11 from Christian Birchinger <joker@netswarm.net> ---
Simply doing this also works:
ni_dpm.c:
bool ni_dpm_vblank_too_short(struct radeon_device *rdev)
{
struct rv7xx_power_info *pi = rv770_get_pi(rdev);
u32 vblank_time = r600_dpm_get_vblank_time(rdev);
/* we never hit the non-gddr5 limit so disable it */
u32 switch_limit = pi->mem_gddr5 ? 450 : 0;
return true;
Adding a hardcoded true also disables mclk changes. which only leads
to one conclusion:
if (vblank_time <= switch_limit)
return true;
else
return false;
Somehow the values are not always 450 but i cannot see such a case
in the printk debug.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2014-08-19 18:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-19 15:11 [Bug 82781] New: Option to disable mclk reclocking with AMD R9 280X (TAHITI) to avoid screen flickering on VGA/CRT bugzilla-daemon
2014-08-19 15:23 ` [Bug 82781] " bugzilla-daemon
2014-08-19 15:56 ` bugzilla-daemon
2014-08-19 15:57 ` bugzilla-daemon
2014-08-19 16:00 ` bugzilla-daemon
2014-08-19 16:16 ` bugzilla-daemon
2014-08-19 16:27 ` bugzilla-daemon
2014-08-19 16:38 ` bugzilla-daemon
2014-08-19 17:08 ` bugzilla-daemon
2014-08-19 17:11 ` bugzilla-daemon
2014-08-19 17:58 ` bugzilla-daemon
2014-08-19 18:46 ` bugzilla-daemon [this message]
2014-08-19 19:12 ` bugzilla-daemon
2014-08-19 19:39 ` 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-82781-2300-N7mjbtstOu@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.