From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 107143] Prime - OverDrive volt and frequency table(pp_od_clk_voltage) is reset every time on power on
Date: Fri, 06 Jul 2018 18:15:47 +0000 [thread overview]
Message-ID: <bug-107143-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1152 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=107143
Bug ID: 107143
Summary: Prime - OverDrive volt and frequency
table(pp_od_clk_voltage) is reset every time on power
on
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/AMDgpu
Assignee: dri-devel@lists.freedesktop.org
Reporter: rune@megahurts.dk
OverDrive volt and frequency table(pp_od_clk_voltage) is reset every time on
power on.
For most desktop this is not a problem since, the GPU is not powered off until
you turn off the computer.
When you use PRIME, the dGPU is powered off every time you stop using it, which
again means that next time it is powered all OverDrive table changes will be
lost.
Distro: Debian
Kernel: 4.17.3(custom)
Machine: HP ZBook 15 G4 Mobile Workstation.
CPU: i7-7700HQ
dGPU: AMD Radeon Pro WX 4150
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2451 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 reply other threads:[~2018-07-06 18:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-06 18:15 bugzilla-daemon [this message]
2018-07-26 2:01 ` [Bug 107143] Prime - OverDrive volt and frequency table(pp_od_clk_voltage) is reset every time on power on bugzilla-daemon
2019-11-19 8:43 ` 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-107143-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.