From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 82781] New: Option to disable mclk reclocking with AMD R9 280X (TAHITI) to avoid screen flickering on VGA/CRT
Date: Tue, 19 Aug 2014 15:11:12 +0000 [thread overview]
Message-ID: <bug-82781-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=82781
Bug ID: 82781
Summary: Option to disable mclk reclocking with AMD R9 280X
(TAHITI) to avoid screen flickering on VGA/CRT
Product: Drivers
Version: 2.5
Kernel Version: 3.16.1
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: joker@netswarm.net
Regression: No
I would like an option to forcefully disable mclk reclocking. Either as a
module parameter
or of course prefered at runtime as additional sysfs option in
/sys/class/drm/card[n]/device
probably with "power_<something>". The reason for this follows.
I switched from a AMD 5570 to a R9 280X card. Both have working and stable DPM.
With the new AMD R9 280X i noticed ocasiuonal screen flickering and narrowed it
down
to the mclk reclocking between "15000" level 0 and "160000" level 1-3.
By connecting my TV over HDMI i noticed this would stop as multi head is known
to
disable mclk reclocking (I've checked si_dpm.c)
I now hardcoded "disable_mclk_switching = true;" there and have a perfectly
working
flicker free screen.
The sclk still changes fine and while probably not as power saving as full
reclocking
of course a lot better than totaly disabling DPM or forcing it to "low" and
"high" based
on the tasks i'm doing.
I've also noticed this effect on Windows using proprietary drivers even tough a
lot less
than on Linux. Therefor i expect this to be a hardware related issue probably
only visible
on VGA analog out to CRT screens, so i fear it's not fixable in an automatic
way.
An option to manualy disable this feature in sysfs would help a lot. At runtime
mclk reclocking
could be reenabled while DPMS is on (aka. the screen is turned off). If this
could be detected
automaticaly it would be even better.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2014-08-19 15:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-19 15:11 bugzilla-daemon [this message]
2014-08-19 15:23 ` [Bug 82781] Option to disable mclk reclocking with AMD R9 280X (TAHITI) to avoid screen flickering on VGA/CRT 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
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@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.