From: sashiko-bot@kernel.org
To: "Ankit Nautiyal" <ankit.k.nautiyal@intel.com>
Cc: intel-xe@lists.freedesktop.org, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915/display: Update the CMN_SDP_TL in fastset path
Date: Wed, 23 Sep 2026 14:00:49 +0000 [thread overview]
Message-ID: <20260923140049.B35151F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260923133307.323439-1-ankit.k.nautiyal@intel.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] drm/i915: missing stagger values in cmn_sdp_changed() during fastset
--
commit ff9e34489c7caadda60fd7bbc48f29b27fcbfe10
Author: Ankit Nautiyal <ankit.k.nautiyal@intel.com>
drm/i915/display: Update the CMN_SDP_TL in fastset path
Commit bfa597238073 ("drm/i915/dip: Enable Common SDP Transmission line")
enabled the CMN_SDP_TL for the modeset path, but missed to add it to the
fastset path. This commit updates the CMN_SDP_TL register during fastsets
if it has changed, similar to EMP_AS_SDP_TL.
> diff --git a/drivers/gpu/drm/i915/display/intel_display.c b/drivers/gpu/drm/i915/display/intel_display.c
> index e3e0d2f8faefd..01604c4e8615c 100644
> --- a/drivers/gpu/drm/i915/display/intel_display.c
> +++ b/drivers/gpu/drm/i915/display/intel_display.c
[ ... ]
> @@ -999,6 +1000,12 @@ static bool cmrr_params_changed(const struct intel_crtc_state *old_crtc_state,
> old_crtc_state->vrr.cmrr.cmrr_n != new_crtc_state->vrr.cmrr.cmrr_n;
> }
>
> +static bool cmn_sdp_changed(const struct intel_crtc_state *old_crtc_state,
> + const struct intel_crtc_state *new_crtc_state)
> +{
> + return old_crtc_state->dip.cmn_sdp_tl != new_crtc_state->dip.cmn_sdp_tl;
> +}
> +
[Severity: Medium]
Should cmn_sdp_changed() in drivers/gpu/drm/i915/display/intel_display.c also
check other transmission line fields like gmp_sdp_tl, pps_sdp_tl, and
vsc_ext_sdp_tl?
intel_dip_cmn_sdp_transmission_line_enable() programs the CMN_SDP_TL_STGR_CTL
register using these stagger values. During a fastset taking over from BIOS,
if the BIOS programmed non-default stagger values but left the base cmn_sdp_tl
identical to the driver's default, cmn_sdp_changed() will return false.
Since intel_pipe_config_compare() ignores differences in these stagger fields,
intel_dip_cmn_sdp_transmission_line_enable() would never be called to update
CMN_SDP_TL_STGR_CTL, leaving the hardware operating with the inherited BIOS
values.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260923133307.323439-1-ankit.k.nautiyal@intel.com?part=1
next prev parent reply other threads:[~2026-09-23 14:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-23 13:33 [PATCH] drm/i915/display: Update the CMN_SDP_TL in fastset path Ankit Nautiyal
2026-09-23 14:00 ` sashiko-bot [this message]
2026-09-23 22:13 ` ✓ i915.CI.BAT: success for " Patchwork
2026-09-24 2:19 ` [PATCH v2] " Ankit Nautiyal
2026-09-24 3:40 ` Kandpal, Suraj
2026-09-24 3:29 ` ✓ i915.CI.BAT: success for drm/i915/display: Update the CMN_SDP_TL in fastset path (rev2) Patchwork
2026-09-25 2:58 ` ✗ i915.CI.Full: failure " Patchwork
2026-09-25 23:07 ` ✓ i915.CI.Full: success " Patchwork
2026-09-26 8:32 ` 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=20260923140049.B35151F000FF@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=ankit.k.nautiyal@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=sashiko-reviews@lists.linux.dev \
/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