Comment # 38
on bug 69723
from Alexandre Demers
A couple of observations. I've forced power state to performance and performance state to high. Here is the result: [root@Xander device]# more /sys/kernel/debug/dri/64/radeon_pm_info uvd vclk: 0 dclk: 0 power level 2 sclk: 83000 mclk: 130000 vddc: 1060 vddci: 1150 Now, keeping this configuration, I launched a video relying on UVD. The result downclocks the core clock from 830 (probably limited to 800 as we know) to 725. [root@Xander device]# more /sys/kernel/debug/dri/64/radeon_pm_info uvd vclk: 54000 dclk: 40000 power level 2 sclk: 72500 mclk: 130000 vddc: 1060 vddci: 1150 However, if I don't force this power and performance states combination (letting it as balanced and auto or performance and auto), I have the following: [root@Xander device]# more /sys/kernel/debug/dri/64/radeon_pm_info uvd vclk: 54000 dclk: 40000 power level 0 sclk: 50000 mclk: 130000 vddc: 1000 vddci: 1150 [root@Xander device]# more /sys/kernel/debug/dri/64/radeon_pm_info uvd vclk: 54000 dclk: 40000 power level 2 sclk: 72500 mclk: 130000 vddc: 1060 vddci: 1150 As you can see, it will adapt to the needed performance state. - So, first question: is it expected to see a lowered sclk when UVD is active? - Second one: when the performance is changed automatically (auto), could we be triggering a performance state change too quickly? - Third one: it was previously said mclk is tied to vddci AND vddc. Wouldn't there be a chance we could encounter a problem here if vddc=1000 and not 1060 when running at full speed? - Last one: is there a way to monitor the GPU temperature and/or the GPU fan speed? (even at full speed when highly solicited, the fan is not running as fast as when dpm=0. I'm wondering if I'm not overheating from time to time).
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
