From: Greg KH <gregkh@linuxfoundation.org>
To: Aurabindo Pillai <aurabindo.pillai@amd.com>
Cc: stable@vger.kernel.org, Martin Tsai <martin.tsai@amd.com>,
Robin Chen <robin.chen@amd.com>,
Daniel Wheeler <daniel.wheeler@amd.com>,
Alex Deucher <alexander.deucher@amd.com>
Subject: Re: [PATCH 6.1.y] drm/amd/display: should support dmub hw lock on Replay
Date: Mon, 24 Mar 2025 11:34:04 -0700 [thread overview]
Message-ID: <2025032452-tarantula-encircle-6fd3@gregkh> (raw)
In-Reply-To: <20250324164929.2622811-1-aurabindo.pillai@amd.com>
On Mon, Mar 24, 2025 at 12:49:29PM -0400, Aurabindo Pillai wrote:
> From: Martin Tsai <martin.tsai@amd.com>
>
> [Why]
> Without acquiring DMCUB hw lock, a race condition is caused with
> Panel Replay feature, which will trigger a hang. Indicate that a
> lock is necessary to prevent this when replay feature is enabled.
>
> [How]
> To allow dmub hw lock on Replay.
>
> Reviewed-by: Robin Chen <robin.chen@amd.com>
> Signed-off-by: Aurabindo Pillai <aurabindo.pillai@amd.com>
> Signed-off-by: Martin Tsai <martin.tsai@amd.com>
> Tested-by: Daniel Wheeler <daniel.wheeler@amd.com>
> Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
> (cherry picked from commit bfeefe6ea5f18cabb8fda55364079573804623f9)
> ---
> drivers/gpu/drm/amd/display/dc/dce/dmub_hw_lock_mgr.c | 3 +++
> 1 file changed, 3 insertions(+)
Does not apply to the tree at all :(
next prev parent reply other threads:[~2025-03-24 18:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-24 16:20 FAILED: patch "[PATCH] drm/amd/display: should support dmub hw lock on Replay" failed to apply to 6.1-stable tree gregkh
2025-03-24 16:49 ` [PATCH 6.1.y] drm/amd/display: should support dmub hw lock on Replay Aurabindo Pillai
2025-03-24 18:34 ` Greg KH [this message]
2025-03-24 19:06 ` Pillai, Aurabindo
2025-03-25 11:33 ` Sasha Levin
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=2025032452-tarantula-encircle-6fd3@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=alexander.deucher@amd.com \
--cc=aurabindo.pillai@amd.com \
--cc=daniel.wheeler@amd.com \
--cc=martin.tsai@amd.com \
--cc=robin.chen@amd.com \
--cc=stable@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.