From: Imre Deak <imre.deak@intel.com>
To: Suraj Kandpal <suraj.kandpal@intel.com>
Cc: <intel-xe@lists.freedesktop.org>,
<intel-gfx@lists.freedesktop.org>, <ankit.k.nautiyal@intel.com>,
<arun.r.murthy@intel.com>
Subject: Re: [PATCH] drm/i915/ltphy: Return true for TBT scenario during lt_phy_state compare
Date: Tue, 3 Feb 2026 10:25:45 +0200 [thread overview]
Message-ID: <aYGxCTupSRGPp4jH@ideak-desk.lan> (raw)
In-Reply-To: <20260203024141.1549517-1-suraj.kandpal@intel.com>
On Tue, Feb 03, 2026 at 08:11:41AM +0530, Suraj Kandpal wrote:
> TBT PHY is enablement/disablement is handled by its own TBT module.
> We do not play a big part in it's state management that being take care
> by it's own TBT modeule. With that in mind comparing the state would be
> wrong since we really don't touch it.
> Simple return true when we are in tbt mode.
>
> Signed-off-by: Suraj Kandpal <suraj.kandpal@intel.com>
> ---
> drivers/gpu/drm/i915/display/intel_lt_phy.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_lt_phy.c b/drivers/gpu/drm/i915/display/intel_lt_phy.c
> index 04f63bdd0b87..27ad8407606b 100644
> --- a/drivers/gpu/drm/i915/display/intel_lt_phy.c
> +++ b/drivers/gpu/drm/i915/display/intel_lt_phy.c
> @@ -2158,6 +2158,9 @@ bool
> intel_lt_phy_pll_compare_hw_state(const struct intel_lt_phy_pll_state *a,
> const struct intel_lt_phy_pll_state *b)
> {
> + if (a->tbt_mode || b->tbt_mode)
> + return true;
It is a relevant state whether the PHY is in TBT mode or in a non-TBT
mode, even if the PHY is programmed by the TBT HW block in TBT mode. So
it's not ok to ignore a difference in this state. Please provide the
actual context for why the change was added.
> +
> /*
> * With LT PHY values other than VDR0_CONFIG and VDR2_CONFIG are
> * unreliable. They cannot always be read back since internally
> --
> 2.34.1
>
next prev parent reply other threads:[~2026-02-03 8:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-03 2:41 [PATCH] drm/i915/ltphy: Return true for TBT scenario during lt_phy_state compare Suraj Kandpal
2026-02-03 8:05 ` ✓ CI.KUnit: success for " Patchwork
2026-02-03 8:25 ` Imre Deak [this message]
2026-02-03 8:40 ` [PATCH] " Kandpal, Suraj
2026-02-03 16:10 ` Imre Deak
2026-02-04 2:23 ` Kandpal, Suraj
2026-02-03 8:43 ` ✓ Xe.CI.BAT: success for " Patchwork
2026-02-03 21:29 ` ✓ Xe.CI.FULL: " Patchwork
2026-02-04 2:32 ` [PATCH v2] " Suraj Kandpal
2026-02-04 11:24 ` Imre Deak
2026-02-04 2:49 ` ✓ CI.KUnit: success for drm/i915/ltphy: Return true for TBT scenario during lt_phy_state compare (rev2) Patchwork
2026-02-04 3:25 ` ✗ Xe.CI.BAT: failure " Patchwork
2026-02-04 17:03 ` ✓ CI.KUnit: success for drm/i915/ltphy: Return true for TBT scenario during lt_phy_state compare (rev3) Patchwork
2026-02-04 17:42 ` ✗ Xe.CI.FULL: failure for drm/i915/ltphy: Return true for TBT scenario during lt_phy_state compare (rev2) Patchwork
2026-02-04 17:46 ` ✗ Xe.CI.BAT: failure for drm/i915/ltphy: Return true for TBT scenario during lt_phy_state compare (rev3) Patchwork
2026-02-04 20:30 ` ✓ Xe.CI.BAT: success " Patchwork
2026-02-05 3:42 ` ✗ Xe.CI.FULL: 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=aYGxCTupSRGPp4jH@ideak-desk.lan \
--to=imre.deak@intel.com \
--cc=ankit.k.nautiyal@intel.com \
--cc=arun.r.murthy@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=suraj.kandpal@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