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 07/22] drm/i915/vrr: Prepare for fixed refresh rate timings
Date: Wed, 5 Mar 2025 14:00:26 +0530 [thread overview]
Message-ID: <c136da5d-6e46-44a3-a9df-5798146e4dab@intel.com> (raw)
In-Reply-To: <Z8dLQPox84RBqlNU@intel.com>
On 3/5/2025 12:19 AM, Ville Syrjälä wrote:
> On Tue, Mar 04, 2025 at 01:49:33PM +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.
>>
>> v2: Use actual timings without any adjustments while preparing for
>> fixed timings in compute_config. (Ville)
>> v3: Avoid setting fixed timings if !vrr_possible().
>>
>> Signed-off-by: Ankit Nautiyal <ankit.k.nautiyal@intel.com>
>> Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com> (#v2)
>> ---
>> drivers/gpu/drm/i915/display/intel_vrr.c | 73 ++++++++++++++++++++++++
>> 1 file changed, 73 insertions(+)
>>
>> diff --git a/drivers/gpu/drm/i915/display/intel_vrr.c b/drivers/gpu/drm/i915/display/intel_vrr.c
>> index e0573e28014b..0e606dfe4a56 100644
>> --- a/drivers/gpu/drm/i915/display/intel_vrr.c
>> +++ b/drivers/gpu/drm/i915/display/intel_vrr.c
>> @@ -246,6 +246,68 @@ void intel_vrr_compute_vrr_timings(struct intel_crtc_state *crtc_state)
>> crtc_state->mode_flags |= I915_MODE_FLAG_VRR;
>> }
>>
>> +/*
>> + * For fixed refresh rate mode Vmin, Vmax and Flipline all are set to
>> + * Vtotal value.
>> + */
>> +static
>> +int intel_vrr_fixed_rr_vtotal(const struct intel_crtc_state *crtc_state)
>> +{
>> + struct intel_display *display = to_intel_display(crtc_state);
>> + int crtc_vtotal = crtc_state->hw.adjusted_mode.crtc_vtotal;
>> +
>> + if (DISPLAY_VER(display) >= 13)
>> + return crtc_vtotal;
>> + else
>> + return crtc_vtotal -
>> + 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_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;
>> +
>> + if (!intel_vrr_possible(crtc_state))
>> + return;
>> +
>> + 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);
>> +}
>> +
>> +static
>> +void intel_vrr_prepare_fixed_timings(struct intel_crtc_state *crtc_state)
>> +{
>> + crtc_state->vrr.vmax = intel_vrr_vmin_flipline(crtc_state);
>> + crtc_state->vrr.flipline = intel_vrr_vmin_flipline(crtc_state);
> I think it would be cleaner to just use crtc_vtotal during
> all this timing compute stuff, and move the magic vmin
> adjustment to be done after it's all done.
Alright so IIUC for fixed timings case :
crtc_state->vrr.vmax = crtc_state->hw.adjusted_mode.crtc_vtotal;
crtc_state->vrr.flipline = crtc_state->hw.adjusted_mode.crtc_vtotal;
And will move crtc_state->vrr.vmin -=
intel_vrr_flipline_offset(display); after all compute timings is done.
>
>> +}
>> +
>> static
>> int intel_vrr_compute_vmin(struct intel_crtc_state *crtc_state)
>> {
>> @@ -325,6 +387,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);
> The "compute" vs. "prepare" difference in terminology is a bit
> confusing.
Can change this to `intel_vrr_compute_fixed_rr_timings()`
Regards,
Ankit
>
>>
>> if (HAS_AS_SDP(display)) {
>> crtc_state->vrr.vsync_start =
>> @@ -496,6 +560,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);
>>
>> @@ -523,6 +594,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
next prev parent reply other threads:[~2025-03-05 8:30 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 [this message]
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
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=c136da5d-6e46-44a3-a9df-5798146e4dab@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