From: Wayne Lin <Wayne.Lin@amd.com>
To: <dri-devel@lists.freedesktop.org>, <amd-gfx@lists.freedesktop.org>
Cc: harry.wentland@amd.com, jerry.zuo@amd.com,
Nicholas.Kazlauskas@amd.com, Wayne Lin <Wayne.Lin@amd.com>
Subject: [PATCH 0/2] Take SST-only branch device into account
Date: Wed, 8 Jan 2020 16:44:14 +0800 [thread overview]
Message-ID: <20200108084416.6296-1-Wayne.Lin@amd.com> (raw)
Noticed this while testing 4 ports MST hub from StarTech.com.
While plugging in and display a MST monitor(Dell U2417H), change the MST
feature to off from OSD. Monitor then can't display anymore.
After analyzing, found out that the CSN reports the specific port from
Device with MST Branching Unit (Message_Capability_Status=1 &&
Peer_Device_Type=010) to SST-only Branch Device ((Message_Capability_Status=0 &&
Peer_Device_Type=010). Current code expects peer device as MST branch
device and can handle sideband message once the peer device type is
declared as Peer_Device_Type=010. But for SST-only Branch Device, its
Peer_Device_Type is 010 and can't handle sideband message. For this case,
we should follow the same handling procedure as the case in
DP_PEER_DEVICE_DP_LEGACY_CONV & DP_PEER_DEVICE_SST_SINK.
This series is trying to add the SST-only branch device case in and remain
the original processing logic in current code.
Wayne Lin (2):
drm/dp_mst: Add a function to determine the mst end device
drm/dp_mst: Handle SST-only branch device case
drivers/gpu/drm/drm_dp_mst_topology.c | 147 +++++++++++++++-----------
1 file changed, 84 insertions(+), 63 deletions(-)
--
2.17.1
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
next reply other threads:[~2020-01-08 8:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-08 8:44 Wayne Lin [this message]
2020-01-08 8:44 ` [PATCH 1/2] drm/dp_mst: Add a function to determine the mst end device Wayne Lin
2020-01-14 21:15 ` Lyude Paul
2020-01-15 2:40 ` Lin, Wayne
2020-01-08 8:44 ` [PATCH 2/2] drm/dp_mst: Handle SST-only branch device case Wayne Lin
2020-01-14 21:18 ` Lyude Paul
2020-01-15 2:43 ` Lin, Wayne
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=20200108084416.6296-1-Wayne.Lin@amd.com \
--to=wayne.lin@amd.com \
--cc=Nicholas.Kazlauskas@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=harry.wentland@amd.com \
--cc=jerry.zuo@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;
as well as URLs for NNTP newsgroup(s).