From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 69721] Can't reach maximum memory speed (or core speed) when using dpm=1 on r600g on cards not sticking to reference board
Date: Mon, 22 Sep 2014 16:19:23 +0000 [thread overview]
Message-ID: <bug-69721-502-ITprB1L5ms@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-69721-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 850 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=69721
--- Comment #4 from Alexandre Demers <alexandre.f.demers@gmail.com> ---
(In reply to comment #3)
> Did you try again after fixing the vddci setup?
To my knowledge, the memory speed is still limited to 1250 instead of reaching
its maximum speed of 1300; the same thing goes for the core clock. I'll need to
have a look at the code, but the last time I had a look, we were still calling
btc_get_max_clock_from_voltage_dependency_table(), which was limiting the speed
to the reference values.
If I have time, I'll look at the code tonight and add some code to print values
that would be limited by btc_get_max_clock_from_voltage_dependency_table().
Other than this limitation, I have mostly no problem with my Cayman GPU.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1838 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-09-22 16:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-23 16:13 [Bug 69721] New: Can't reach maximum memory speed (or core speed) when using dpm=1 on r600g bugzilla-daemon
2013-09-23 16:14 ` [Bug 69721] " 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 [this message]
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-ITprB1L5ms@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 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.