From: Jani Nikula <jani.nikula@linux.intel.com>
To: Mitul Golani <mitulkumar.ajitkumar.golani@intel.com>,
intel-gfx@lists.freedesktop.org
Cc: intel-xe@lists.freedesktop.org, ankit.k.nautiyal@intel.com,
ville.syrjala@linux.intel.com, suraj.kandpal@intel.com
Subject: Re: [PATCH RESEND v2] drm/i915/display: Program TRANS_VTOTAL from mode vtotal
Date: Thu, 02 Jul 2026 18:41:21 +0300 [thread overview]
Message-ID: <0b7919083586f3ba26159f909f87666ea9b41045@intel.com> (raw)
In-Reply-To: <20260617045850.862100-1-mitulkumar.ajitkumar.golani@intel.com>
On Wed, 17 Jun 2026, Mitul Golani <mitulkumar.ajitkumar.golani@intel.com> wrote:
> There are monitors being sensitive to MSA and end up
> blanking out when we override Vtotal, DP transcoder
> uses TRANS_VTOTAL to derive MSA VTotal. Avoid overriding
> crtc_vtotal to 1 on platform which supports VRR Timing
> generator and always program VTOTAL from mode timing in
> transcoder timing paths.
Should this have had Fixes: tag? Does it require a backport?
BR,
Jani.
>
> --v2:
> - Remove write to crtc_state->hw.adjusted_mode.crtc_vtotal
> during intel_vrr_get_config. (Ankit)
> - Fix merge conflicts.
>
> Bspec: 70001
> Cc: Ankit Nautiyal <ankit.k.nautiyal@intel.com>
> Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
> Cc: Suraj Kandpal <suraj.kandpal@intel.com>
> Signed-off-by: Mitul Golani <mitulkumar.ajitkumar.golani@intel.com>
> Reviewed-by: Suraj Kandpal <suraj.kandpal@intel.com>
> ---
> drivers/gpu/drm/i915/display/intel_display.c | 17 -----------------
> drivers/gpu/drm/i915/display/intel_vrr.c | 10 ----------
> 2 files changed, 27 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_display.c b/drivers/gpu/drm/i915/display/intel_display.c
> index e76aa6c8dab6..42eb4c5bc9b6 100644
> --- a/drivers/gpu/drm/i915/display/intel_display.c
> +++ b/drivers/gpu/drm/i915/display/intel_display.c
> @@ -2737,15 +2737,6 @@ void intel_set_transcoder_timings(const struct intel_crtc_state *crtc_state,
> HSYNC_START(adjusted_mode->crtc_hsync_start - 1) |
> HSYNC_END(adjusted_mode->crtc_hsync_end - 1));
>
> - /*
> - * For platforms that always use VRR Timing Generator, the VTOTAL.Vtotal
> - * bits are not required. Since the support for these bits is going to
> - * be deprecated in upcoming platforms, avoid writing these bits for the
> - * platforms that do not use legacy Timing Generator.
> - */
> - if (intel_vrr_always_use_vrr_tg(display))
> - crtc_vtotal = 1;
> -
> intel_de_write(display, TRANS_VTOTAL(display, transcoder),
> VACTIVE(crtc_vdisplay - 1) |
> VTOTAL(crtc_vtotal - 1));
> @@ -2834,14 +2825,6 @@ void intel_set_transcoder_timings_lrr(const struct intel_crtc_state *crtc_state,
> intel_de_write(display, TRANS_VSYNC(display, transcoder),
> VSYNC_START(adjusted_mode->crtc_vsync_start - 1) |
> VSYNC_END(adjusted_mode->crtc_vsync_end - 1));
> - /*
> - * For platforms that always use VRR Timing Generator, the VTOTAL.Vtotal
> - * bits are not required. Since the support for these bits is going to
> - * be deprecated in upcoming platforms, avoid writing these bits for the
> - * platforms that do not use legacy Timing Generator.
> - */
> - if (intel_vrr_always_use_vrr_tg(display))
> - crtc_vtotal = 1;
>
> /*
> * The double buffer latch point for TRANS_VTOTAL
> diff --git a/drivers/gpu/drm/i915/display/intel_vrr.c b/drivers/gpu/drm/i915/display/intel_vrr.c
> index cd380fe8fd01..5d9b11185296 100644
> --- a/drivers/gpu/drm/i915/display/intel_vrr.c
> +++ b/drivers/gpu/drm/i915/display/intel_vrr.c
> @@ -1102,16 +1102,6 @@ void intel_vrr_get_config(struct intel_crtc_state *crtc_state)
> crtc_state->vrr.vmin += intel_vrr_vmin_flipline_offset(display);
> }
>
> - /*
> - * For platforms that always use VRR Timing Generator, the VTOTAL.Vtotal
> - * bits are not filled. Since for these platforms TRAN_VMIN is always
> - * filled with crtc_vtotal, use TRAN_VRR_VMIN to get the vtotal for
> - * adjusted_mode.
> - */
> - if (intel_vrr_always_use_vrr_tg(display))
> - crtc_state->hw.adjusted_mode.crtc_vtotal =
> - intel_vrr_vmin_vtotal(crtc_state);
> -
> if (HAS_AS_SDP(display)) {
> trans_vrr_vsync =
> intel_de_read(display,
--
Jani Nikula, Intel
next prev parent reply other threads:[~2026-07-02 15:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-17 4:58 [PATCH RESEND v2] drm/i915/display: Program TRANS_VTOTAL from mode vtotal Mitul Golani
2026-06-17 5:57 ` ✓ CI.KUnit: success for drm/i915/display: Program TRANS_VTOTAL from mode vtotal (rev4) Patchwork
2026-06-17 6:35 ` ✓ Xe.CI.BAT: " Patchwork
2026-06-17 12:13 ` ✓ Xe.CI.FULL: " Patchwork
2026-07-02 15:41 ` Jani Nikula [this message]
2026-07-02 16:14 ` [PATCH RESEND v2] drm/i915/display: Program TRANS_VTOTAL from mode vtotal Golani, Mitulkumar Ajitkumar
2026-07-02 17:26 ` Jani Nikula
-- strict thread matches above, loose matches on Subject: below --
2026-06-17 4:45 Mitul Golani
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=0b7919083586f3ba26159f909f87666ea9b41045@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=ankit.k.nautiyal@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=mitulkumar.ajitkumar.golani@intel.com \
--cc=suraj.kandpal@intel.com \
--cc=ville.syrjala@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox