All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 205393] [amdgpu powerplay] vega10: custom pp_table, AVFS accidentally reenabled after display powersave
Date: Fri, 08 Nov 2019 10:49:13 +0000	[thread overview]
Message-ID: <bug-205393-2300-izJteAx2gG@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-205393-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=205393

--- Comment #10 from tempel.julian@gmail.com ---
I'd try out patches if you want. :)
Though it's probably not really important, as the regular overdrive
functionality works fine with Polaris.

Much more important would be situation for Navi, as regular overdrive doesn't
work with it yet and one is dependent on the powerplay table method:
https://bugs.freedesktop.org/show_bug.cgi?id=111762

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2019-11-08 10:49 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-02 21:26 [Bug 205393] New: [amdgpu powerplay] vega10: custom pp_table, AVFS accidentally reenabled after display powersave bugzilla-daemon
2019-11-04 13:58 ` [Bug 205393] " bugzilla-daemon
2019-11-04 14:02 ` bugzilla-daemon
2019-11-07 17:17 ` bugzilla-daemon
2019-11-07 18:18 ` bugzilla-daemon
2019-11-07 20:17 ` bugzilla-daemon
2019-11-07 20:39 ` bugzilla-daemon
2019-11-07 23:57 ` bugzilla-daemon
2019-11-08  0:00 ` bugzilla-daemon
2019-11-08 10:35 ` bugzilla-daemon
2019-11-08 10:49 ` bugzilla-daemon [this message]
2019-11-08 16:18 ` bugzilla-daemon
2019-11-08 17:16 ` bugzilla-daemon
2019-11-08 17:22 ` bugzilla-daemon
2019-11-08 17:25 ` bugzilla-daemon
2019-11-09  9:48 ` 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-205393-2300-izJteAx2gG@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.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.