Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Mario Limonciello <mario.limonciello@amd.com>
To: gregkh@linuxfoundation.org, alex.hung@amd.com,
	alexander.deucher@amd.com, chiahsuan.chung@amd.com,
	daniel.wheeler@amd.com
Cc: stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] drm/amd/display: Use HW lock mgr for PSR1 when only one eDP" failed to apply to 6.6-stable tree
Date: Mon, 24 Mar 2025 10:52:49 -0500	[thread overview]
Message-ID: <69bf7189-358b-40ca-9b4d-60b61e1b89d7@amd.com> (raw)
In-Reply-To: <2025032441-constrain-eastbound-09d8@gregkh>

On 3/24/2025 10:37, gregkh@linuxfoundation.org wrote:
> 
> The patch below does not apply to the 6.6-stable tree.
> If someone wants it applied there, or to any other stable or longterm
> tree, then please email the backport, including the original git commit
> id to <stable@vger.kernel.org>.
> 
> To reproduce the conflict and resubmit, you may use the following commands:
> 
> git fetch https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/ linux-6.6.y
> git checkout FETCH_HEAD
> git cherry-pick -x acbf16a6ae775b4db86f537448cc466288aa307e
> # <resolve conflicts, build, test, etc.>
> git commit -s
> git send-email --to '<stable@vger.kernel.org>' --in-reply-to '2025032441-constrain-eastbound-09d8@gregkh' --subject-prefix 'PATCH 6.6.y' HEAD^..
> 
> Possible dependencies:
> 
> 
> 
> thanks,
> 
> greg k-h
> 

Hi,

Here is them missing dependency commit.  Cherry-picking this first will 
let the fix apply cleanly on 6.6.y:

commit bfeefe6ea5f1 ("drm/amd/display: should support dmub hw lock on 
Replay")

Thanks,

> ------------------ original commit in Linus's tree ------------------
> 
>  From acbf16a6ae775b4db86f537448cc466288aa307e Mon Sep 17 00:00:00 2001
> From: Mario Limonciello <mario.limonciello@amd.com>
> Date: Fri, 7 Mar 2025 15:55:20 -0600
> Subject: [PATCH] drm/amd/display: Use HW lock mgr for PSR1 when only one eDP
> 
> [WHY]
> DMUB locking is important to make sure that registers aren't accessed
> while in PSR.  Previously it was enabled but caused a deadlock in
> situations with multiple eDP panels.
> 
> [HOW]
> Detect if multiple eDP panels are in use to decide whether to use
> lock. Refactor the function so that the first check is for PSR-SU
> and then replay is in use to prevent having to look up number
> of eDP panels for those configurations.
> 
> Fixes: f245b400a223 ("Revert "drm/amd/display: Use HW lock mgr for PSR1"")
> Closes: https://gitlab.freedesktop.org/drm/amd/-/issues/3965
> Reviewed-by: ChiaHsuan Chung <chiahsuan.chung@amd.com>
> Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
> Signed-off-by: Alex Hung <alex.hung@amd.com>
> Tested-by: Daniel Wheeler <daniel.wheeler@amd.com>
> Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
> (cherry picked from commit ed569e1279a3045d6b974226c814e071fa0193a6)
> Cc: stable@vger.kernel.org
> 
> diff --git a/drivers/gpu/drm/amd/display/dc/dce/dmub_hw_lock_mgr.c b/drivers/gpu/drm/amd/display/dc/dce/dmub_hw_lock_mgr.c
> index bf636b28e3e1..6e2fce329d73 100644
> --- a/drivers/gpu/drm/amd/display/dc/dce/dmub_hw_lock_mgr.c
> +++ b/drivers/gpu/drm/amd/display/dc/dce/dmub_hw_lock_mgr.c
> @@ -69,5 +69,16 @@ bool should_use_dmub_lock(struct dc_link *link)
>   	if (link->replay_settings.replay_feature_enabled)
>   		return true;
>   
> +	/* only use HW lock for PSR1 on single eDP */
> +	if (link->psr_settings.psr_version == DC_PSR_VERSION_1) {
> +		struct dc_link *edp_links[MAX_NUM_EDP];
> +		int edp_num;
> +
> +		dc_get_edp_links(link->dc, edp_links, &edp_num);
> +
> +		if (edp_num == 1)
> +			return true;
> +	}
> +
>   	return false;
>   }
> 


  reply	other threads:[~2025-03-24 15:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-24 15:37 FAILED: patch "[PATCH] drm/amd/display: Use HW lock mgr for PSR1 when only one eDP" failed to apply to 6.6-stable tree gregkh
2025-03-24 15:52 ` Mario Limonciello [this message]
2025-03-24 15:59   ` Greg KH
2025-03-24 16:21     ` Greg KH
2025-03-24 16:23       ` Mario Limonciello

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=69bf7189-358b-40ca-9b4d-60b61e1b89d7@amd.com \
    --to=mario.limonciello@amd.com \
    --cc=alex.hung@amd.com \
    --cc=alexander.deucher@amd.com \
    --cc=chiahsuan.chung@amd.com \
    --cc=daniel.wheeler@amd.com \
    --cc=gregkh@linuxfoundation.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox