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 18/20] drm/i915/vrr: Use fixed timings for platforms that support VRR
Date: Fri, 28 Feb 2025 18:01:37 +0530 [thread overview]
Message-ID: <a9bc6c3b-ee6f-48ed-9601-53112deb88db@intel.com> (raw)
In-Reply-To: <Z8DTmGHA4qptFxjG@intel.com>
On 2/28/2025 2:35 AM, Ville Syrjälä wrote:
> On Thu, Feb 27, 2025 at 04:31:28PM +0530, Nautiyal, Ankit K wrote:
>> On 2/26/2025 8:41 PM, Ville Syrjälä wrote:
>>> On Mon, Feb 24, 2025 at 11:47:15AM +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.
>>>> For platforms that do support VRR, readback vrr timings whether or not
>>>> VRR_CTL_FLIP_LINE_EN is set in VRR_CTL or not.
>>>>
>>>> Signed-off-by: Ankit Nautiyal <ankit.k.nautiyal@intel.com>
>>>> ---
>>>> drivers/gpu/drm/i915/display/intel_vrr.c | 43 ++++++++++++------------
>>>> 1 file changed, 22 insertions(+), 21 deletions(-)
>>>>
>>>> diff --git a/drivers/gpu/drm/i915/display/intel_vrr.c b/drivers/gpu/drm/i915/display/intel_vrr.c
>>>> index 551dcc16f0d4..975fed9930c1 100644
>>>> --- a/drivers/gpu/drm/i915/display/intel_vrr.c
>>>> +++ b/drivers/gpu/drm/i915/display/intel_vrr.c
>>>> @@ -344,6 +344,9 @@ intel_vrr_compute_config(struct intel_crtc_state *crtc_state,
>>>> struct drm_display_mode *adjusted_mode = &crtc_state->hw.adjusted_mode;
>>>> int vmin = 0, vmax = 0;
>>>>
>>>> + if (!HAS_VRR(display))
>>>> + return;
>>>> +
>>>> if (adjusted_mode->flags & DRM_MODE_FLAG_INTERLACE)
>>>> return;
>>>>
>>>> @@ -358,9 +361,6 @@ intel_vrr_compute_config(struct intel_crtc_state *crtc_state,
>>>>
>>>> vmin = intel_vrr_compute_vmin(crtc_state);
>>>>
>>>> - if (vmin >= vmax)
>>>> - return;
>>>> -
>>>> crtc_state->vrr.vmin = vmin;
>>>> crtc_state->vrr.vmax = vmax;
>>> I think your earlier pathc left vmax==0 here for the !in_range so
>>> this looks a bit wrong. But if you change the earlier patch like I
>>> suggested to set vmax=vmin then this would be fine.
>> Right, will set the vmax=vmin, as discussed in the earlier patch.
>>
>>
>>>>
>>>> @@ -373,7 +373,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);
>>>> @@ -640,6 +640,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;
>>> I think the caller is already checking that. But I suppose we could
>>> move the checks into the VRR code.
>>>
>>>> +
>>>> trans_vrr_ctl = intel_de_read(display,
>>>> TRANS_VRR_CTL(display, cpu_transcoder));
>>>>
>>>> @@ -663,23 +666,21 @@ void intel_vrr_get_config(struct intel_crtc_state *crtc_state)
>>>> crtc_state->vrr.pipeline_full =
>>>> REG_FIELD_GET(VRR_CTL_PIPELINE_FULL_MASK, trans_vrr_ctl);
>>>>
>>>> - if (trans_vrr_ctl & VRR_CTL_FLIP_LINE_EN) {
>>>> - crtc_state->vrr.flipline = intel_de_read(display,
>>>> - TRANS_VRR_FLIPLINE(display, cpu_transcoder)) + 1;
>>>> - crtc_state->vrr.vmax = intel_de_read(display,
>>>> - TRANS_VRR_VMAX(display, cpu_transcoder)) + 1;
>>>> - crtc_state->vrr.vmin = intel_de_read(display,
>>>> - TRANS_VRR_VMIN(display, cpu_transcoder)) + 1;
>>>> -
>>>> - if (HAS_AS_SDP(display)) {
>>>> - trans_vrr_vsync =
>>>> - intel_de_read(display,
>>>> - TRANS_VRR_VSYNC(display, cpu_transcoder));
>>>> - crtc_state->vrr.vsync_start =
>>>> - REG_FIELD_GET(VRR_VSYNC_START_MASK, trans_vrr_vsync);
>>>> - crtc_state->vrr.vsync_end =
>>>> - REG_FIELD_GET(VRR_VSYNC_END_MASK, trans_vrr_vsync);
>>>> - }
>>> I think you want to keep the VRR_CTL_FLIP_LINE_EN check around the
>>> TRANS_VRR_FLIPLINE read at least, because we want the state checker
>>> to catch any misprogrammng of VRR_CTL_FLIP_LINE_EN.
>> Alright, will remove this change.
>>
>>
>> There is one more thing I wanted your opinion on:
>>
>> For PTL+, the support for TRANS_VTOTAL.Vtotal bits is going away.
> Aren't we still using the legacy timing gnerator currently on ptl?
> I think I did manage to run upstream code on a ptl somehwat
> succesfully, and I don't remeber any state checker warns or other
> real problems (which I would expect to happen if we don't have a
> working vtotal programmed in).
For PTL the support for legacy timing generator is still there but its
recommended to switch to VRR Timing generator.
GOP I think has already moved in that direction.
>
>> I can
>> skip writing it based on the intel_vrr_always_use_vrr_tg(), but how
>> should I fill adjusted_mode->crtc_vtotal during readout?
>>
>> Can we use vrr.vmin for that? Or should we just remove the state checker
>> for crtc_vtotal for platforms where this applies?
> I think reading it out from VMIN would be the way to go. Otherwise
> we'd have to somehow stop using crtc_vtotal everywhere and that sounds
> like a lot of work.
Will try to have this read from VRR.Vmin.
Regards,
Ankit
>
>> I am intending to include this change as the last patch of the series.
>>
>> Thanks again for all the reviews and suggestions.
>>
>>
>> Regards,
>>
>> Ankit
>>
>>
>>>> + crtc_state->vrr.flipline = intel_de_read(display,
>>>> + TRANS_VRR_FLIPLINE(display, cpu_transcoder)) + 1;
>>>> + crtc_state->vrr.vmax = intel_de_read(display,
>>>> + TRANS_VRR_VMAX(display, cpu_transcoder)) + 1;
>>>> + crtc_state->vrr.vmin = intel_de_read(display,
>>>> + TRANS_VRR_VMIN(display, cpu_transcoder)) + 1;
>>>> +
>>>> + if (HAS_AS_SDP(display)) {
>>>> + trans_vrr_vsync =
>>>> + intel_de_read(display,
>>>> + TRANS_VRR_VSYNC(display, cpu_transcoder));
>>>> + crtc_state->vrr.vsync_start =
>>>> + REG_FIELD_GET(VRR_VSYNC_START_MASK, trans_vrr_vsync);
>>>> + crtc_state->vrr.vsync_end =
>>>> + REG_FIELD_GET(VRR_VSYNC_END_MASK, trans_vrr_vsync);
>>>> }
>>>>
>>>> crtc_state->vrr.enable = trans_vrr_ctl & VRR_CTL_VRR_ENABLE &&
>>>> --
>>>> 2.45.2
next prev parent reply other threads:[~2025-02-28 12:32 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-24 6:16 [PATCH 00/20] Use VRR timing generator for fixed refresh rate modes Ankit Nautiyal
2025-02-24 6:16 ` [PATCH 01/20] drm/i915/vrr: Remove unwanted comment Ankit Nautiyal
2025-02-26 13:06 ` Ville Syrjälä
2025-02-24 6:16 ` [PATCH 02/20] drm/i915:vrr: Separate out functions to compute vmin and vmax Ankit Nautiyal
2025-02-26 12:59 ` Ville Syrjälä
2025-02-27 10:13 ` Nautiyal, Ankit K
2025-02-24 6:17 ` [PATCH 03/20] drm/i915/vrr: Make helpers for cmrr and vrr timings Ankit Nautiyal
2025-02-26 13:07 ` Ville Syrjälä
2025-02-24 6:17 ` [PATCH 04/20] drm/i915/vrr: Disable CMRR Ankit Nautiyal
2025-02-26 13:08 ` Ville Syrjälä
2025-02-24 6:17 ` [PATCH 05/20] drm/i915/vrr: Track vrr.enable only for variable timing Ankit Nautiyal
2025-02-26 13:10 ` Ville Syrjälä
2025-02-27 10:16 ` Nautiyal, Ankit K
2025-02-24 6:17 ` [PATCH 06/20] drm/i915/vrr: Use crtc_vtotal for vmin Ankit Nautiyal
2025-02-26 13:11 ` Ville Syrjälä
2025-02-24 6:17 ` [PATCH 07/20] drm/i915/vrr: Prepare for fixed refresh rate timings Ankit Nautiyal
2025-02-26 13:13 ` Ville Syrjälä
2025-02-24 6:17 ` [PATCH 08/20] drm/i915/display: Enable MSA Ignore Timing PAR only when in not fixed_rr mode Ankit Nautiyal
2025-02-26 13:27 ` Ville Syrjälä
2025-02-27 10:19 ` Nautiyal, Ankit K
2025-02-24 6:17 ` [PATCH 09/20] drm/i915/hdmi: Use VRR Timing generator for HDMI Ankit Nautiyal
2025-02-26 13:30 ` Ville Syrjälä
2025-02-27 10:31 ` Nautiyal, Ankit K
2025-02-24 6:17 ` [PATCH 10/20] drm/i915/dp_mst: Use VRR Timing generator for DP MST Ankit Nautiyal
2025-02-26 13:30 ` Ville Syrjälä
2025-02-24 6:17 ` [PATCH 11/20] drm/i915/display: Disable PSR before disabling VRR Ankit Nautiyal
2025-02-26 13:45 ` Ville Syrjälä
2025-02-27 10:33 ` Nautiyal, Ankit K
2025-02-24 6:17 ` [PATCH 12/20] drm/i915/display: Extend WA 14015406119 for PSR2 Ankit Nautiyal
2025-02-26 13:55 ` Ville Syrjälä
2025-02-27 10:36 ` Nautiyal, Ankit K
2025-02-24 6:17 ` [PATCH 13/20] drm/i915/vrr: Handle joiner with vrr Ankit Nautiyal
2025-02-24 13:47 ` Nautiyal, Ankit K
2025-02-26 15:14 ` Ville Syrjälä
2025-02-27 10:37 ` Nautiyal, Ankit K
2025-02-24 6:17 ` [PATCH 14/20] drm/i915/vrr: Refactor condition for computing vmax and LRR Ankit Nautiyal
2025-02-26 14:01 ` Ville Syrjälä
2025-02-27 10:39 ` Nautiyal, Ankit K
2025-02-24 6:17 ` [PATCH 15/20] drm/i915/vrr: Always set vrr vmax/vmin/flipline in vrr_{enable/disable} Ankit Nautiyal
2025-02-26 14:01 ` Ville Syrjälä
2025-02-24 6:17 ` [PATCH 16/20] drm/i915/display: Use fixed rr timings in intel_set_transcoder_timings_lrr() Ankit Nautiyal
2025-02-26 15:00 ` Ville Syrjälä
2025-02-27 10:28 ` Nautiyal, Ankit K
2025-02-24 6:17 ` [PATCH 17/20] drm/i915/display: Use fixed_rr timings in modeset sequence Ankit Nautiyal
2025-02-26 15:06 ` Ville Syrjälä
2025-02-26 16:04 ` Ville Syrjälä
2025-02-27 10:44 ` Nautiyal, Ankit K
2025-02-27 10:42 ` Nautiyal, Ankit K
2025-02-24 6:17 ` [PATCH 18/20] drm/i915/vrr: Use fixed timings for platforms that support VRR Ankit Nautiyal
2025-02-26 15:11 ` Ville Syrjälä
2025-02-27 11:01 ` Nautiyal, Ankit K
2025-02-27 21:05 ` Ville Syrjälä
2025-02-28 12:31 ` Nautiyal, Ankit K [this message]
2025-02-24 6:17 ` [PATCH 19/20] drm/i915/vrr: Always use VRR timing generator for MTL+ Ankit Nautiyal
2025-02-24 6:17 ` [PATCH 20/20] drm/i915/display: Add fixed_rr to crtc_state dump Ankit Nautiyal
2025-02-24 17:59 ` ✓ CI.Patch_applied: success for Use VRR timing generator for fixed refresh rate modes (rev5) Patchwork
2025-02-24 17:59 ` ✓ CI.checkpatch: " Patchwork
2025-02-24 18:00 ` ✓ CI.KUnit: " Patchwork
2025-02-24 18:17 ` ✓ CI.Build: " Patchwork
2025-02-24 18:19 ` ✓ CI.Hooks: " Patchwork
2025-02-24 18:21 ` ✗ CI.checksparse: warning " Patchwork
2025-02-24 18:39 ` ✓ Xe.CI.BAT: success " Patchwork
2025-02-24 20:03 ` ✗ 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=a9bc6c3b-ee6f-48ed-9601-53112deb88db@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