Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Imre Deak <imre.deak@intel.com>
To: <intel-gfx@lists.freedesktop.org>,
	<intel-xe@lists.freedesktop.org>,
	<dri-devel@lists.freedesktop.org>
Cc: "Ville Syrjälä" <ville.syrjala@linux.intel.com>,
	"Jani Nikula" <jani.nikula@linux.intel.com>
Subject: [PATCH 0/4] drm/dp: Limit the DPCD probe quirk to the affected monitor
Date: Tue, 3 Jun 2025 15:15:39 +0300	[thread overview]
Message-ID: <20250603121543.17842-1-imre.deak@intel.com> (raw)

This patchset fixes a known issue where the DPCD probe quirk leads to
link training failures (patch 1) and limits the quirk to the monitor
which requires it, to avoid similar failures in the future.

Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
Cc: Jani Nikula <jani.nikula@linux.intel.com>

Imre Deak (4):
  drm/dp: Change AUX DPCD probe address from DPCD_REV to LANE0_1_STATUS
  drm/edid: Add support for quirks visible to DRM core and drivers
  drm/dp: Add an EDID quirk for the DPCD register access probe
  drm/i915/dp: Disable the AUX DPCD probe quirk if it's not required

 drivers/gpu/drm/display/drm_dp_helper.c      | 17 +++++++--
 drivers/gpu/drm/drm_edid.c                   | 36 ++++++++++++++++----
 drivers/gpu/drm/i915/display/intel_dp.c      | 11 ++++--
 drivers/gpu/drm/i915/display/intel_dp_aux.c  |  2 ++
 drivers/gpu/drm/i915/display/intel_hotplug.c | 10 ++++++
 include/drm/display/drm_dp_helper.h          |  6 ++++
 include/drm/drm_connector.h                  |  5 +++
 include/drm/drm_edid.h                       |  6 ++++
 8 files changed, 82 insertions(+), 11 deletions(-)

-- 
2.44.2


             reply	other threads:[~2025-06-03 12:16 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-03 12:15 Imre Deak [this message]
2025-06-03 12:15 ` [PATCH 1/4] drm/dp: Change AUX DPCD probe address from DPCD_REV to LANE0_1_STATUS Imre Deak
2025-06-04  9:53   ` Jani Nikula
2025-06-03 12:15 ` [PATCH 2/4] drm/edid: Add support for quirks visible to DRM core and drivers Imre Deak
2025-06-04  9:13   ` [PATCH v2 " Imre Deak
2025-06-04 10:02     ` Jani Nikula
2025-06-04 16:27       ` Imre Deak
2025-06-03 12:15 ` [PATCH 3/4] drm/dp: Add an EDID quirk for the DPCD register access probe Imre Deak
2025-06-03 15:36   ` [PATCH v2 " Imre Deak
2025-06-04 10:11     ` Jani Nikula
2025-06-04 16:34       ` Imre Deak
2025-06-03 12:15 ` [PATCH 4/4] drm/i915/dp: Disable the AUX DPCD probe quirk if it's not required Imre Deak
2025-06-04 10:13   ` Jani Nikula
2025-06-03 14:46 ` ✗ Fi.CI.CHECKPATCH: warning for drm/dp: Limit the DPCD probe quirk to the affected monitor Patchwork
2025-06-03 14:46 ` ✗ Fi.CI.SPARSE: " Patchwork
2025-06-03 15:09 ` ✗ i915.CI.BAT: failure " Patchwork
2025-06-03 16:32 ` ✗ Fi.CI.CHECKPATCH: warning for drm/dp: Limit the DPCD probe quirk to the affected monitor (rev2) Patchwork
2025-06-03 16:32 ` ✗ Fi.CI.SPARSE: " Patchwork
2025-06-03 16:54 ` ✓ i915.CI.BAT: success " Patchwork
2025-06-03 19:29 ` ✓ i915.CI.Full: " Patchwork
2025-06-04 10:00 ` ✗ Fi.CI.CHECKPATCH: warning for drm/dp: Limit the DPCD probe quirk to the affected monitor (rev3) Patchwork
2025-06-04 10:00 ` ✗ Fi.CI.SPARSE: " Patchwork
2025-06-04 10:20 ` ✗ i915.CI.BAT: 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=20250603121543.17842-1-imre.deak@intel.com \
    --to=imre.deak@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.com \
    --cc=ville.syrjala@linux.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