From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 106188] Can't successfully set pstates in pp_od_clk_voltage
Date: Fri, 27 Apr 2018 18:45:49 +0000 [thread overview]
Message-ID: <bug-106188-502-fdW0BE18Qg@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-106188-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1415 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=106188
--- Comment #4 from tempel.julian@gmail.com ---
Ok, it's simple. To unlock higher clocks, I simply have to set
"/sys/class/drm/card0/device/pp_sclk_od" as well.
To sum up: For my 1209MHz 900mV I have to do the following:
echo "2" > /sys/class/drm/card0/device/pp_sclk_od
echo "s 7 1209 900" > /sys/class/drm/card0/device/pp_od_clk_voltage
echo "c" > /sys/class/drm/card0/device/pp_od_clk_voltage
Works like a charm, thanks for the "Wattman" functionality!
However, I am still not able to raise the maximum allowed power consumption of
the GPU.
It's clear that "/sys/class/drm/card0/device/hwmon/hwmon0/power1_cap" sets the
actual power limit and thus I need to raise it. But the problem is:
- I can't set it higher than power1_cap_max, only values below work.
- power1_cap_max equals to power1_cap, so raising power consumption is actually
completely forbidden
- Despite of being root, I don't have write access to power1_cap_max, unlike to
power1_cap
So, it seems I'm being stuck and there is no way of increasing allowed maximum
power consumption, which is not a problem with Wattman on Windows.
I suppose either I'm missing a boot parameter to unlock write access to
power1_cap_max, or there might be a bug in amdgpu driver.
Any help appreciated.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2259 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-04-27 18:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-23 12:49 [Bug 106188] Can't successfully set pstates in pp_od_clk_voltage bugzilla-daemon
2018-04-23 15:04 ` bugzilla-daemon
2018-04-23 16:12 ` bugzilla-daemon
2018-04-23 16:39 ` bugzilla-daemon
2018-04-27 18:45 ` bugzilla-daemon [this message]
2018-04-29 18:43 ` bugzilla-daemon
2018-05-08 22:18 ` 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-106188-502-fdW0BE18Qg@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox