All of lore.kernel.org
 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 07/19] drm/i915/vrr: Prepare for fixed refresh rate timings
Date: Mon, 17 Feb 2025 20:12:54 +0200	[thread overview]
Message-ID: <Z7N8JhVO7cFezgyI@intel.com> (raw)
In-Reply-To: <20250214121130.1808451-8-ankit.k.nautiyal@intel.com>

On Fri, Feb 14, 2025 at 05:41:17PM +0530, Ankit Nautiyal wrote:
> Currently we always compute the timings as if vrr is enabled.
> With this approach the state checker becomes complicated when we
> introduce fixed refresh rate mode with vrr timing generator.
> 
> To avoid the complications, instead of always computing vrr timings, we
> compute vrr timings based on uapi.vrr_enable knob.
> So when the knob is disabled we always compute vmin=flipline=vmax.
> 
> Signed-off-by: Ankit Nautiyal <ankit.k.nautiyal@intel.com>
> ---
>  drivers/gpu/drm/i915/display/intel_vrr.c | 54 ++++++++++++++++++++++++
>  1 file changed, 54 insertions(+)
> 
> diff --git a/drivers/gpu/drm/i915/display/intel_vrr.c b/drivers/gpu/drm/i915/display/intel_vrr.c
> index 3bcf2a026ad3..a4ed102a2119 100644
> --- a/drivers/gpu/drm/i915/display/intel_vrr.c
> +++ b/drivers/gpu/drm/i915/display/intel_vrr.c
> @@ -263,6 +263,35 @@ int intel_vrr_fixed_rr_vtotal(const struct intel_crtc_state *crtc_state)
>  			intel_vrr_real_vblank_delay(crtc_state);
>  }
>  
> +static
> +int intel_vrr_fixed_rr_vmax(const struct intel_crtc_state *crtc_state)
> +{
> +	return intel_vrr_fixed_rr_vtotal(crtc_state);
> +}
> +
> +static
> +int intel_vrr_fixed_rr_vmin(const struct intel_crtc_state *crtc_state)
> +{
> +	struct intel_display *display = to_intel_display(crtc_state);
> +
> +	return intel_vrr_fixed_rr_vtotal(crtc_state) -
> +		intel_vrr_flipline_offset(display);
> +}
> +
> +static
> +int intel_vrr_fixed_rr_flipline(const struct intel_crtc_state *crtc_state)
> +{
> +	return intel_vrr_fixed_rr_vtotal(crtc_state);
> +}
> +
> +static
> +void intel_vrr_prepare_fixed_timings(struct intel_crtc_state *crtc_state)
> +{
> +	crtc_state->vrr.vmax = intel_vrr_fixed_rr_vmax(crtc_state);
> +	crtc_state->vrr.vmin = intel_vrr_fixed_rr_vmin(crtc_state);
> +	crtc_state->vrr.flipline = intel_vrr_fixed_rr_flipline(crtc_state);

Same comment as to the previous patch: vblank delay is not a thing
at this point, so this needs to just use the actual timings without
any adjustments.

The rest of the patch looks fine.

> +}
> +
>  static
>  int intel_vrr_compute_vmin(struct intel_crtc_state *crtc_state)
>  {
> @@ -343,6 +372,8 @@ intel_vrr_compute_config(struct intel_crtc_state *crtc_state,
>  		intel_vrr_compute_vrr_timings(crtc_state);
>  	else if (is_cmrr_frac_required(crtc_state) && is_edp)
>  		intel_vrr_compute_cmrr_timings(crtc_state);
> +	else
> +		intel_vrr_prepare_fixed_timings(crtc_state);
>  
>  	if (HAS_AS_SDP(display)) {
>  		crtc_state->vrr.vsync_start =
> @@ -514,6 +545,13 @@ void intel_vrr_enable(const struct intel_crtc_state *crtc_state)
>  	if (!crtc_state->vrr.enable)
>  		return;
>  
> +	intel_de_write(display, TRANS_VRR_VMIN(display, cpu_transcoder),
> +		       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_FLIPLINE(display, cpu_transcoder),
> +		       crtc_state->vrr.flipline - 1);
> +
>  	intel_de_write(display, TRANS_PUSH(display, cpu_transcoder),
>  		       TRANS_PUSH_EN);
>  
> @@ -527,6 +565,20 @@ void intel_vrr_enable(const struct intel_crtc_state *crtc_state)
>  	}
>  }
>  
> +static
> +void intel_vrr_set_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_de_write(display, TRANS_VRR_VMIN(display, cpu_transcoder),
> +		       intel_vrr_fixed_rr_vmin(crtc_state) - 1);
> +	intel_de_write(display, TRANS_VRR_VMAX(display, cpu_transcoder),
> +		       intel_vrr_fixed_rr_vmax(crtc_state) - 1);
> +	intel_de_write(display, TRANS_VRR_FLIPLINE(display, cpu_transcoder),
> +		       intel_vrr_fixed_rr_flipline(crtc_state) - 1);
> +}
> +
>  void intel_vrr_disable(const struct intel_crtc_state *old_crtc_state)
>  {
>  	struct intel_display *display = to_intel_display(old_crtc_state);
> @@ -541,6 +593,8 @@ void intel_vrr_disable(const struct intel_crtc_state *old_crtc_state)
>  				TRANS_VRR_STATUS(display, cpu_transcoder),
>  				VRR_STATUS_VRR_EN_LIVE, 1000);
>  	intel_de_write(display, TRANS_PUSH(display, cpu_transcoder), 0);
> +
> +	intel_vrr_set_fixed_rr_timings(old_crtc_state);
>  }
>  
>  static
> -- 
> 2.45.2

-- 
Ville Syrjälä
Intel

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

Thread overview: 50+ 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ä [this message]
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ä
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:44 ` ✗ Fi.CI.SPARSE: warning for Use VRR timing generator for fixed refresh rate modes (rev9) Patchwork
2025-02-14 12:56 ` ✓ CI.Build: success for Use VRR timing generator for fixed refresh rate modes (rev4) Patchwork
2025-02-14 12:58 ` ✓ CI.Hooks: " Patchwork
2025-02-14 13:00 ` ✓ CI.checksparse: " Patchwork
2025-02-14 13:02 ` ✓ i915.CI.BAT: success for Use VRR timing generator for fixed refresh rate modes (rev9) Patchwork
2025-02-14 13:20 ` ✓ Xe.CI.BAT: success for Use VRR timing generator for fixed refresh rate modes (rev4) Patchwork
2025-02-14 15:26 ` ✗ i915.CI.Full: failure for Use VRR timing generator for fixed refresh rate modes (rev9) Patchwork
2025-02-15 11:06 ` ✗ Xe.CI.Full: failure for Use VRR timing generator for fixed refresh rate modes (rev4) 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=Z7N8JhVO7cFezgyI@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 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.