From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: intel-xe@lists.freedesktop.org, stable@vger.kernel.org,
Jani Nikula <jani.nikula@linux.intel.com>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
Tvrtko Ursulin <tursulin@ursulin.net>,
Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [PATCH 1/2] drm/i915/cdclk: Avoid spurious cdclk sanitization on PTL+
Date: Fri, 17 Jul 2026 19:05:26 +0300 [thread overview]
Message-ID: <alpSxjjmv34zKW2p@intel.com> (raw)
In-Reply-To: <20260717155107.17801-1-ville.syrjala@linux.intel.com>
On Fri, Jul 17, 2026 at 06:51:06PM +0300, Ville Syrjala wrote:
> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> Apparently PTL+ no longer has the cd2x pipe select field in
> CDCLK_CTL. Take that into account during CDCLK sanitization.
>
> This currently triggers a spurious CDCLK sanitization during
> driver load on PTL+ which will causes a visible glitch on all
> active displays.
>
> Cc: stable@vger.kernel.org
> Closes: https://gitlab.freedesktop.org/drm/xe/kernel/-/work_items/8550
> Fixes: 3f9de66f8acb ("drm/i915/cdclk: Fix up CDCLK_FREQ_DECIMAL without a full PLL re-enable")
> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> ---
Unfortunately the regression itself has a cc:stable on it, so we'll
need to backport this fix as well.
To do that cleanly we need to pick up these as well:
commit cd16e794aead ("drm/i915/cdclk: Clean up CDCLK_CTL defines")
commit 67d77d9472c6 ("drm/i915/cdclk: Introduce bxt_cdclk_cd2x_pipe_mask() and use it")
> drivers/gpu/drm/i915/display/intel_cdclk.c | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_cdclk.c b/drivers/gpu/drm/i915/display/intel_cdclk.c
> index a53d88727177..9e5e15b0c4d1 100644
> --- a/drivers/gpu/drm/i915/display/intel_cdclk.c
> +++ b/drivers/gpu/drm/i915/display/intel_cdclk.c
> @@ -2381,8 +2381,10 @@ static void bxt_sanitize_cdclk(struct intel_display *display)
> * dividers both syncing to an active pipe, or asynchronously
> * (PIPE_NONE).
> */
> - cdctl &= ~bxt_cdclk_cd2x_pipe_mask(display);
> - cdctl |= bxt_cdclk_cd2x_pipe(display, INVALID_PIPE);
> + if (DISPLAY_VER(display) < 30) {
> + cdctl &= ~bxt_cdclk_cd2x_pipe_mask(display);
> + cdctl |= bxt_cdclk_cd2x_pipe(display, INVALID_PIPE);
> + }
>
> if (cdctl != expected) {
> if (DISPLAY_VER(display) < 20) {
> --
> 2.54.0
--
Ville Syrjälä
Intel
next prev parent reply other threads:[~2026-07-17 16:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-17 15:51 [PATCH 1/2] drm/i915/cdclk: Avoid spurious cdclk sanitization on PTL+ Ville Syrjala
2026-07-17 15:51 ` [PATCH 2/2] drm/i915/cdclk: Introduce has_cd2x_pipe_select() Ville Syrjala
2026-07-17 16:05 ` Ville Syrjälä [this message]
2026-07-17 16:26 ` ✓ CI.KUnit: success for series starting with [1/2] drm/i915/cdclk: Avoid spurious cdclk sanitization on PTL+ Patchwork
2026-07-17 17:02 ` ✓ Xe.CI.BAT: " Patchwork
2026-07-17 20:21 ` ✓ i915.CI.BAT: " Patchwork
2026-07-18 0:00 ` ✓ Xe.CI.FULL: " 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=alpSxjjmv34zKW2p@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=stable@vger.kernel.org \
--cc=tursulin@ursulin.net \
/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.