From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@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:31:35 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1895960544==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 4281E6E453 for ; Mon, 22 Sep 2014 09:31:35 -0700 (PDT) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============1895960544== Content-Type: multipart/alternative; boundary="1411403495.feEe4b1.1437"; charset="us-ascii" --1411403495.feEe4b1.1437 Date: Mon, 22 Sep 2014 16:31:35 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" https://bugs.freedesktop.org/show_bug.cgi?id=69721 --- Comment #5 from Alex Deucher --- (In reply to comment #4) > (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. Right. I mean have you tried reverting that patch or just skipping the calls to btc_get_max_clock_from_voltage_dependency_table(). I think they should work fine now that vddci is fixed. -- You are receiving this mail because: You are the assignee for the bug. --1411403495.feEe4b1.1437 Date: Mon, 22 Sep 2014 16:31:35 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8"

Comment # 5 on bug 69721 from 
(In reply to comment #4)
> (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.

Right.  I mean have you tried reverting that patch or just skipping the calls
to btc_get_max_clock_from_voltage_dependency_table().  I think they should work
fine now that vddci is fixed.

You are receiving this mail because:
  • You are the assignee for the bug.
--1411403495.feEe4b1.1437-- --===============1895960544== 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 --===============1895960544==--