From: Sasha Levin <sashal@kernel.org>
To: Mario Limonciello <mario.limonciello@amd.com>
Cc: stable@vger.kernel.org, Cruise Hung <Cruise.Hung@amd.com>,
Wenjing Liu <Wenjing.Liu@amd.com>,
Qingqing Zhuo <qingqing.zhuo@amd.com>,
Daniel Wheeler <daniel.wheeler@amd.com>,
Alex Deucher <alexander.deucher@amd.com>
Subject: Re: [PATCH 6.2.y/6.1.y 1/1] drm/amd/display: Fix DP MST sinks removal issue
Date: Fri, 24 Mar 2023 20:43:57 -0400 [thread overview]
Message-ID: <ZB5DzbW6Kz3Sx7W4@sashalap> (raw)
In-Reply-To: <20230322220841.898-2-mario.limonciello@amd.com>
On Wed, Mar 22, 2023 at 05:08:41PM -0500, Mario Limonciello wrote:
>From: Cruise Hung <Cruise.Hung@amd.com>
>
>[Why]
>In USB4 DP tunneling, it's possible to have this scenario that
>the path becomes unavailable and CM tears down the path a little bit late.
>So, in this case, the HPD is high but fails to read any DPCD register.
>That causes the link connection type to be set to sst.
>And not all sinks are removed behind the MST branch.
>
>[How]
>Restore the link connection type if it fails to read DPCD register.
>
>Cc: stable@vger.kernel.org
>Cc: Mario Limonciello <mario.limonciello@amd.com>
>Reviewed-by: Wenjing Liu <Wenjing.Liu@amd.com>
>Acked-by: Qingqing Zhuo <qingqing.zhuo@amd.com>
>Signed-off-by: Cruise Hung <Cruise.Hung@amd.com>
>Tested-by: Daniel Wheeler <daniel.wheeler@amd.com>
>Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
>(cherry picked from commit cbd6c1b17d3b42b7935526a86ad5f66838767d03)
>Modified for stable backport as a lot of the code in this file was moved
>in 6.3 to drivers/gpu/drm/amd/display/dc/link/link_detection.c.
>Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
Queued up, thanks!
--
Thanks,
Sasha
prev parent reply other threads:[~2023-03-25 0:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-22 22:08 [PATCH 6.2.y/6.1.y 0/1] Fixed stable backport for USB4 CM issue Mario Limonciello
2023-03-22 22:08 ` [PATCH 6.2.y/6.1.y 1/1] drm/amd/display: Fix DP MST sinks removal issue Mario Limonciello
2023-03-25 0:43 ` Sasha Levin [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=ZB5DzbW6Kz3Sx7W4@sashalap \
--to=sashal@kernel.org \
--cc=Cruise.Hung@amd.com \
--cc=Wenjing.Liu@amd.com \
--cc=alexander.deucher@amd.com \
--cc=daniel.wheeler@amd.com \
--cc=mario.limonciello@amd.com \
--cc=qingqing.zhuo@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).