<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [amdgpu][bisected][polaris] "drm/amdgpu: refine uvd 6.0 clock gate feature" sets MCLK on highest state"
href="https://bugs.freedesktop.org/show_bug.cgi?id=98821#c7">Comment # 7</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [amdgpu][bisected][polaris] "drm/amdgpu: refine uvd 6.0 clock gate feature" sets MCLK on highest state"
href="https://bugs.freedesktop.org/show_bug.cgi?id=98821">bug 98821</a>
from <span class="vcard"><a class="email" href="mailto:arek.rusi@gmail.com" title="Arek Ruśniak <arek.rusi@gmail.com>"> <span class="fn">Arek Ruśniak</span></a>
</span></b>
<pre>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:
<a href="https://cgit.freedesktop.org/~agd5f/linux/commit/?h=drm-next-4.10-wip&id=ddfe1db18752b08d88d81cb7b661e1f982fc5d04">https://cgit.freedesktop.org/~agd5f/linux/commit/?h=drm-next-4.10-wip&id=ddfe1db18752b08d88d81cb7b661e1f982fc5d04</a>
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.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>