Message ID | CAPM=9twnYJ8SrVzJEEH+Vksibomvk5CE+Nn6BXKYwLG_8r=GJQ@mail.gmail.com (mailing list archive) |
---|---|
State | New, archived |
Headers | show |
Series | [git,pull] drm final fixes for 5.16 | expand |
The pull request you sent on Fri, 7 Jan 2022 13:23:45 +1000:
> git://anongit.freedesktop.org/drm/drm tags/drm-fixes-2022-01-07
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/7a6043cc2e863ab45016622c30879e555523ee13
Thank you!
On Thu, Jan 6, 2022 at 7:23 PM Dave Airlie <airlied@gmail.com> wrote: > > There is only the amdgpu runtime pm regression fix in here. Thanks, from a quick test it works for me - the backlight actually does eventually go away. It does so only on the second time the monitors say "no signal, going to power save", but that has been true before too. So I think there's still some confusion in this area, but it might be elsewhere - who knows what Wayland and friends do. At least it doesn't look like a regression to me any more. Thanks, Linus
On Fri, Jan 7, 2022 at 6:42 PM Linus Torvalds <torvalds@linux-foundation.org> wrote: > > On Thu, Jan 6, 2022 at 7:23 PM Dave Airlie <airlied@gmail.com> wrote: > > > > There is only the amdgpu runtime pm regression fix in here. > > Thanks, from a quick test it works for me - the backlight actually > does eventually go away. > > It does so only on the second time the monitors say "no signal, going > to power save", but that has been true before too. > > So I think there's still some confusion in this area, but it might be > elsewhere - who knows what Wayland and friends do. At least it doesn't > look like a regression to me any more. Well it's not a true fix, just a "go back to exact old behaviour, but limited to relevant gpus for amdgpu only" so that i915 doesn't regress. I think there's some more debug to do here and Alex/Harry&team can look at leisure now :-) Cheers, Daniel