Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Imre Deak <imre.deak@intel.com>,
	intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org,
	dri-devel@lists.freedesktop.org
Cc: stable@vger.kernel.org, "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Subject: Re: [PATCH 1/4] drm/dp: Change AUX DPCD probe address from DPCD_REV to LANE0_1_STATUS
Date: Wed, 04 Jun 2025 12:53:23 +0300	[thread overview]
Message-ID: <892023ee348a6bcad3fd553cafe6ff650974fa3f@intel.com> (raw)
In-Reply-To: <20250603121543.17842-2-imre.deak@intel.com>

On Tue, 03 Jun 2025, Imre Deak <imre.deak@intel.com> wrote:
> Reading DPCD registers has side-effects in general. In particular
> accessing registers outside of the link training register range
> (0x102-0x106, 0x202-0x207, 0x200c-0x200f, 0x2216) is explicitly
> forbidden by the DP v2.1 Standard, see
>
> 3.6.5.1 DPTX AUX Transaction Handling Mandates
> 3.6.7.4 128b/132b DP Link Layer LTTPR Link Training Mandates
>
> Based on my tests, accessing the DPCD_REV register during the link
> training of an UHBR TBT DP tunnel sink leads to link training failures.
>
> Solve the above by using the DP_LANE0_1_STATUS (0x202) register for the
> DPCD register access quirk.
>
> Cc: <stable@vger.kernel.org>
> Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
> Cc: Jani Nikula <jani.nikula@linux.intel.com>
> Signed-off-by: Imre Deak <imre.deak@intel.com>

Acked-by: Jani Nikula <jani.nikula@intel.com>

> ---
>  drivers/gpu/drm/display/drm_dp_helper.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/display/drm_dp_helper.c b/drivers/gpu/drm/display/drm_dp_helper.c
> index f2a6559a27100..dc622c78db9d4 100644
> --- a/drivers/gpu/drm/display/drm_dp_helper.c
> +++ b/drivers/gpu/drm/display/drm_dp_helper.c
> @@ -725,7 +725,7 @@ ssize_t drm_dp_dpcd_read(struct drm_dp_aux *aux, unsigned int offset,
>  	 * monitor doesn't power down exactly after the throw away read.
>  	 */
>  	if (!aux->is_remote) {
> -		ret = drm_dp_dpcd_probe(aux, DP_DPCD_REV);
> +		ret = drm_dp_dpcd_probe(aux, DP_LANE0_1_STATUS);
>  		if (ret < 0)
>  			return ret;
>  	}

-- 
Jani Nikula, Intel

  reply	other threads:[~2025-06-04  9:53 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-03 12:15 [PATCH 0/4] drm/dp: Limit the DPCD probe quirk to the affected monitor Imre Deak
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 [this message]
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 12:44 ` ✓ CI.Patch_applied: success for drm/dp: Limit the DPCD probe quirk to the affected monitor Patchwork
2025-06-03 12:44 ` ✗ CI.checkpatch: warning " Patchwork
2025-06-03 12:45 ` ✓ CI.KUnit: success " Patchwork
2025-06-03 12:56 ` ✓ CI.Build: " Patchwork
2025-06-03 12:58 ` ✓ CI.Hooks: " Patchwork
2025-06-03 13:00 ` ✗ CI.checksparse: warning " Patchwork
2025-06-03 13:48 ` ✓ Xe.CI.BAT: success " Patchwork
2025-06-03 15:42 ` ✓ CI.Patch_applied: success for drm/dp: Limit the DPCD probe quirk to the affected monitor (rev2) Patchwork
2025-06-03 15:42 ` ✗ CI.checkpatch: warning " Patchwork
2025-06-03 15:43 ` ✗ CI.KUnit: failure " Patchwork
2025-06-04 10:13 ` ✓ CI.Patch_applied: success for drm/dp: Limit the DPCD probe quirk to the affected monitor (rev3) Patchwork
2025-06-04 10:13 ` ✗ CI.checkpatch: warning " Patchwork
2025-06-04 10:14 ` ✓ CI.KUnit: success " Patchwork
2025-06-04 10:33 ` ✓ CI.Hooks: " Patchwork
2025-06-04 10:33 ` ✗ CI.checksparse: warning " Patchwork
2025-06-04 11:21 ` ✓ Xe.CI.BAT: success " Patchwork
2025-06-04 13:58 ` ✗ Xe.CI.Full: failure for drm/dp: Limit the DPCD probe quirk to the affected monitor Patchwork
2025-06-05  3:45 ` ✗ Xe.CI.Full: failure for drm/dp: Limit the DPCD probe quirk to the affected monitor (rev3) 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=892023ee348a6bcad3fd553cafe6ff650974fa3f@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=imre.deak@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=stable@vger.kernel.org \
    --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