From: Imre Deak <imre.deak@intel.com>
To: <intel-gfx@lists.freedesktop.org>, <intel-xe@lists.freedesktop.org>
Subject: [PATCH 2/2] drm/i915/dp: Simplify forcing a link retraining
Date: Wed, 11 Mar 2026 17:31:52 +0200 [thread overview]
Message-ID: <20260311153152.133744-2-imre.deak@intel.com> (raw)
In-Reply-To: <20260311153152.133744-1-imre.deak@intel.com>
Since both the DP SST and MST HPD IRQ handlers call
intel_dp_handle_link_service_irq() with LINK_STATUS_CHANGED set in
irq_mask if intel_dp->link.force_retrain is set, checking for the former
flag is sufficient to determine if the link status needs to be checked
(which includes retraining the link if this is forced); remove checking
for the latter flag.
Since LINK_STATUS_CHANGED is currently set unconditionally for DP SST,
extend the related comment to note that it must be set if
intel_dp->link.force_retrain is set (in case setting LINK_STATUS_CHANGED
becomes conditional on DPCD_REV).
Signed-off-by: Imre Deak <imre.deak@intel.com>
---
drivers/gpu/drm/i915/display/intel_dp.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/i915/display/intel_dp.c b/drivers/gpu/drm/i915/display/intel_dp.c
index 2ae030eda73ee..4955bd8b11d7a 100644
--- a/drivers/gpu/drm/i915/display/intel_dp.c
+++ b/drivers/gpu/drm/i915/display/intel_dp.c
@@ -5925,7 +5925,7 @@ static bool intel_dp_handle_link_service_irq(struct intel_dp *intel_dp, u8 irq_m
if (irq_mask & RX_CAP_CHANGED)
reprobe_needed = true;
- if ((irq_mask & LINK_STATUS_CHANGED) || intel_dp->link.force_retrain)
+ if (irq_mask & LINK_STATUS_CHANGED)
intel_dp_check_link_state(intel_dp);
if (irq_mask & HDMI_LINK_STATUS_CHANGED)
@@ -5984,7 +5984,7 @@ intel_dp_short_pulse(struct intel_dp *intel_dp)
/*
* Force checking the link status for DPCD_REV < 1.2
* TODO: let the link status check depend on LINK_STATUS_CHANGED
- * for DPCD_REV >= 1.2
+ * or intel_dp->link.force_retrain for DPCD_REV >= 1.2
*/
esi[3] |= LINK_STATUS_CHANGED;
if (intel_dp_handle_link_service_irq(intel_dp, esi[3]))
--
2.49.1
next prev parent reply other threads:[~2026-03-11 15:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-11 15:31 [PATCH 1/2] drm/i915/dp_mst: Fix forced link retrain handling in MST HPD IRQ handler Imre Deak
2026-03-11 15:31 ` Imre Deak [this message]
2026-03-12 5:17 ` [PATCH 2/2] drm/i915/dp: Simplify forcing a link retraining Kandpal, Suraj
2026-03-11 16:51 ` ✓ i915.CI.BAT: success for series starting with [1/2] drm/i915/dp_mst: Fix forced link retrain handling in MST HPD IRQ handler Patchwork
2026-03-12 4:59 ` [PATCH 1/2] " Kandpal, Suraj
2026-03-12 8:18 ` ✓ i915.CI.Full: success for series starting with [1/2] " Patchwork
2026-03-13 13:01 ` Imre Deak
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=20260311153152.133744-2-imre.deak@intel.com \
--to=imre.deak@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox