From: Sylvain BERTRAND <sylware@legeek.net>
To: dri-devel@lists.freedesktop.org
Subject: atombios powerplay cac table
Date: Thu, 7 Nov 2013 04:57:21 +0100 [thread overview]
Message-ID: <20131107035721.GA4330@freedom> (raw)
Hi,
Which GPU generations/families do use the "new" powerplay CAC
table, defined when the atombios platform capabilities have the
ATOM_PP_PLATFORM_CAP_NEW_CAC_VOLTAGE flag?
----
On drm-next-3.13 branch, commit
70471860ff9f335c60c004d42ebd48945bfa5403, I noticed the
following:
For the "new" power CAC table, there is a relationship with the
table defining the link between vddc and the engine
clock. My tahiti based board does use the "old" cac table, but I
noticed the use of a virtual value (0xff??) for vddc in the vddc dependency
on engine clock table which is not translated to a real voltage
value.
This is found in si_dpm.c, si_get_std_voltage_value function.
Would that would explain why there are 2 lookup loops in
si_get_std_voltage_value function? (one looking for the exact
value, the other one seems to be a trick to deal with
untranslated virtual voltage).
regards,
--
Sylvain
next reply other threads:[~2013-11-07 3:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-07 3:57 Sylvain BERTRAND [this message]
2013-11-12 16:29 ` atombios powerplay cac table Sylvain BERTRAND
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=20131107035721.GA4330@freedom \
--to=sylware@legeek.net \
--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