All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 98821] [amdgpu][bisected][polaris] "drm/amdgpu: refine uvd 6.0 clock gate feature" sets MCLK on highest state
Date: Tue, 22 Nov 2016 20:31:50 +0000	[thread overview]
Message-ID: <bug-98821-502-htgbVPHEGz@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-98821-502@http.bugs.freedesktop.org/>


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

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

--- Comment #1 from Alex Deucher <alexdeucher@gmail.com> ---
Can you clarify the situation a bit?  I take it there are two issues?

With commit:
drm/amdgpu: refine uvd 6.0 clock gate feature
does the mclk always stay high?  With this reverted does it go up and down on
demand?  Is this just an issue with two monitors attached?  Do you also see it
with only one monitor attached?

With commit:
drm/amdgpu:impl vgt_flush for VI(V5)
is the mclk always stuck in low?  Do you not see to adjusting on the fly based
on load?

Please use /sys/kernel/debug/dri/64/amdgpu_pm_info to verify the clocks at
runtime.

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

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

  reply	other threads:[~2016-11-22 20:31 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-22 20:11 [Bug 98821] [amdgpu][bisected][polaris] "drm/amdgpu: refine uvd 6.0 clock gate feature" sets MCLK on highest state bugzilla-daemon
2016-11-22 20:31 ` bugzilla-daemon [this message]
2016-11-22 21:11 ` bugzilla-daemon
2016-11-22 21:11 ` bugzilla-daemon
2016-11-22 21:12 ` bugzilla-daemon
2016-11-22 21:33 ` bugzilla-daemon
2016-11-22 21:35 ` bugzilla-daemon
2016-11-22 21:36 ` bugzilla-daemon
2016-11-22 21:41 ` bugzilla-daemon
2016-11-23 15:50 ` bugzilla-daemon
2016-11-23 17:03 ` bugzilla-daemon
2016-11-23 17:54 ` bugzilla-daemon
2016-11-23 17:55 ` bugzilla-daemon
2016-11-23 19:05 ` bugzilla-daemon
2016-11-23 19:32 ` bugzilla-daemon
2016-11-25  9:55 ` bugzilla-daemon
2016-11-28 22:59 ` bugzilla-daemon
2016-11-28 23:05 ` bugzilla-daemon
2016-11-28 23:15 ` bugzilla-daemon
2016-11-28 23:27 ` 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-98821-502-htgbVPHEGz@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.