(In reply to Alex Deucher from comment #9)
> I don't think this is a bug. The problem is, prior to that patch, the
> display component was requesting minimum clocks that were 10x too low. This
> saved power, but led to display problems on some systems because the clocks
> were too low to sustain the display requirements.
Sorry Alex,
what?
_All_ was fine _before_ this commit for ages with stable upstream and all 'amd-staging-drm-next'.
Now, I get ~60 W raised from ~30 W with 1920x1080 (even dual display was good before).
(In reply to Alex Deucher from comment #9)
> I don't think this is a bug. The problem is, prior to that patch, the
> display component was requesting minimum clocks that were 10x too low. This
> saved power, but led to display problems on some systems because the clocks
> were too low to sustain the display requirements.
Sorry Alex,
what?
_All_ was fine _before_ this commit for ages with stable upstream and all 'amd-staging- drm-next' .
Now, I get ~60 W raised from ~30 W with 1920x1080 (even dual display was good before).