AMD-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Wayne Lin <Wayne.Lin@amd.com>
To: <amd-gfx@lists.freedesktop.org>, <dri-devel@lists.freedesktop.org>
Cc: <lyude@redhat.com>, <jani.nikula@intel.com>,
	<imre.deak@intel.com>, <daniel@ffwll.ch>,
	<Harry.Wentland@amd.com>, <jerry.zuo@amd.com>,
	Wayne Lin <Wayne.Lin@amd.com>
Subject: [PATCH 0/3] Fix mst daisy chain light up issue after resume
Date: Wed, 26 Jun 2024 16:48:22 +0800	[thread overview]
Message-ID: <20240626084825.878565-1-Wayne.Lin@amd.com> (raw)

Under DP mst daisy chain configuration, unplug one chained monitor
during suspend and then resume, observe left connected monitor not
light up. After analyzing, seems it's due to changing dpcd
DP_MSTM_CTRL value after LT during reume.

We used to defer handling UP request by disabling DP_UP_REQ_EN at the
begining of resume process to avoid some problems. However, it turns
out that it will cause problem on the hub if we change DP_UP_REQ_EN
after LT. This series is trying to solve the problem by another way
that we don't explicitly disable DP_UP_REQ_EN at source side. Instead,
source should ignore the CSN event before source completeting topology
probing during resume.

Wayne Lin (3):
  drm/dp_mst: Fix all mstb marked as not probed after suspend/resume
  drm/dp_mst: Skip CSN if topology probing is not done yet
  drm/amd/display: Solve mst monitors blank out problem after resume

 drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c |  3 ++-
 drivers/gpu/drm/display/drm_dp_mst_topology.c     | 15 +++++++++++++--
 2 files changed, 15 insertions(+), 3 deletions(-)

-- 
2.37.3


             reply	other threads:[~2024-06-26  8:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-26  8:48 Wayne Lin [this message]
2024-06-26  8:48 ` [PATCH 1/3] drm/dp_mst: Fix all mstb marked as not probed after suspend/resume Wayne Lin
2024-06-26 16:22   ` Lyude Paul
2024-06-26  8:48 ` [PATCH 2/3] drm/dp_mst: Skip CSN if topology probing is not done yet Wayne Lin
2024-06-26 16:20   ` Lyude Paul
2024-06-27  9:04     ` Lin, Wayne
2024-06-28 17:40       ` Lyude Paul
2024-07-03  8:13         ` Lin, Wayne
2024-07-03 13:51           ` Lyude Paul
2024-06-26  8:48 ` [PATCH 3/3] drm/amd/display: Solve mst monitors blank out problem after resume Wayne Lin
2024-07-03 14:06   ` Zuo, Jerry

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=20240626084825.878565-1-Wayne.Lin@amd.com \
    --to=wayne.lin@amd.com \
    --cc=Harry.Wentland@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=imre.deak@intel.com \
    --cc=jani.nikula@intel.com \
    --cc=jerry.zuo@amd.com \
    --cc=lyude@redhat.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