MIME-Version: 1.0
References: <CAPM=9twnYJ8SrVzJEEH+Vksibomvk5CE+Nn6BXKYwLG_8r=GJQ@mail.gmail.com>
In-Reply-To: <CAPM=9twnYJ8SrVzJEEH+Vksibomvk5CE+Nn6BXKYwLG_8r=GJQ@mail.gmail.com>
From:   Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri, 7 Jan 2022 09:41:58 -0800
Message-ID: <CAHk-=wiyfiVoci-LHaY=e70zOpAoUqwoaFF4iD3xm847PkK1CQ@mail.gmail.com>
Subject: Re: [git pull] drm final fixes for 5.16
To:     Dave Airlie <airlied@gmail.com>,
        Alex Deucher <alexdeucher@gmail.com>
Cc:     Daniel Vetter <daniel.vetter@ffwll.ch>,
        dri-devel <dri-devel@lists.freedesktop.org>,
        LKML <linux-kernel@vger.kernel.org>
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

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