All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 110777] Kernel 5.1-5.2 MCLK stuck at 167MHz Vega 10 (56)
Date: Mon, 03 Jun 2019 18:55:18 +0000	[thread overview]
Message-ID: <bug-110777-502-jWBiW7nol5@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-110777-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 680 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=110777

--- Comment #3 from antonh@gmx.de ---
reverting the following two patches fixes the boost in memory clocks but it
seems once mem clock has ramped up it's not going down again.

1.
Revert "drm/amd/powerplay: update soc boot and max level on vega10"   
This reverts commit 373e87fc91527124cb8ec21465a6d070a65c56af.

2.
Revert "drm/amd/powerplay: support Vega10 SOCclk and DCEFclk dpm level
settings"
This reverts commit bb05821b13fa0c0b97760cb292b30d3105d65954.

Evan Quan <evan.quan@amd.com>
Alex Deucher <alexander.deucher@amd.com>

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1563 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

  parent reply	other threads:[~2019-06-03 18:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-27 17:56 [Bug 110777] Kernel 5.1-5.2 MCLK stuck at 167MHz Vega 10 (56) bugzilla-daemon
2019-06-02 17:40 ` bugzilla-daemon
2019-06-03 18:41 ` bugzilla-daemon
2019-06-03 18:55 ` bugzilla-daemon [this message]
2019-06-03 19:21 ` bugzilla-daemon
2019-06-05 17:44 ` bugzilla-daemon
2019-06-11 17:04 ` 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-110777-502-jWBiW7nol5@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.