Radeon DRM: Dynamic Power Management Updates
Phoronix: Radeon DRM: Dynamic Power Management Updates
The DRM pull request has yet to be submitted for the Linux 3.11 kernel and already there is another revision to the Radeon DRM kernel driver to be submitted. This latest Radeon DRM work provides additional dynamic power management fixes and some new sysfs features...
Alex, two questions for ya. One related to this and one general radeon question.
Related question: I know an AMD dev made a comment at one point that said that catalyst PM code was larger than all of Mesa totalled....lovely. What's the hopes for this code drop? I'm not really expecting almost identical power usage between radeon and catalyst after 3.11, but in your tests is it comparable at least? Not trying to bash the work, even if all this did was automatically jump between 'low' 'medium' 'high' power profiles based upon load that would still be an improvement over the status quo, so its definitely appreciated. I'm just curious what you, as the developer, would say the impact in comparison to Catalyst.
Radeon question: So 3.10 bring us UVD, 3.11 brings us DPM, Crossfire would probably require a big rework kernel side and user-side (as far as Kernel, Mesa, and X) to make work so that really just leaves one thing in my head.... How's HDMI audio coming along? Its been disabled by default since like 3.0 or 3.2, Michael did an article about how one of the devs made Radeon do the exact same steps (as far as registers go) that catalyst does and that it worked out all the problems he was having on his test machines... did those patches ever get merged? Whats the big blocker-bug for hdmi audio enabled by default?
The RV770 improvement works for me. Thanks, Alex Deucher.
As a bonus, fan speed seems to be proportional to load in the 3d_perf state - old code/firmware had it at max all the time.
Anyone know if this fixes the flickering and UVD problems on RV730?
Originally Posted by tball
First is realated to tear-free rendering (which require replacing X.org..), second is related to UVD code itself. So you will have flickering GPU with UVD problems, but which consume less power and which fan work lighter.
(Did you reported your bugs? Not about flickering unless its whole screen flickering, but about UVD?)
I don't know if you are refering to tearing, but this is not tearing. It is related to the new dpm code (I think). The flickering is coming and going, and consists of the whole screen jumping up and down.
Originally Posted by przemoli
I don't mind the UVD problems, since it is very experimental code. But the flickering renders my desktop hard to look at for too long.
Have you seen the size of the dpm patch set It should come pretty close to the closed driver savings-wise. It is pretty much on par feature-wise.
Originally Posted by Ericg
There were a number of monitors that would display blank screens with hdmi audio enabled by default. We fixed a number of bugs in the hdmi packet generation in the last couple of kernels so if all goes well in this cycle we can probably enable it.
Originally Posted by Ericg
I'm probably again using an outdated kernel (from 4th of july) but I used dynpm for a whole day and it was annoying loud, producing lots of warmth & eating energy - thus money
dynpm in that state may be perfectly suitable for gamers but for e.g. "normal" research work & while it's warm outside - it's not
it's simply too loud and disturbing concentration, furthermore energy is pretty expensive here and my appartment gets warm very fast while the gpu runs as a heater
might the fact that I'm using compiz-fusion play a role in this ?
the gpu is also running a full speed/clocking pretty high even when working on a console window in X with compositing activated
don't get me wrong: this is not to directly criticize your work - which I heavly appreciate - but to point out that under these consequences it's not suitable for all:
e.g. when using the windows 7/8 catalyst driver it's significantly more silent and only clocks up that much when running games and putting full load on the gpu
fglrx back then when I used it (last year) also was way more silent - it was noticably louder than under windows but it was still tolerable
hope there's changes - otherwise - unfortunately the only option I had would be to use static "low" performance profile
thanks for your hard work !
Umm, are you sure you're actually using the new DPM code (kernel parameter radeon.dpm=1)? dynpm is the old and useless way of doing things, dpm is the new awesome one.
Originally Posted by kernelOfTruth