Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: tarund18303@gmail.com
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
	intel-xe@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915/dp: remove redundant link state check
Date: Wed, 26 Aug 2026 04:54:59 +0000	[thread overview]
Message-ID: <20260826045459.964831F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260826044533.9292-1-tarund18303@gmail.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] Removing the DP link state check from `intel_dp_detect()` breaks recovery for monitors that drop link synchronization silently (without sending an HPD IRQ).
--

commit 26b9e2acc7df07dcc2e2026421a5c54d7a72b52e
Author: tarun-tarun143 <tarund18303@gmail.com>

drm/i915/dp: remove redundant link state check

This commit removes the DP link state check from intel_dp_detect(), relying
instead on the link recovery paths after modesets and hotplug events.

> diff --git a/drivers/gpu/drm/i915/display/intel_dp.c b/drivers/gpu/drm/i915/display/intel_dp.c
> index 113d767e62e9c..ffd39206b958e 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);
> -

[Severity: Medium]
Does removing this check break recovery for monitors that drop link
synchronization silently?

While the link state is recovered after modesets and hotplug events, some
non-compliant monitors fail to assert an HPD IRQ when the main link drops
due to issues like EMI. When this hardware failure happens, a user or
desktop environment running a probe calls intel_dp_detect().

Before this patch, intel_dp_detect() would read the DPCD link status and
queue a link retrain, acting as a manual fallback. By removing this check,
intel_dp_detect() succeeds via the independent AUX channel but ignores the
broken main link. Will this leave users with a permanent blank screen until
a full modeset or physical replug is performed?

>  	/*
>  	 * Clearing NACK and defer counts to get their exact values
>  	 * while reading EDID which are required by Compliance tests

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260826044533.9292-1-tarund18303@gmail.com?part=1

  reply	other threads:[~2026-08-26  4:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-26  4:45 [PATCH] drm/i915/dp: remove redundant link state check tarund18303
2026-08-26  4:54 ` sashiko-bot [this message]
2026-08-26 19:47 ` ✗ LGCI.VerificationFailed: failure for " 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=20260826045459.964831F000E9@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=tarund18303@gmail.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