From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@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 Message-ID: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1812806444==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 466DAE7421 for ; Mon, 23 Sep 2013 09:13:24 -0700 (PDT) List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org Errors-To: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============1812806444== Content-Type: multipart/alternative; boundary="1379952804.Ce1A1c30.5498"; charset="us-ascii" --1379952804.Ce1A1c30.5498 Date: Mon, 23 Sep 2013 16:13:24 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" 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. --1379952804.Ce1A1c30.5498 Date: Mon, 23 Sep 2013 16:13:24 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8"
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.
--1379952804.Ce1A1c30.5498-- --===============1812806444== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel --===============1812806444==--