From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 73067] RV770 - screen flicker with radeon.dpm=1
Date: Thu, 16 Jan 2014 19:06:02 +0000 [thread overview]
Message-ID: <bug-73067-502-ZqsUdGVo6O@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-73067-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1138 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=73067
--- Comment #12 from Alex Deucher <agd5f@yahoo.com> ---
(In reply to comment #11)
> I found that my screen was flicking once in ~4 seconds because of conky.
> With conky off, flicks happen but happen a lot less, like 1 in ~20 - this
> period depends on what I'm doing. But testing with glxspheres, screen
> flicker happens each ~4 seconds again. Probably this isn't important.
>
It happens whenever there is an mclk transition based on GPU load.
> Can you give some hints about the solution? Do you think this can be fixed?
> Or this driver won't support mclk transition on this board?
I'm not sure how reliable mclk switching was on rv770 boards in general. Most
rv770 boards I've seen have the same mclk for all performance levels. You
might try adjusting the value of CG_DISPLAY_GAP_CNTL in
rv770_program_display_gap(). Maybe try R600_PM_DISPLAY_GAP_VBLANK_OR_WM or
R600_PM_DISPLAY_GAP_WATERMARK rather than R600_PM_DISPLAY_GAP_VBLANK for
DISP1_GAP_MCHG, but I don't think it will make a difference.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2007 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2014-01-16 19:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-27 13:31 [Bug 73067] New: RV770 - screen flicker with radeon.dpm=1 bugzilla-daemon
2013-12-27 13:34 ` [Bug 73067] " bugzilla-daemon
2013-12-27 13:37 ` bugzilla-daemon
2013-12-27 15:20 ` bugzilla-daemon
2013-12-27 15:22 ` bugzilla-daemon
2013-12-27 20:15 ` bugzilla-daemon
2013-12-27 20:16 ` bugzilla-daemon
2013-12-28 11:22 ` bugzilla-daemon
2014-01-07 18:53 ` bugzilla-daemon
2014-01-16 17:12 ` bugzilla-daemon
2014-01-16 17:15 ` bugzilla-daemon
2014-01-16 18:07 ` bugzilla-daemon
2014-01-16 19:06 ` bugzilla-daemon [this message]
2014-02-16 13:03 ` bugzilla-daemon
2014-02-17 8:03 ` bugzilla-daemon
2014-02-17 17:35 ` 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-73067-502-ZqsUdGVo6O@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.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;
as well as URLs for NNTP newsgroup(s).