intel-xe.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Ankit Nautiyal <ankit.k.nautiyal@intel.com>
Cc: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org,
	jani.nikula@linux.intel.com,
	mitulkumar.ajitkumar.golani@intel.com
Subject: Re: [PATCH 16/19] drm/i915/display: Use fixed_rr timings in modeset sequence
Date: Mon, 17 Feb 2025 20:56:37 +0200	[thread overview]
Message-ID: <Z7OGZY3mBy24LHYy@intel.com> (raw)
In-Reply-To: <Z7OBP8kdGZLtWCAK@intel.com>

On Mon, Feb 17, 2025 at 08:34:39PM +0200, Ville Syrjälä wrote:
> On Fri, Feb 14, 2025 at 05:41:26PM +0530, Ankit Nautiyal wrote:
> > During modeset enable sequence, program the fixed timings,
> > and turn on the VRR Timing Generator (VRR TG) for platforms
> > that always use VRR TG.
> > 
> > Later if vrr timings are required, vrr_enable() will switch
> > to the real VRR timings.
> > 
> > With this we dont want to reset TRANS_CTL_VRR Enable bit while updating
> > the vrr transcoder timings.
> > 
> > v2: Update intel_vrr_set_transcoder_timings for fixed_rr.
> > v3: Update intel_set_transcoder_timings_lrr for fixed_rr. (Ville)
> >     Add TRANS_PUSH while enabling VRR for fixed_rr.
> > 
> > Signed-off-by: Ankit Nautiyal <ankit.k.nautiyal@intel.com>
> > ---
> >  drivers/gpu/drm/i915/display/intel_display.c | 10 +++++--
> >  drivers/gpu/drm/i915/display/intel_vrr.c     | 29 ++++++++++++++++++--
> >  drivers/gpu/drm/i915/display/intel_vrr.h     |  3 ++
> >  3 files changed, 36 insertions(+), 6 deletions(-)
> > 
> > diff --git a/drivers/gpu/drm/i915/display/intel_display.c b/drivers/gpu/drm/i915/display/intel_display.c
> > index 66c5ad46bfea..c9d1c091b109 100644
> > --- a/drivers/gpu/drm/i915/display/intel_display.c
> > +++ b/drivers/gpu/drm/i915/display/intel_display.c
> > @@ -1755,6 +1755,7 @@ static void hsw_set_frame_start_delay(const struct intel_crtc_state *crtc_state)
> >  
> >  static void hsw_configure_cpu_transcoder(const struct intel_crtc_state *crtc_state)
> >  {
> > +	struct intel_display *display = to_intel_display(crtc_state);
> >  	struct intel_crtc *crtc = to_intel_crtc(crtc_state->uapi.crtc);
> >  	struct drm_i915_private *dev_priv = to_i915(crtc->base.dev);
> >  	enum transcoder cpu_transcoder = crtc_state->cpu_transcoder;
> > @@ -1770,9 +1771,12 @@ static void hsw_configure_cpu_transcoder(const struct intel_crtc_state *crtc_sta
> >  	}
> >  
> >  	intel_set_transcoder_timings(crtc_state);
> > -	if (HAS_VRR(dev_priv))
> > -		intel_vrr_set_transcoder_timings(crtc_state);
> > -
> > +	if (HAS_VRR(dev_priv)) {
> > +		if (intel_vrr_always_use_vrr_tg(display))
> > +			intel_vrr_enable_fixed_rr_timings(crtc_state);
> > +		else
> > +			intel_vrr_set_transcoder_timings(crtc_state);
> 
> I think intel_vrr_set_transcoder_timings() should just program the
> fixed timings always. And we shouldn't do anything else here.
> 
> And I think the VRR_CTL enable/disable for the always_use_vrr_tg==true
> case should be done at some more appropriate spot in the modeset
> sequence. We can add eg. intel_vrr_trancoder_{enable,disable}() for
> that part.
> 
> > +	}
> >  	if (cpu_transcoder != TRANSCODER_EDP)
> >  		intel_de_write(dev_priv, TRANS_MULT(dev_priv, cpu_transcoder),
> >  			       crtc_state->pixel_multiplier - 1);
> > diff --git a/drivers/gpu/drm/i915/display/intel_vrr.c b/drivers/gpu/drm/i915/display/intel_vrr.c
> > index e247055bc486..4151fcd0f978 100644
> > --- a/drivers/gpu/drm/i915/display/intel_vrr.c
> > +++ b/drivers/gpu/drm/i915/display/intel_vrr.c
> > @@ -456,8 +456,12 @@ void intel_vrr_set_transcoder_timings(const struct intel_crtc_state *crtc_state)
> >  		       crtc_state->vrr.vmin - 1);
> >  	intel_de_write(display, TRANS_VRR_VMAX(display, cpu_transcoder),
> >  		       crtc_state->vrr.vmax - 1);
> > -	intel_de_write(display, TRANS_VRR_CTL(display, cpu_transcoder),
> > -		       trans_vrr_ctl(crtc_state));
> > +	if (intel_vrr_always_use_vrr_tg(display))
> > +		intel_de_write(display, TRANS_VRR_CTL(display, cpu_transcoder),
> > +			       VRR_CTL_VRR_ENABLE | trans_vrr_ctl(crtc_state));
> > +	else
> > +		intel_de_write(display, TRANS_VRR_CTL(display, cpu_transcoder),
> > +			       trans_vrr_ctl(crtc_state));
> 
> We should probably remove this VRR_CTL frobbing from here entirely,
> and just always do it from the intel_vrr_trancoder_{enable,disable}().
> And obviously for the !always_use_vrr_tg case we just skip setting
> the enable bit there.

Hmm. One thing that might screw us over here is the fastboot vs.
vblank_delay stuff. We might have to allow that to reconfigure
the guardband...

In that case we need to reprogram VRR_CTL from
intel_set_transcoder_timings_lrr(), and be careful what
we do with the enable bit. So it'd perhaps have to be
something like:
 vrr_ctl = trans_vrr_ctl();
 if (always_use_vrr_tg && !needs_modeset)
	vrr_ctl |= VRR_CTL_VRR_ENABLE;

Either way we should move the guardbad and pipeline_full checks
out from the pure !fastset block in intel_pipe_config_compare().
And if we do need the fastboot stuff for them then we need to use
the allow_vblank_delay_fastset() stuff for them as well.

> 
> >  	intel_de_write(display, TRANS_VRR_FLIPLINE(display, cpu_transcoder),
> >  		       crtc_state->vrr.flipline - 1);
> >  
> > @@ -536,7 +540,6 @@ bool intel_vrr_is_push_sent(const struct intel_crtc_state *crtc_state)
> >  	return intel_de_read(display, TRANS_PUSH(display, cpu_transcoder)) & TRANS_PUSH_SEND;
> >  }
> >  
> > -static
> >  bool intel_vrr_always_use_vrr_tg(struct intel_display *display)
> >  {
> >  	if (!HAS_VRR(display))
> > @@ -616,6 +619,26 @@ void intel_vrr_disable(const struct intel_crtc_state *old_crtc_state)
> >  	intel_vrr_set_fixed_rr_timings(old_crtc_state);
> >  }
> >  
> > +void intel_vrr_enable_fixed_rr_timings(const struct intel_crtc_state *crtc_state)
> > +{
> > +	struct intel_display *display = to_intel_display(crtc_state);
> > +	enum transcoder cpu_transcoder = crtc_state->cpu_transcoder;
> > +
> > +	intel_vrr_set_fixed_rr_timings(crtc_state);
> > +
> > +	if (HAS_AS_SDP(display))
> > +		intel_de_write(display,
> > +			       TRANS_VRR_VSYNC(display, cpu_transcoder),
> > +			       VRR_VSYNC_END(crtc_state->vrr.vsync_end) |
> > +			       VRR_VSYNC_START(crtc_state->vrr.vsync_start));
> > +
> > +	intel_de_write(display, TRANS_PUSH(display, cpu_transcoder),
> > +		       TRANS_PUSH_EN);
> > +
> > +	intel_de_write(display, TRANS_VRR_CTL(display, cpu_transcoder),
> > +		       VRR_CTL_VRR_ENABLE | trans_vrr_ctl(crtc_state));
> > +}
> > +
> >  static
> >  bool intel_vrr_is_fixed_rr(const struct intel_crtc_state *crtc_state)
> >  {
> > diff --git a/drivers/gpu/drm/i915/display/intel_vrr.h b/drivers/gpu/drm/i915/display/intel_vrr.h
> > index 514822577e8a..9259964978b1 100644
> > --- a/drivers/gpu/drm/i915/display/intel_vrr.h
> > +++ b/drivers/gpu/drm/i915/display/intel_vrr.h
> > @@ -12,6 +12,7 @@ struct drm_connector_state;
> >  struct intel_atomic_state;
> >  struct intel_connector;
> >  struct intel_crtc_state;
> > +struct intel_display;
> >  struct intel_dsb;
> >  
> >  bool intel_vrr_is_capable(struct intel_connector *connector);
> > @@ -35,5 +36,7 @@ int intel_vrr_vmin_vtotal(const struct intel_crtc_state *crtc_state);
> >  int intel_vrr_vmax_vblank_start(const struct intel_crtc_state *crtc_state);
> >  int intel_vrr_vmin_vblank_start(const struct intel_crtc_state *crtc_state);
> >  int intel_vrr_vblank_delay(const struct intel_crtc_state *crtc_state);
> > +bool intel_vrr_always_use_vrr_tg(struct intel_display *display);
> > +void intel_vrr_enable_fixed_rr_timings(const struct intel_crtc_state *crtc_state);
> >  
> >  #endif /* __INTEL_VRR_H__ */
> > -- 
> > 2.45.2
> 
> -- 
> Ville Syrjälä
> Intel

-- 
Ville Syrjälä
Intel

  reply	other threads:[~2025-02-17 18:56 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-14 12:11 [PATCH 00/19] Use VRR timing generator for fixed refresh rate modes Ankit Nautiyal
2025-02-14 12:11 ` [PATCH 01/19] drm/i915/vrr: Remove unwanted comment Ankit Nautiyal
2025-02-14 12:11 ` [PATCH 02/19] drm/i915:vrr: Separate out functions to compute vmin and vmax Ankit Nautiyal
2025-02-14 12:11 ` [PATCH 03/19] drm/i915/vrr: Make helpers for cmrr and vrr timings Ankit Nautiyal
2025-02-14 12:11 ` [PATCH 04/19] drm/i915/vrr: Disable CMRR Ankit Nautiyal
2025-02-14 12:11 ` [PATCH 05/19] drm/i915/vrr: Track vrr.enable only for variable timing Ankit Nautiyal
2025-02-17 18:06   ` Ville Syrjälä
2025-02-19 12:35     ` Nautiyal, Ankit K
2025-02-14 12:11 ` [PATCH 06/19] drm/i915/vrr: Use crtc_vtotal for vmin Ankit Nautiyal
2025-02-17 18:08   ` Ville Syrjälä
2025-02-19 12:38     ` Nautiyal, Ankit K
2025-02-14 12:11 ` [PATCH 07/19] drm/i915/vrr: Prepare for fixed refresh rate timings Ankit Nautiyal
2025-02-17 18:12   ` Ville Syrjälä
2025-02-19 12:40     ` Nautiyal, Ankit K
2025-02-14 12:11 ` [PATCH 08/19] drm/i915/dp: Avoid vrr compute config for HDMI sink Ankit Nautiyal
2025-02-17 18:14   ` Ville Syrjälä
2025-02-19 12:53     ` Nautiyal, Ankit K
2025-02-19 14:59       ` Ville Syrjälä
2025-02-14 12:11 ` [PATCH 09/19] drm/i915/display: Enable MSA Ignore Timing PAR only when in not fixed_rr mode Ankit Nautiyal
2025-02-14 12:11 ` [PATCH 10/19] drm/i915/hdmi: Use VRR Timing generator for HDMI Ankit Nautiyal
2025-02-14 12:11 ` [PATCH 11/19] drm/i915/display: Disable PSR before disabling VRR Ankit Nautiyal
2025-02-14 12:11 ` [PATCH 12/19] drm/i915/display: Extend WA 14015406119 for PSR2 Ankit Nautiyal
2025-02-14 12:11 ` [PATCH 13/19] drm/i915/vrr: Handle joiner with vrr Ankit Nautiyal
2025-02-17 18:17   ` Ville Syrjälä
2025-02-19 12:56     ` Nautiyal, Ankit K
2025-02-14 12:11 ` [PATCH 14/19] drm/i915/vrr: Refactor condition for computing vmax and LRR Ankit Nautiyal
2025-02-14 12:11 ` [PATCH 15/19] drm/i915/vrr: Always set vrr vmax/vmin/flipline in vrr_{enable/disable} Ankit Nautiyal
2025-02-14 12:11 ` [PATCH 16/19] drm/i915/display: Use fixed_rr timings in modeset sequence Ankit Nautiyal
2025-02-17 18:34   ` Ville Syrjälä
2025-02-17 18:56     ` Ville Syrjälä [this message]
2025-02-19 13:57       ` Nautiyal, Ankit K
2025-02-19 15:08         ` Ville Syrjälä
2025-02-19 13:17     ` Nautiyal, Ankit K
2025-02-19 15:05       ` Ville Syrjälä
2025-02-20  5:31         ` Nautiyal, Ankit K
2025-02-14 12:11 ` [PATCH 17/19] drm/i915/display: Use fixed rr timings in intel_set_transcoder_timings_lrr() Ankit Nautiyal
2025-02-14 12:11 ` [PATCH 18/19] drm/i915/vrr: Always use VRR timing generator for MTL+ Ankit Nautiyal
2025-02-17 18:39   ` Ville Syrjälä
2025-02-14 12:11 ` [PATCH 19/19] drm/i915/display: Add fixed_rr to crtc_state dump Ankit Nautiyal
2025-02-14 12:38 ` ✓ CI.Patch_applied: success for Use VRR timing generator for fixed refresh rate modes (rev4) Patchwork
2025-02-14 12:38 ` ✓ CI.checkpatch: " Patchwork
2025-02-14 12:39 ` ✓ CI.KUnit: " Patchwork
2025-02-14 12:56 ` ✓ CI.Build: " Patchwork
2025-02-14 12:58 ` ✓ CI.Hooks: " Patchwork
2025-02-14 13:00 ` ✓ CI.checksparse: " Patchwork
2025-02-14 13:20 ` ✓ Xe.CI.BAT: " Patchwork
2025-02-15 11:06 ` ✗ 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=Z7OGZY3mBy24LHYy@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 \
    --cc=mitulkumar.ajitkumar.golani@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;
as well as URLs for NNTP newsgroup(s).