From: "Nautiyal, Ankit K" <ankit.k.nautiyal@intel.com>
To: "Ville Syrjälä" <ville.syrjala@linux.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/22] drm/i915/vrr: Use fixed timings for platforms that support VRR
Date: Wed, 5 Mar 2025 14:16:44 +0530 [thread overview]
Message-ID: <f85c0746-0923-4ae5-b0d3-d750590b42b1@intel.com> (raw)
In-Reply-To: <Z8dMNIG2H9FuG9Qi@intel.com>
On 3/5/2025 12:23 AM, Ville Syrjälä wrote:
> On Tue, Mar 04, 2025 at 01:49:42PM +0530, Ankit Nautiyal wrote:
>> For fixed refresh rate use fixed timings for all platforms that support
>> VRR. For this add checks to avoid computing and reading VRR for
>> platforms that do not support VRR.
>>
>> v2: Avoid touching check for VRR_CTL_FLIP_LINE_EN. (Ville)
>>
>> Signed-off-by: Ankit Nautiyal <ankit.k.nautiyal@intel.com>
>> ---
>> drivers/gpu/drm/i915/display/intel_vrr.c | 11 ++++++++---
>> 1 file changed, 8 insertions(+), 3 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/i915/display/intel_vrr.c b/drivers/gpu/drm/i915/display/intel_vrr.c
>> index 97040ab9ed86..11f23affd13a 100644
>> --- a/drivers/gpu/drm/i915/display/intel_vrr.c
>> +++ b/drivers/gpu/drm/i915/display/intel_vrr.c
>> @@ -347,6 +347,9 @@ intel_vrr_compute_config(struct intel_crtc_state *crtc_state,
>> struct drm_display_mode *adjusted_mode = &crtc_state->hw.adjusted_mode;
>> int vmin, vmax;
>>
>> + if (!HAS_VRR(display))
>> + return;
>> +
>> /*
>> * FIXME all joined pipes share the same transcoder.
>> * Need to account for that during VRR toggle/push/etc.
>> @@ -370,8 +373,7 @@ intel_vrr_compute_config(struct intel_crtc_state *crtc_state,
>> vmax = vmin;
>> }
>>
>> - if (vmin >= vmax)
>> - return;
>> + vmin = intel_vrr_compute_vmin(crtc_state);
> Didn't we already do that?
(facepalm) Yes, indeed, this is already set in an earlier patch. It
should be removed. Thanks for catching this.
>
>>
>> crtc_state->vrr.vmin = vmin;
>> crtc_state->vrr.vmax = vmax;
>> @@ -385,7 +387,7 @@ intel_vrr_compute_config(struct intel_crtc_state *crtc_state,
>> */
>> crtc_state->vrr.vmin -= intel_vrr_flipline_offset(display);
>>
>> - if (crtc_state->uapi.vrr_enabled)
>> + if (crtc_state->uapi.vrr_enabled && vmin < vmax)
>> intel_vrr_compute_vrr_timings(crtc_state);
>> else if (is_cmrr_frac_required(crtc_state) && is_edp)
>> intel_vrr_compute_cmrr_timings(crtc_state);
>> @@ -659,6 +661,9 @@ void intel_vrr_get_config(struct intel_crtc_state *crtc_state)
>> enum transcoder cpu_transcoder = crtc_state->cpu_transcoder;
>> u32 trans_vrr_ctl, trans_vrr_vsync;
>>
>> + if (!HAS_VRR(display))
>> + return;
>> +
> The caller already checks that, so should not be needed here.
Will remove this check from here.
Regards,
Ankit
>
>> trans_vrr_ctl = intel_de_read(display,
>> TRANS_VRR_CTL(display, cpu_transcoder));
>>
>> --
>> 2.45.2
next prev parent reply other threads:[~2025-03-05 8:47 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-04 8:19 [PATCH 00/22] Use VRR timing generator for fixed refresh rate modes Ankit Nautiyal
2025-03-04 8:19 ` [PATCH 01/22] drm/i915/vrr: Remove unwanted comment Ankit Nautiyal
2025-03-04 8:19 ` [PATCH 02/22] drm/i915:vrr: Separate out functions to compute vmin and vmax Ankit Nautiyal
2025-03-04 8:19 ` [PATCH 03/22] drm/i915/vrr: Make helpers for cmrr and vrr timings Ankit Nautiyal
2025-03-04 8:19 ` [PATCH 04/22] drm/i915/vrr: Disable CMRR Ankit Nautiyal
2025-03-04 8:19 ` [PATCH 05/22] drm/i915/vrr: Track vrr.enable only for variable timing Ankit Nautiyal
2025-03-04 8:19 ` [PATCH 06/22] drm/i915/vrr: Use crtc_vtotal for vmin Ankit Nautiyal
2025-03-04 8:19 ` [PATCH 07/22] drm/i915/vrr: Prepare for fixed refresh rate timings Ankit Nautiyal
2025-03-04 18:49 ` Ville Syrjälä
2025-03-05 8:30 ` Nautiyal, Ankit K
2025-03-04 8:19 ` [PATCH 08/22] drm/i915/display: Enable MSA Ignore Timing PAR only when in not fixed_rr mode Ankit Nautiyal
2025-03-04 8:19 ` [PATCH 09/22] drm/i915/hdmi: Use VRR Timing generator for HDMI for fixed_rr Ankit Nautiyal
2025-03-04 8:19 ` [PATCH 10/22] drm/i915/dp_mst: Use VRR Timing generator for DP MST " Ankit Nautiyal
2025-03-04 8:19 ` [PATCH 11/22] drm/i915/display: Disable PSR before disabling VRR Ankit Nautiyal
2025-03-04 8:19 ` [PATCH 12/22] drm/i915/display: Move intel_psr_post_plane_update() at the later Ankit Nautiyal
2025-03-04 8:19 ` [PATCH 13/22] drm/i915/vrr: Refactor condition for computing vmax and LRR Ankit Nautiyal
2025-03-04 8:19 ` [PATCH 14/22] drm/i915/vrr: Always set vrr vmax/vmin/flipline in vrr_{enable/disable} Ankit Nautiyal
2025-03-04 8:19 ` [PATCH 15/22] drm/i915/display: Use fixed_rr timings in modeset sequence Ankit Nautiyal
2025-03-04 18:50 ` Ville Syrjälä
2025-03-05 8:41 ` Nautiyal, Ankit K
2025-03-05 12:53 ` Ville Syrjälä
2025-03-05 14:45 ` Nautiyal, Ankit K
2025-03-04 8:19 ` [PATCH 16/22] drm/i915/vrr: Use fixed timings for platforms that support VRR Ankit Nautiyal
2025-03-04 18:53 ` Ville Syrjälä
2025-03-05 8:46 ` Nautiyal, Ankit K [this message]
2025-03-04 8:19 ` [PATCH 17/22] drm/i915/display: Move vrr.guardband/pipeline_full out of !fastset block Ankit Nautiyal
2025-03-04 8:19 ` [PATCH 18/22] drm/i915/display: Use fixed rr timings in intel_set_transcoder_timings_lrr() Ankit Nautiyal
2025-03-04 18:56 ` Ville Syrjälä
2025-03-05 8:52 ` Nautiyal, Ankit K
2025-03-04 8:19 ` [PATCH 19/22] drm/i915/vrr: Allow fixed_rr with pipe joiner Ankit Nautiyal
2025-03-04 19:07 ` Ville Syrjälä
2025-03-05 9:35 ` Nautiyal, Ankit K
2025-03-04 8:19 ` [PATCH 20/22] drm/i915/vrr: Always use VRR timing generator for MTL+ Ankit Nautiyal
2025-03-04 8:19 ` [PATCH 21/22] drm/i915/display: Add fixed_rr to crtc_state dump Ankit Nautiyal
2025-03-04 8:19 ` [PATCH 22/22] drm/i915/display: Avoid use of VTOTAL.Vtotal bits Ankit Nautiyal
2025-03-04 9:16 ` ✓ CI.Patch_applied: success for Use VRR timing generator for fixed refresh rate modes (rev6) Patchwork
2025-03-04 9:17 ` ✗ CI.checkpatch: warning " Patchwork
2025-03-04 9:18 ` ✓ CI.KUnit: success " Patchwork
2025-03-04 9:35 ` ✓ CI.Build: " Patchwork
2025-03-04 9:37 ` ✓ CI.Hooks: " Patchwork
2025-03-04 9:38 ` ✗ CI.checksparse: warning " Patchwork
2025-03-04 10:04 ` ✗ Xe.CI.BAT: failure " Patchwork
2025-03-04 11:18 ` ✗ 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=f85c0746-0923-4ae5-b0d3-d750590b42b1@intel.com \
--to=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 \
--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