From: "Kazlauskas, Nicholas" <nicholas.kazlauskas@amd.com>
To: Aurabindo Pillai <aurabindo.pillai@amd.com>,
amd-gfx@lists.freedesktop.org
Cc: aurabindo.pilai@amd.com, Bhawanpreet.Lakha@amd.com, Eryk.Brol@amd.com
Subject: Re: [PATCH] drm/amd/display: Clear dc remote sinks on MST disconnect
Date: Thu, 26 Nov 2020 09:35:54 -0500 [thread overview]
Message-ID: <ab9f847e-d819-7ff0-f677-c2ee5587b2ae@amd.com> (raw)
In-Reply-To: <20201126143105.32016-1-aurabindo.pillai@amd.com>
On 2020-11-26 9:31 a.m., Aurabindo Pillai wrote:
> [Why&How]
> Recent changes to upstream mst code remove the callback which
> cleared the internal state for mst. Move the missing functionality
> that was previously called through the destroy call back for mst connector
> destroy
>
> Signed-off-by: Aurabindo Pillai <aurabindo.pillai@amd.com>
> Signed-off-by: Eryk Brol <eryk.brol@amd.com>
> ---
> .../amd/display/amdgpu_dm/amdgpu_dm_helpers.c | 22 +++++++++++++++++--
> drivers/gpu/drm/amd/display/dc/dm_helpers.h | 2 +-
> 2 files changed, 21 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_helpers.c b/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_helpers.c
> index b7d7ec3ba00d..d8b0f07deaf2 100644
> --- a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_helpers.c
> +++ b/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_helpers.c
> @@ -418,9 +418,10 @@ bool dm_helpers_dp_mst_start_top_mgr(
>
> void dm_helpers_dp_mst_stop_top_mgr(
> struct dc_context *ctx,
> - const struct dc_link *link)
> + struct dc_link *link)
> {
> struct amdgpu_dm_connector *aconnector = link->priv;
> + uint8_t i;
>
> if (!aconnector) {
> DRM_ERROR("Failed to find connector for link!");
> @@ -430,8 +431,25 @@ void dm_helpers_dp_mst_stop_top_mgr(
> DRM_INFO("DM_MST: stopping TM on aconnector: %p [id: %d]\n",
> aconnector, aconnector->base.base.id);
>
> - if (aconnector->mst_mgr.mst_state == true)
> + if (aconnector->mst_mgr.mst_state == true) {
> drm_dp_mst_topology_mgr_set_mst(&aconnector->mst_mgr, false);
> +
> + for (i = 0; i < MAX_SINKS_PER_LINK; i++) {
> + if (link->remote_sinks[i] == NULL)
> + continue;
> +
> + if (link->remote_sinks[i]->sink_signal ==
> + SIGNAL_TYPE_DISPLAY_PORT_MST) {
> + dc_link_remove_remote_sink(link, link->remote_sinks[i]);
In general I think this patch looks fine, and you can have the:
Reviewed-by: Nicholas Kazlauskas <nicholas.kazlauskas@amd.com>
But I think that this loop is redundant - dc_link_remove_remote_sink
should be removing all the remote sinks. Not sure if remote_sinks can
start at an index other than 0 though.
Regards,
Nicholas Kazlauskas
> +
> + if (aconnector->dc_sink) {
> + dc_sink_release(aconnector->dc_sink);
> + aconnector->dc_sink = NULL;
> + aconnector->dc_link->cur_link_settings.lane_count = 0;
> + }
> + }
> + }
> + } > }
>
> bool dm_helpers_dp_read_dpcd(
> diff --git a/drivers/gpu/drm/amd/display/dc/dm_helpers.h b/drivers/gpu/drm/amd/display/dc/dm_helpers.h
> index b2cd8491c707..07e349b1067b 100644
> --- a/drivers/gpu/drm/amd/display/dc/dm_helpers.h
> +++ b/drivers/gpu/drm/amd/display/dc/dm_helpers.h
> @@ -113,7 +113,7 @@ bool dm_helpers_dp_mst_start_top_mgr(
>
> void dm_helpers_dp_mst_stop_top_mgr(
> struct dc_context *ctx,
> - const struct dc_link *link);
> + struct dc_link *link);
> /**
> * OS specific aux read callback.
> */
>
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
next prev parent reply other threads:[~2020-11-26 14:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-26 14:31 [PATCH] drm/amd/display: Clear dc remote sinks on MST disconnect Aurabindo Pillai
2020-11-26 14:35 ` Kazlauskas, Nicholas [this message]
2020-11-26 14:44 ` Harry Wentland
2020-11-26 16:05 ` Aurabindo Pillai
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=ab9f847e-d819-7ff0-f677-c2ee5587b2ae@amd.com \
--to=nicholas.kazlauskas@amd.com \
--cc=Bhawanpreet.Lakha@amd.com \
--cc=Eryk.Brol@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=aurabindo.pilai@amd.com \
--cc=aurabindo.pillai@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