Bug 99476 - Forcing perf level to high doesn't change memory clock
Summary: Forcing perf level to high doesn't change memory clock
Status: RESOLVED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/AMDgpu (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-01-20 15:10 UTC by Samuel Pitoiset
Modified: 2017-02-10 17:59 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Samuel Pitoiset 2017-01-20 15:10:18 UTC
Hi,

After changing the current performance level with:

echo high > /sys/class/drm/card0/device/power_dpm_force_performance_level

only the shader clock is updated but not the memory clock.

# cat /sys/kernel/debug/dri/0/amdgpu_pm_info

 [  mclk  ]: 300 MHz

 [  sclk  ]: 1306 MHz

# cat /sys/class/drm/card0/device/pp_dpm_sclk 
0: 300Mhz 
1: 608Mhz 
2: 910Mhz 
3: 1077Mhz 
4: 1145Mhz 
5: 1191Mhz 
6: 1236Mhz 
7: 1306Mhz *

# cat /sys/class/drm/card0/device/pp_dpm_mclk 
0: 300Mhz *
1: 1750Mhz 

Same issue if I choose the manual mode and try to echo 1 in pp_dpm_mclk.

Tested on Linux 4.8 with RX480.

Thanks!
Comment 1 Alex Deucher 2017-02-09 17:10:30 UTC
Does the firmware here help?
https://people.freedesktop.org/~agd5f/radeon_ucode/polaris/
Comment 2 Samuel Pitoiset 2017-02-10 17:59:37 UTC
This is fixed in amd-staging-4.9. I didn't test the firmwares. Looks good now.


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.