From: Suraj Kandpal <suraj.kandpal@intel.com>
To: intel-xe@lists.freedesktop.org, intel-gfx@lists.freedesktop.org
Cc: ankit.k.nautiyal@intel.com, arun.r.murthy@intel.com,
Suraj Kandpal <suraj.kandpal@intel.com>
Subject: [PATCH v2 03/10] drm/i915/dp_mst: Limit M/N ratio for MST
Date: Wed, 16 Sep 2026 08:27:03 +0530 [thread overview]
Message-ID: <20260916025710.432281-4-suraj.kandpal@intel.com> (raw)
In-Reply-To: <20260916025710.432281-1-suraj.kandpal@intel.com>
From: Ankit Nautiyal <ankit.k.nautiyal@intel.com>
The hardware does not support DisplayPort configurations where the
ceiling of the Link M/Link N ratio exceeds the limit. Enforce this
constraint for MST as well.
The compute config path needs no change: MST goes through
intel_dp_compute_config_limits() too, so the link config filter set up
there already excludes the configurations violating the ratio limit, and
MST fails there if none is left.
What is still missing is pruning such modes, so add the check to
mst_connector_mode_valid_ctx(), mirroring the SST mode_valid.
The ratio shrinks as the link rate grows, so the check uses the highest
available link rate rather than the rate of the maximum bandwidth
configuration the rest of the function works with. Those are not always
the same one: link training failures disable individual configurations,
after which the highest bandwidth configuration can be a slower rate with
more lanes, and using it here would prune modes a narrower but faster
configuration could still drive.
v2:
-Drop the checks in the MST link config helpers, redundant now that the
constraint is applied while computing the link config limits. (Imre)
v3
-Use the maximum rate rather than the maximum bandwidth configuration
for the ratio check. (Sashiko)
Signed-off-by: Ankit Nautiyal <ankit.k.nautiyal@intel.com>
Signed-off-by: Suraj Kandpal <suraj.kandpal@intel.com>
---
drivers/gpu/drm/i915/display/intel_dp.c | 2 +-
drivers/gpu/drm/i915/display/intel_dp.h | 3 +++
drivers/gpu/drm/i915/display/intel_dp_mst.c | 10 ++++++++++
3 files changed, 14 insertions(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/i915/display/intel_dp.c b/drivers/gpu/drm/i915/display/intel_dp.c
index 28c9461a7723..4a1934d4eca4 100644
--- a/drivers/gpu/drm/i915/display/intel_dp.c
+++ b/drivers/gpu/drm/i915/display/intel_dp.c
@@ -1275,7 +1275,7 @@ intel_dp_get_max_m_n_ratio(struct intel_display *display)
return 10;
}
-static bool
+bool
intel_dp_can_support_m_n(struct intel_display *display,
int pixel_clock, int link_rate)
{
diff --git a/drivers/gpu/drm/i915/display/intel_dp.h b/drivers/gpu/drm/i915/display/intel_dp.h
index 04fae203bb69..757e74ca8696 100644
--- a/drivers/gpu/drm/i915/display/intel_dp.h
+++ b/drivers/gpu/drm/i915/display/intel_dp.h
@@ -242,4 +242,7 @@ u8 intel_dp_as_sdp_transmission_time(void);
int intel_dp_link_init(struct intel_dp *intel_dp);
void intel_dp_link_cleanup(struct intel_dp *intel_dp);
+bool intel_dp_can_support_m_n(struct intel_display *display,
+ int pixel_clock, int link_rate);
+
#endif /* __INTEL_DP_H__ */
diff --git a/drivers/gpu/drm/i915/display/intel_dp_mst.c b/drivers/gpu/drm/i915/display/intel_dp_mst.c
index 6a869d0f6ffc..3f4ab9573d0c 100644
--- a/drivers/gpu/drm/i915/display/intel_dp_mst.c
+++ b/drivers/gpu/drm/i915/display/intel_dp_mst.c
@@ -1521,6 +1521,7 @@ mst_connector_mode_valid_ctx(struct drm_connector *_connector,
DRM_DP_BW_OVERHEAD_MST | DRM_DP_BW_OVERHEAD_SSC_REF_CLK;
int min_link_bpp_x16 = fxp_q4_from_int(18);
struct intel_dp_link_config max_bw_config;
+ struct intel_dp_link_config max_rate_config;
static bool supports_dsc;
int ret;
bool dsc = false;
@@ -1564,6 +1565,15 @@ mst_connector_mode_valid_ctx(struct drm_connector *_connector,
min_link_bpp_x16,
bw_overhead_flags);
+ if (intel_dp_link_caps_get_max_config(intel_dp->link.caps,
+ INTEL_DP_LINK_CAPS_ORDER_KEY_RATE_LANE,
+ INTEL_DP_LINK_CAPS_FILTER_ALL,
+ &max_rate_config) &&
+ !intel_dp_can_support_m_n(display, mode->clock, max_rate_config.rate)) {
+ *status = MODE_CLOCK_HIGH;
+ return 0;
+ }
+
/*
* TODO:
* - Also check if compression would allow for the mode
--
2.34.1
next prev parent reply other threads:[~2026-09-16 2:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-16 2:57 [PATCH v2 00/10] Implement Wa_14021768792 to bypass m_n ratio limit Suraj Kandpal
2026-09-16 2:57 ` [PATCH v2 01/10] drm/i915/display: Add helper to compute link M/N ratio for reuse Suraj Kandpal
2026-09-16 2:57 ` [PATCH v2 02/10] drm/i915/dp: Limit M/N ratio for DP SST Suraj Kandpal
2026-09-16 2:57 ` Suraj Kandpal [this message]
2026-09-16 3:08 ` [PATCH v2 03/10] drm/i915/dp_mst: Limit M/N ratio for MST sashiko-bot
2026-09-16 2:57 ` [PATCH v2 04/10] drm/i915/dp: Add M/N ratio check with warning for DP link config Suraj Kandpal
2026-09-16 2:57 ` [PATCH v2 05/10] drm/i915/display: Add bits for link_n_extended for DISPLAY >= 14 Suraj Kandpal
2026-09-16 3:02 ` sashiko-bot
2026-09-16 2:57 ` [PATCH v2 06/10] drm/i915/display_wa: Add support for Wa_14021768792 Suraj Kandpal
2026-09-16 2:57 ` [PATCH v2 07/10] drm/i915/display: Add bits for Wa_14021768792 for linkm/n ratio > 10 Suraj Kandpal
2026-09-16 2:57 ` [PATCH v2 08/10] drm/i915/display: Implement Wa_14021768792 for BMG DP for link_m/n " Suraj Kandpal
2026-09-16 2:57 ` [PATCH v2 09/10] drm/i915/dp: Extend intel_dp_can_support_m_n() for BMG M/N bypass Suraj Kandpal
2026-09-16 2:57 ` [PATCH v2 10/10] drm/i915/dp: Bump the max Link M/N ratio to 22 for DISPLAY_VER >= 35 Suraj Kandpal
2026-09-16 3:06 ` ✓ CI.KUnit: success for Implement Wa_14021768792 to bypass m_n ratio limit (rev7) Patchwork
2026-09-16 3:44 ` ✓ Xe.CI.BAT: " Patchwork
2026-09-16 3:47 ` ✓ i915.CI.BAT: " Patchwork
2026-09-16 4:54 ` ✓ Xe.CI.FULL: " Patchwork
2026-09-16 10:58 ` ✗ i915.CI.Full: failure " 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=20260916025710.432281-4-suraj.kandpal@intel.com \
--to=suraj.kandpal@intel.com \
--cc=ankit.k.nautiyal@intel.com \
--cc=arun.r.murthy@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.