From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 69721] New: Can't reach maximum memory speed (or core speed) when using dpm=1 on r600g
Date: Mon, 23 Sep 2013 16:13:24 +0000 [thread overview]
Message-ID: <bug-69721-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1272 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=69721
Priority: medium
Bug ID: 69721
Assignee: dri-devel@lists.freedesktop.org
Summary: Can't reach maximum memory speed (or core speed) when
using dpm=1 on r600g
Severity: normal
Classification: Unclassified
OS: All
Reporter: alexandre.f.demers@gmail.com
Hardware: All
Status: NEW
Version: XOrg CVS
Component: DRM/Radeon
Product: DRI
After fixing bug 68235, it appears the maximum memory speed (or core speed)
can't always be reached. This situation depends on the voltage tweaking seen on
some cards. As an exemple, XFX HD-695X-ZNDC has the following maximum values:
max_sclk_vddc->80000, max_mclk_vddci->125000, max_mclk_vddc->125000.
However, the maximum memory clock value should be 130000 and the core clock
should be 83000.
As Alex Deucher explained: "This patch set works around the issue by limiting
the sclk and mclk to the highest levels listed in the clk/voltage dependency
tables. I'll need to dig a bit more internally to try and figure out how to
handle these clks properly."
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2801 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 reply other threads:[~2013-09-23 16:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-23 16:13 bugzilla-daemon [this message]
2013-09-23 16:14 ` [Bug 69721] Can't reach maximum memory speed (or core speed) when using dpm=1 on r600g bugzilla-daemon
2013-09-23 16:15 ` bugzilla-daemon
2013-09-23 23:03 ` [Bug 69721] Can't reach maximum memory speed (or core speed) when using dpm=1 on r600g on cards not sticking to reference board bugzilla-daemon
2014-09-22 4:30 ` bugzilla-daemon
2014-09-22 14:18 ` bugzilla-daemon
2014-09-22 16:19 ` bugzilla-daemon
2014-09-22 16:31 ` bugzilla-daemon
2014-09-22 19:30 ` bugzilla-daemon
2014-09-23 4:43 ` bugzilla-daemon
2014-09-26 22:10 ` 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-69721-502@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).