From: sashiko-bot@kernel.org
To: "Xiao Lu" <xiaolu.xie@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v7 1/2] drm/dp/mst: recognize DP-to-HDMI PCON as virtual DPCD in DP-to-DP topology
Date: Wed, 09 Sep 2026 04:20:45 +0000 [thread overview]
Message-ID: <20260909042046.118FB1F00A3A@smtp.kernel.org> (raw)
In-Reply-To: <20260909041041.244531-1-xiaolu.xie@intel.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] drm_dp_mst_is_virtual_dpcd() unconditionally accepts DP_PEER_DEVICE_DP_LEGACY_CONV as a virtual DPCD without checking for a non-zero DPCD revision.
--
commit 7fdc1d351cc143b9e4d9acdb9eabc2fbc5bb1fee
Author: Xiao Lu <xiaolu.xie@intel.com>
drm/dp/mst: recognize DP-to-HDMI PCON as virtual DPCD in DP-to-DP topology
This commit attempts to correctly identify DP-to-HDMI PCON devices as having
a virtual DPCD within DP-to-DP topologies. It updates the peer device check
to accept legacy converters as valid downstream peer types.
> diff --git a/drivers/gpu/drm/display/drm_dp_mst_topology.c b/drivers/gpu/drm/display/drm_dp_mst_topology.c
> --- a/drivers/gpu/drm/display/drm_dp_mst_topology.c
> +++ b/drivers/gpu/drm/display/drm_dp_mst_topology.c
[ ... ]
> @@ -6047,7 +6047,8 @@ static bool drm_dp_mst_is_virtual_dpcd(struct drm_dp_mst_port *port)
> port->mstb &&
> port->mstb->num_ports == 2) {
> list_for_each_entry(downstream_port, &port->mstb->ports, next) {
> - if (downstream_port->pdt == DP_PEER_DEVICE_SST_SINK &&
> + if ((downstream_port->pdt == DP_PEER_DEVICE_SST_SINK ||
> + downstream_port->pdt == DP_PEER_DEVICE_DP_LEGACY_CONV) &&
> !downstream_port->input) {
[Severity: High]
Does this code also need to check for a non-zero DPCD revision?
The commit message specifies that PCON devices indicating a virtual DPCD
advertise DP_PEER_DEVICE_DP_LEGACY_CONV with a non-zero DPCD_Revision (VESA
SCR Option 2). However, this new condition accepts any downstream port with
the legacy converter peer type without verifying that
downstream_port->dpcd_rev != 0.
Standard legacy converters (like DP-to-VGA or standard DP-to-HDMI adapters)
with an internal MST branch will typically have a DPCD revision of 0. By
omitting the dpcd_rev != 0 check, these standard legacy converters might be
falsely identified as having a virtual DPCD.
If this happens, drm_dp_mst_dsc_aux_for_port() treats the adapter as having
a virtual DPCD and attempts a remote DPCD read on the legacy port. Since
the legacy port has no virtual DPCD, the remote DPCD read receives a NAK
and returns -EIO, causing drm_dp_mst_dsc_aux_for_port() to return NULL and
potentially disable DSC for the port entirely.
> mutex_unlock(&port->mgr->lock);
> return true;
> }
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260909041041.244531-1-xiaolu.xie@intel.com?part=1
next prev parent reply other threads:[~2026-09-09 4:20 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-06 9:41 [PATCH v4] drm/i915/dp: enable DSC passthrough for HDMI 2.1 PCON devices Xiao Lu
2026-09-06 10:00 ` sashiko-bot
2026-09-06 10:23 ` ✓ i915.CI.BAT: success for drm/i915/dp: enable DSC passthrough for HDMI 2.1 PCON devices (rev4) Patchwork
2026-09-06 12:28 ` ✗ i915.CI.Full: failure " Patchwork
2026-09-07 4:41 ` [PATCH v5 1/2] drm/dp/mst: recognize DP-to-HDMI PCON as virtual DPCD in DP-to-DP topology Xiao Lu
2026-09-07 4:41 ` [PATCH v5 2/2] drm/i915/dp: enable DSC passthrough for HDMI 2.1 PCON devices Xiao Lu
2026-09-07 4:56 ` sashiko-bot
2026-09-07 4:53 ` [PATCH v5 1/2] drm/dp/mst: recognize DP-to-HDMI PCON as virtual DPCD in DP-to-DP topology sashiko-bot
2026-09-07 4:44 ` [PATCH v5 0/2] drm/i915/dp: enable DSC passthrough for HDMI 2.1 PCON devices Xiao Lu
2026-09-07 4:44 ` [PATCH v5 1/2] drm/dp/mst: recognize DP-to-HDMI PCON as virtual DPCD in DP-to-DP topology Xiao Lu
2026-09-07 4:54 ` sashiko-bot
2026-09-07 4:44 ` [PATCH v5 2/2] drm/i915/dp: enable DSC passthrough for HDMI 2.1 PCON devices Xiao Lu
2026-09-07 5:04 ` sashiko-bot
2026-09-09 3:35 ` [PATCH v6 1/2] drm/dp/mst: recognize DP-to-HDMI PCON as virtual DPCD in DP-to-DP topology Xiao Lu
2026-09-09 3:35 ` [PATCH v6 2/2] drm/i915/dp: enable DSC passthrough for HDMI 2.1 PCON devices Xiao Lu
2026-09-09 3:47 ` sashiko-bot
2026-09-09 4:10 ` [PATCH v7 1/2] drm/dp/mst: recognize DP-to-HDMI PCON as virtual DPCD in DP-to-DP topology Xiao Lu
2026-09-09 4:10 ` [PATCH v7 2/2] drm/i915/dp: enable DSC passthrough for HDMI 2.1 PCON devices Xiao Lu
2026-09-09 4:21 ` sashiko-bot
2026-09-09 5:13 ` [PATCH v8] " Xiao Lu
2026-09-09 5:29 ` sashiko-bot
2026-09-09 5:42 ` [PATCH v9] " Xiao Lu
2026-09-09 5:57 ` sashiko-bot
2026-09-09 4:20 ` sashiko-bot [this message]
2026-09-07 6:30 ` ✓ i915.CI.BAT: success for drm/i915/dp: enable DSC passthrough for HDMI 2.1 PCON devices (rev7) Patchwork
2026-09-07 11:33 ` ✓ i915.CI.Full: " Patchwork
2026-09-09 3:50 ` ✗ Fi.CI.BUILD: failure for drm/i915/dp: enable DSC passthrough for HDMI 2.1 PCON devices (rev9) Patchwork
2026-09-09 4:24 ` ✗ Fi.CI.BUILD: failure for drm/i915/dp: enable DSC passthrough for HDMI 2.1 PCON devices (rev11) Patchwork
2026-09-09 6:01 ` ✓ i915.CI.BAT: success for drm/i915/dp: enable DSC passthrough for HDMI 2.1 PCON devices (rev12) Patchwork
2026-09-09 6:36 ` ✓ i915.CI.BAT: success for drm/i915/dp: enable DSC passthrough for HDMI 2.1 PCON devices (rev13) Patchwork
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=20260909042046.118FB1F00A3A@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=xiaolu.xie@intel.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