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 21:41:34 +0000	[thread overview]
Message-ID: <bug-98821-502-lxYAMKa1uN@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-98821-502@http.bugs.freedesktop.org/>


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

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

--- Comment #8 from Alex Deucher <alexdeucher@gmail.com> ---
(In reply to Arek Ruśniak from comment #7)
> Alex I use something like that:
> watch -n 1 -c "cat /sys/kernel/debug/dri/0/amdgpu_pm_info"
> combined with 
> vblank_mode=0 glxgears
> it should set mclk on fire IIRC, but it was still 300MHz, bisecting gives me:
> https://cgit.freedesktop.org/~agd5f/linux/commit/?h=drm-next-4.10-
> wip&id=ddfe1db18752b08d88d81cb7b661e1f982fc5d04
> 


I doubt regular sized gears will generate enough memory load to raise the mclk.
 Does it work if you try:
vblank_mode=0 glxgears -fullscreen
Or try some more demanding app.

> but when I've tested (in the bisecting proces) commit [1] I saw that mclk i
> set always on 2000MHz... and this is first commit (I checked +/- 1) when is
> set on HIGH no matter what.
> 
> So yes, this are two issues in one I believe because revert
> 1b7eab1f8346ab3b8e4fc54882306340a84497a8 fixes them all.

Also does the number of displays attached change the behavior?  When you say
fix, do you mean mclk stays high, or changes dynamically?

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

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

  parent reply	other threads:[~2016-11-22 21:41 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
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 [this message]
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-lxYAMKa1uN@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.