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/22] drm/i915/display: Use fixed rr timings in intel_set_transcoder_timings_lrr()
Date: Wed, 5 Mar 2025 14:22:59 +0530 [thread overview]
Message-ID: <d2e5cb75-3165-46f3-835b-2a9cd3d9e22c@intel.com> (raw)
In-Reply-To: <Z8dM0XNVzXeHX_ow@intel.com>
On 3/5/2025 12:26 AM, Ville Syrjälä wrote:
> On Tue, Mar 04, 2025 at 01:49:44PM +0530, Ankit Nautiyal wrote:
>> To have Guardband/Pipeline_full reconfigured seamlessly, move the
>> guardband and pipeline_full from intel_pipe_config_compare() to fastboot
>> exception.
>> Update the intel_set_transcoder_timings_lrr() function to use
>> fixed refresh rate timings for platforms which always use
>> VRR timing generator.
>>
>> Signed-off-by: Ankit Nautiyal <ankit.k.nautiyal@intel.com>
>> ---
>> drivers/gpu/drm/i915/display/intel_display.c | 9 +++++++--
>> drivers/gpu/drm/i915/display/intel_vrr.c | 1 -
>> drivers/gpu/drm/i915/display/intel_vrr.h | 1 +
>> 3 files changed, 8 insertions(+), 3 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/i915/display/intel_display.c b/drivers/gpu/drm/i915/display/intel_display.c
>> index 3e8ceafcbbb4..c31a87d8afd3 100644
>> --- a/drivers/gpu/drm/i915/display/intel_display.c
>> +++ b/drivers/gpu/drm/i915/display/intel_display.c
>> @@ -2768,6 +2768,9 @@ static void intel_set_transcoder_timings_lrr(const struct intel_crtc_state *crtc
>> intel_de_write(dev_priv, TRANS_VTOTAL(dev_priv, cpu_transcoder),
>> VACTIVE(crtc_vdisplay - 1) |
>> VTOTAL(crtc_vtotal - 1));
>> +
>> + intel_vrr_set_fixed_rr_timings(crtc_state);
>> + intel_vrr_transcoder_enable(crtc_state);
>> }
>>
>> static void intel_set_pipe_src_size(const struct intel_crtc_state *crtc_state)
>> @@ -5418,8 +5421,10 @@ intel_pipe_config_compare(const struct intel_crtc_state *current_config,
>> PIPE_CONF_CHECK_BOOL(cmrr.enable);
>> }
>>
>> - PIPE_CONF_CHECK_I(vrr.pipeline_full);
>> - PIPE_CONF_CHECK_I(vrr.guardband);
>> + if (!fastset && !allow_vblank_delay_fastset(current_config)) {
> Should be ||, but I think this would still break LRR.
Will fix to ||.
Yes this is breaking seamless switch to LRR, as also mentioned in last
version.
The Bspec: 68917 mentions to disable VRR first for LNL.
For PTL it seems to just mention to set Flipline = Vmax and the fact
that Vmin/Flipline/Vmax can be set to any refresh rate supported by panel.
Whether its safe to change guardband for PTL, not much sure.
Regards,
Ankit
>
>> + PIPE_CONF_CHECK_I(vrr.pipeline_full);
>> + PIPE_CONF_CHECK_I(vrr.guardband);
>> + }
>>
>> #undef PIPE_CONF_CHECK_X
>> #undef PIPE_CONF_CHECK_I
>> diff --git a/drivers/gpu/drm/i915/display/intel_vrr.c b/drivers/gpu/drm/i915/display/intel_vrr.c
>> index 11f23affd13a..0dfe6220ff4a 100644
>> --- a/drivers/gpu/drm/i915/display/intel_vrr.c
>> +++ b/drivers/gpu/drm/i915/display/intel_vrr.c
>> @@ -284,7 +284,6 @@ 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);
>> diff --git a/drivers/gpu/drm/i915/display/intel_vrr.h b/drivers/gpu/drm/i915/display/intel_vrr.h
>> index c81f98f83b58..0e1becd7a0c0 100644
>> --- a/drivers/gpu/drm/i915/display/intel_vrr.h
>> +++ b/drivers/gpu/drm/i915/display/intel_vrr.h
>> @@ -38,5 +38,6 @@ 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);
>> void intel_vrr_transcoder_enable(const struct intel_crtc_state *crtc_state);
>> void intel_vrr_transcoder_disable(const struct intel_crtc_state *crtc_state);
>> +void intel_vrr_set_fixed_rr_timings(const struct intel_crtc_state *crtc_state);
>>
>> #endif /* __INTEL_VRR_H__ */
>> --
>> 2.45.2
next prev parent reply other threads:[~2025-03-05 8:53 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
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 [this message]
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=d2e5cb75-3165-46f3-835b-2a9cd3d9e22c@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