From: tarund18303@gmail.com
To: jani.nikula@linux.intel.com
Cc: rodrigo.vivi@intel.com, joonas.lahtinen@linux.intel.com,
tursulin@ursulin.net, airlied@gmail.com, simona@ffwll.ch,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org,
tarun-tarun143 <tarund18303@gmail.com>
Subject: [PATCH] drm/i915/dp: remove redundant link state check
Date: Wed, 26 Aug 2026 05:23:57 +0000 [thread overview]
Message-ID: <20260826052357.10151-1-tarund18303@gmail.com> (raw)
From: tarun-tarun143 <tarund18303@gmail.com>
The DP link state is checked and recovered through the encoder link
check work from the modeset and HPD paths.
The detect handler also used to queue the same link check work for
non-eDP sinks. This was added when link recovery was moved to the
encoder's check link state work, and the original change explicitly
left a TODO to remove the detect-time check once it became redundant.
Remove the detect-time link state check and rely on the existing link
recovery paths.
Signed-off-by: tarun-tarun143 <tarund18303@gmail.com>
---
drivers/gpu/drm/i915/display/intel_dp.c | 12 ------------
1 file changed, 12 deletions(-)
diff --git a/drivers/gpu/drm/i915/display/intel_dp.c b/drivers/gpu/drm/i915/display/intel_dp.c
index 113d767e62e9..ffd39206b958 100644
--- a/drivers/gpu/drm/i915/display/intel_dp.c
+++ b/drivers/gpu/drm/i915/display/intel_dp.c
@@ -6379,18 +6379,6 @@ intel_dp_detect(struct drm_connector *_connector,
status = connector_status_disconnected;
goto out_unset_edid;
}
-
- /*
- * Some external monitors do not signal loss of link synchronization
- * with an IRQ_HPD, so force a link status check.
- *
- * TODO: this probably became redundant, so remove it: the link state
- * is rechecked/recovered now after modesets, where the loss of
- * synchronization tends to occur.
- */
- if (!intel_dp_is_edp(intel_dp))
- intel_dp_check_link_state(intel_dp);
-
/*
* Clearing NACK and defer counts to get their exact values
* while reading EDID which are required by Compliance tests
--
2.43.0
next reply other threads:[~2026-08-26 5:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-26 5:23 tarund18303 [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-08-26 4:45 tarund18303
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=20260826052357.10151-1-tarund18303@gmail.com \
--to=tarund18303@gmail.com \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rodrigo.vivi@intel.com \
--cc=simona@ffwll.ch \
--cc=tursulin@ursulin.net \
/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
all inboxes | Powered by JetHome®