Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Imre Deak <imre.deak@intel.com>
To: Wolfgang Frisch <wfrisch@suse.de>
Cc: <intel-gfx@lists.freedesktop.org>,
	<dri-devel@lists.freedesktop.org>,
	Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 6.16.y] Revert "drm/dp: Change AUX DPCD probe address from DPCD_REV to LANE0_1_STATUS"
Date: Thu, 4 Sep 2025 16:35:12 +0300	[thread overview]
Message-ID: <aLmVkGAtcQ91jne9@ideak-desk> (raw)
In-Reply-To: <01426301-990d-4cd2-a6a4-330f1bd20291@suse.de>

On Thu, Sep 04, 2025 at 03:20:23PM +0200, Wolfgang Frisch wrote:
> Hi Imre,
> 
> 
> On 9/2/25 6:13 PM, Imre Deak wrote:
> > This looks like the issue tracked at
> > https://gitlab.freedesktop.org/drm/amd/-/issues/4500
> Thanks! I wasn't aware of that issue being tracked already.
> 
> > The correct solution there is to disable the DPCD probing, which AMD
> > folks are working on atm. Until that, could you give a go to patch [1]
> > on the above ticket equivalent to this solution, applying on v6.17, or
> > the attached patch achieving the same on v6.16.4?
> I can confirm your patch fixes the issue on v6.16.4.
> > Also it would help if you could add a dmesg log on the ticket taken
> > after booting with drm.debug=0x100 and reproducing the problem (vs. two
> > other drm.debug=0x100 logs, one with the above DP_TRAINING_PATTERN_SET
> > -> DP_LANE0_1_STATUS change and another one with DPCD probing disabled
> > as I requested above, taken after booting up and connecting the
> > dock/monitor).
> Done. I attached 3 dmesg logs to the ticket:

Thanks for the testing.

> - GOOD: Linux 6.16.4 with DPCD probing disabled
> - BAD: Linux 6.17.0-rc4

This is expected, as it still does DPCD probing leading to the original
TBT firmware issue tracked on the above ticket.

> - GOOD: Linux 6.17.0-rc4 with the probe address set to DP_LANE0_1_STATUS

Switching the DPCD probing address to DP_LANE0_1_STATUS is not a viable
solution, as it causes an issue for at least one other (eDP) panel. The
probing should be disabled according to the following AMD patch:

https://gitlab.freedesktop.org/-/project/4522/uploads/5205fd4e2bdc396088836bafcac176b6/0004-drm-amd-display-Disable-DPCD-Probe-Quirk.patch

--Imre

> Regards,
> 
> -- 
> Wolfgang Frisch <wolfgang.frisch@suse.com>
> Security Engineer
> OpenPGP fingerprint: A2E6 B7D4 53E9 544F BC13  D26B D9B3 56BD 4D4A 2D15
> SUSE Software Solutions Germany GmbH, Frankenstraße 146, 90461 Nürnberg
> 




  reply	other threads:[~2025-09-04 13:35 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-28 17:49 [PATCH 5.4.y] Revert "drm/dp: Change AUX DPCD probe address from DPCD_REV to LANE0_1_STATUS" Imre Deak
2025-08-28 17:49 ` [PATCH 5.10.y] " Imre Deak
2025-09-02 11:56   ` Patch "Revert "drm/dp: Change AUX DPCD probe address from DPCD_REV to LANE0_1_STATUS"" has been added to the 5.10-stable tree gregkh
2025-08-28 17:49 ` [PATCH 5.15.y] Revert "drm/dp: Change AUX DPCD probe address from DPCD_REV to LANE0_1_STATUS" Imre Deak
2025-08-28 17:49 ` [PATCH 6.1.y] " Imre Deak
2025-09-02 12:27   ` Patch "Revert "drm/dp: Change AUX DPCD probe address from DPCD_REV to LANE0_1_STATUS"" has been added to the 6.1-stable tree gregkh
2025-08-28 17:49 ` [PATCH 6.6.y] Revert "drm/dp: Change AUX DPCD probe address from DPCD_REV to LANE0_1_STATUS" Imre Deak
2025-08-28 17:49 ` [PATCH 6.12.y] " Imre Deak
2025-08-28 17:49 ` [PATCH 6.16.y] " Imre Deak
2025-09-02 14:32   ` Wolfgang Frisch
2025-09-02 16:13     ` Imre Deak
2025-09-04 13:20       ` Wolfgang Frisch
2025-09-04 13:35         ` Imre Deak [this message]
2025-08-28 18:02 ` ✗ Fi.CI.BUILD: failure for Revert "drm/dp: Change AUX DPCD probe address from DPCD_REV to LANE0_1_STATUS" (rev7) Patchwork
2025-09-02 11:44 ` Patch "Revert "drm/dp: Change AUX DPCD probe address from DPCD_REV to LANE0_1_STATUS"" has been added to the 5.4-stable tree gregkh
2025-09-02 20:13 ` ✗ Fi.CI.BUILD: failure for Revert "drm/dp: Change AUX DPCD probe address from DPCD_REV to LANE0_1_STATUS" (rev8) 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=aLmVkGAtcQ91jne9@ideak-desk \
    --to=imre.deak@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=sashal@kernel.org \
    --cc=wfrisch@suse.de \
    /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