public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Alex Deucher <alexander.deucher@amd.com>
Cc: stable@vger.kernel.org, Stylon Wang <stylon.wang@amd.com>
Subject: Re: [RESEND PATCH] drm/amd/display: Fix ASSR regression on embedded panels
Date: Fri, 6 Aug 2021 08:37:27 +0200	[thread overview]
Message-ID: <YQzYpyYCCSjvjo6t@kroah.com> (raw)
In-Reply-To: <20210804164443.3279339-1-alexander.deucher@amd.com>

On Wed, Aug 04, 2021 at 12:44:43PM -0400, Alex Deucher wrote:
> From: Stylon Wang <stylon.wang@amd.com>
> 
> [Why]
> Regression found in some embedded panels traces back to the earliest
> upstreamed ASSR patch. The changed code flow are causing problems
> with some panels.
> 
> [How]
> - Change ASSR enabling code while preserving original code flow
>   as much as possible
> - Simplify the code on guarding with internal display flag
> 
> Bug: https://bugzilla.kernel.org/show_bug.cgi?id=213779
> Bug: https://gitlab.freedesktop.org/drm/amd/-/issues/1620
> Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
> Signed-off-by: Stylon Wang <stylon.wang@amd.com>
> Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
> Cc: stable@vger.kernel.org
> (cherry picked from commit 6be50f5d83adc9541de3d5be26e968182b5ac150)
> ---
> 
> This is a backport of this patch to 5.13.  I originally sent this
> out as a follow up to the reply that the original patch failed to
> apply to 5.13, but it hasn't been applied yet.  Resending to make
> sure it didn't get lost.

Not lost, just not caught up on yet.  Now queued up, thanks.

greg k-h

      reply	other threads:[~2021-08-06  6:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-04 16:44 [RESEND PATCH] drm/amd/display: Fix ASSR regression on embedded panels Alex Deucher
2021-08-06  6:37 ` Greg KH [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YQzYpyYCCSjvjo6t@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=alexander.deucher@amd.com \
    --cc=stable@vger.kernel.org \
    --cc=stylon.wang@amd.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox