From: "Christian König" <deathsimple@vodafone.de>
To: Alex Deucher <alexdeucher@gmail.com>,
Alexandre Demers <alexandre.f.demers@gmail.com>
Cc: dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH 00/22] new radeon info queries
Date: Thu, 02 Oct 2014 14:41:06 +0200 [thread overview]
Message-ID: <542D47E2.2010304@vodafone.de> (raw)
In-Reply-To: <CADnq5_MaYAymkg+==T=xsmweHfuG1Os_zL+qcHOAaPiJjXB31g@mail.gmail.com>
Am 02.10.2014 um 06:50 schrieb Alex Deucher:
> On Wed, Oct 1, 2014 at 12:30 PM, Alexandre Demers
> <alexandre.f.demers@gmail.com> wrote:
>> May I suggest something more to add if available? It would be great to
>> have the core and memory voltages. As an example of a specific
>> application where it would have been usefull: it would have been
>> easier to debug the problem with Cayman when vddci was not correctly
>> set (it would have been higher or lower than expected or the value
>> would have been nonsense).
> It wouldn't have helped for that problem since there's no way to query
> the actual vddc or vddci or even the clocks. All you can query is
> which performance level is active, the driver has to determine the
> clocks and voltages based on that. It's basically the same info that
> is already exposed via debugfs.
I hoped we could expose the PLL test registers as well, this way
somebody could actually measure at least the clocks instead of just
calculating them from the PM profile in use.
Christian.
>
> Alex
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2014-10-02 12:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-01 16:30 [PATCH 00/22] new radeon info queries Alexandre Demers
2014-10-02 4:50 ` Alex Deucher
2014-10-02 12:41 ` Christian König [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-10-01 15:38 Alex Deucher
2014-12-21 20:05 ` Siavash Eliasi
2014-12-22 17:01 ` Alex Deucher
2014-12-23 4:44 ` Siavash Eliasi
2015-02-24 22:09 ` Marek Olšák
2015-02-24 22:51 ` Alex Deucher
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=542D47E2.2010304@vodafone.de \
--to=deathsimple@vodafone.de \
--cc=alexandre.f.demers@gmail.com \
--cc=alexdeucher@gmail.com \
--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.