Bug 72602

Summary: [REGRESSION] r600 cayman: forced performance level gets reset to auto when playing a video with vdpau
Product: DRI Reporter: Harald Judt <h.judt>
Component: DRM/RadeonAssignee: Default DRI bug account <dri-devel>
Status: RESOLVED WONTFIX QA Contact:
Severity: normal    
Priority: medium    
Version: XOrg git   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:

Description Harald Judt 2013-12-11 16:36:54 UTC 
Steps to reproduce:
1) echo low > /sys/class/drm/card0/device/power_dpm_force_performance_level
2) cat /sys/class/drm/card0/device/power_dpm_force_performance_level
   low
3) start playing a video (vdpau)
4) cat /sys/class/drm/card0/device/power_dpm_force_performance_level
   auto

Interestingly, I can repeat step 1 now and the video will play correctly, with the value staying at "low". So it seems this occurs only when initializing video playback (vdpau).

This started happening with kernel 3.12.0 or a rc. It did not get reset with <=3.11.8.
Comment 1 Alex Deucher 2013-12-11 16:42:10 UTC 
This is the expected behavior in kernels 3.11-3.12.  The user preference is retained in 3.13.
Comment 2 Harald Judt 2013-12-11 16:49:19 UTC 
Will it suffice to cherry-pick http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=14ac88af156efcefac9ba3cf249ae84f9ff71d37 to get that behaviour in 3.12?
Comment 3 Alex Deucher 2013-12-11 16:54:19 UTC 
(In reply to comment #2)
> Will it suffice to cherry-pick
> http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/
> ?id=14ac88af156efcefac9ba3cf249ae84f9ff71d37 to get that behaviour in 3.12?

I think that should do it.  I don't remember if there are any dependencies on previous patches.
Comment 4 Harald Judt 2013-12-11 17:09:26 UTC 
Thanks, that indeed did it. It required http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=0a17af373c61b4ded44a2cbac62c05ae5dad2106 too for the patch to apply.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.