From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: "Nautiyal, Ankit K" <ankit.k.nautiyal@intel.com>,
intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Subject: Re: [PATCH 1/2] Revert "drm/i915/dp: Reject HBR3 when sink doesn't support TPS4"
Date: Thu, 26 Jun 2025 14:31:59 +0300 [thread overview]
Message-ID: <aF0vr8gQtw2Lfmx4@intel.com> (raw)
In-Reply-To: <3d26024d8750cb1c188da77f7d3b07fb5b2cc40b@intel.com>
On Wed, Jun 25, 2025 at 11:18:03AM +0300, Jani Nikula wrote:
> On Tue, 24 Jun 2025, Ville Syrjälä <ville.syrjala@linux.intel.com> wrote:
> > On Tue, Jun 24, 2025 at 10:10:53AM +0530, Nautiyal, Ankit K wrote:
> >>
> >> On 6/23/2025 8:12 PM, Ville Syrjälä wrote:
> >> > On Fri, Jun 20, 2025 at 06:14:16PM +0530, Ankit Nautiyal wrote:
> >> >> This reverts commit 584cf613c24a4250d9be4819efc841aa2624d5b6.
> >> >> Commit 584cf613c24a ("drm/i915/dp: Reject HBR3 when sink doesn't support
> >> >> TPS4") introduced a blanket rejection of HBR3 link rate when the sink does
> >> >> not support TPS4. While this was intended to address instability observed
> >> >> on certain eDP panels [1], the TPS4 requirement is only mandated for DPRX
> >> >> and not for eDPRX.
> >> > I see no exception given for eDP regarding this rule. The only exception
> >> > allowed is that eDP can say DPCD_REV=1.4 + TPS4_SUPPORTED=0. So I still
> >> > claim that these eDP sinks are violating the spec.
> >>
> >> Hmm.. Yes the spec allows eDP sinks to report DPCD_REV=1.4 and
> >> TPS4_SUPPORTED, so perhaps eDPs claiming HBR3 with DPCD rev other than
> >> rev 1.4 and not supporting TPS4 are indeed violating the spec.
> >>
> >> Would it make sense to add a condition that checks for DPCD_REV=1.4.
> >>
> >> Specifically:
> >>
> >> if DPCD_REV=1.4 and TPS4_SUPPORTED = 0, then do not prune the HBR3 rate?
> >>
> >> Or otherway if DPCD_REV!=1.4 and TPS4_SUPPORTER = 0, prune the HBR3 rate
> >>
> >> This way the patch need not be reverted, but modified to address
> >> instability issues for eDP panels that are not aligned with the spec.
> >>
> >> That said, the gitlab issue#5969 [1] will still need another solution
> >> since it seems to have DPCD rev 14 as per logs:
> >>
> >> DPCD: 14 1e 44 41 00 00 01 80 02 00 02 00 00 0b 80
> >
> > I think we do need the quirk. But the commit message should IMO be
> > adjusted so that it doesn't claim that these panels are 100% legal.
>
> Right. But are you okay with reverting 584cf613c24a ("drm/i915/dp:
> Reject HBR3 when sink doesn't support TPS4") i.e. allowing HBR3
> *without* TPS4 by default, and quirking the panel that can't handle
> HBR3?
Yeah, I think the revert+quirk for the one known bad system is the way
to go.
>
> No matter what the spec says, this seems to be common. More regressing
> systems are cropping up, e.g. [1].
>
>
> BR,
> Jani.
>
>
> [1] https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/14517
>
>
>
>
> --
> Jani Nikula, Intel
--
Ville Syrjälä
Intel
next prev parent reply other threads:[~2025-06-26 11:32 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-20 12:44 [PATCH 0/2] Revert patch to reject HBR3 for all eDP panels Ankit Nautiyal
2025-06-20 12:44 ` [PATCH 1/2] Revert "drm/i915/dp: Reject HBR3 when sink doesn't support TPS4" Ankit Nautiyal
2025-06-23 14:42 ` Ville Syrjälä
2025-06-24 4:40 ` Nautiyal, Ankit K
2025-06-24 16:49 ` Ville Syrjälä
2025-06-25 8:18 ` Jani Nikula
2025-06-26 11:31 ` Ville Syrjälä [this message]
2025-06-20 12:44 ` [PATCH 2/2] drm/i915/dp: Add device specific quirk to limit eDP rate to HBR2 Ankit Nautiyal
2025-06-23 9:59 ` Jani Nikula
2025-06-24 7:32 ` Nautiyal, Ankit K
2025-06-20 13:23 ` ✓ CI.KUnit: success for Revert patch to reject HBR3 for all eDP panels Patchwork
2025-06-20 13:57 ` ✓ i915.CI.BAT: " Patchwork
2025-06-20 16:46 ` ✗ i915.CI.Full: failure " Patchwork
2025-06-20 23:47 ` ✓ Xe.CI.Full: success " Patchwork
2025-06-23 5:32 ` ✓ i915.CI.Full: " Patchwork
2025-06-24 8:43 ` ✓ CI.KUnit: success for Revert patch to reject HBR3 for all eDP panels (rev2) Patchwork
2025-06-24 9:50 ` ✓ Xe.CI.BAT: " Patchwork
2025-06-24 16:20 ` ✓ Xe.CI.Full: " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2025-07-10 5:20 [PATCH 0/1] Revert patch to reject HBR3 for all eDP panels Ankit Nautiyal
2025-07-10 5:20 ` [PATCH 1/2] Revert "drm/i915/dp: Reject HBR3 when sink doesn't support TPS4" Ankit Nautiyal
2025-07-09 5:51 [PATCH 0/1] Revert patch to reject HBR3 for all eDP panels Ankit Nautiyal
2025-07-09 5:51 ` [PATCH 1/2] Revert "drm/i915/dp: Reject HBR3 when sink doesn't support TPS4" Ankit Nautiyal
2025-07-09 18:04 ` Ville Syrjälä
2025-07-10 4:47 ` Nautiyal, Ankit K
2025-06-10 10:04 [PATCH 0/2] Add kernel param to limit the eDP rate to HBR2 Ankit Nautiyal
2025-06-10 10:04 ` [PATCH 1/2] Revert "drm/i915/dp: Reject HBR3 when sink doesn't support TPS4" Ankit Nautiyal
2025-06-10 12:15 ` Jani Nikula
2025-05-14 8:43 [PATCH 0/2] Add quirk for panels that support HBR3 without TPS4 Ankit Nautiyal
2025-05-14 8:43 ` [PATCH 1/2] Revert "drm/i915/dp: Reject HBR3 when sink doesn't support TPS4" Ankit Nautiyal
2025-05-14 10:02 ` Jani Nikula
2025-05-14 10:47 ` Jani Nikula
2025-05-14 11:33 ` Nautiyal, Ankit K
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=aF0vr8gQtw2Lfmx4@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=ankit.k.nautiyal@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.