From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 110208] New GPU sysfs Power State Interface for custom pp_od_clk_voltage
Date: Wed, 20 Mar 2019 11:48:27 +0000 [thread overview]
Message-ID: <bug-110208-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1152 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=110208
Bug ID: 110208
Summary: New GPU sysfs Power State Interface for custom
pp_od_clk_voltage
Product: DRI
Version: unspecified
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/AMDgpu
Assignee: dri-devel@lists.freedesktop.org
Reporter: richard.llom@gmail.com
In order to use a custom pp_od_clk_voltage one has to set
power_dpm_force_performance_level to manual.
However this way it is not possible to use custom pp_od_clk_voltage and force -
for instance - high or peak performance levels.
The forcing of different performance levels doesn't (and shouldn't) relate to
custom clocks/voltages. Putting this setting in the same interface is a poor
choice and (unnecessarily) restricts the possibilities.
Please add a new sysfs interface for *solely* choosing between default and
custom pp_od_clk_voltage.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2443 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2019-03-20 11:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-20 11:48 bugzilla-daemon [this message]
2019-03-20 11:50 ` [Bug 110208] New GPU sysfs Power State Interface for custom pp_od_clk_voltage bugzilla-daemon
2019-11-19 9:17 ` 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-110208-502@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.