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 15/16] drm/i915/vrr: Always use VRR timing generator for PTL+
Date: Fri, 21 Mar 2025 19:47:12 +0200 [thread overview]
Message-ID: <Z92mIPHsmQaWuFW5@intel.com> (raw)
In-Reply-To: <20250318073540.2773890-16-ankit.k.nautiyal@intel.com>
On Tue, Mar 18, 2025 at 01:05:39PM +0530, Ankit Nautiyal wrote:
> Currently, the VRR timing generator is used only when VRR is enabled by
> userspace for sinks that support VRR. Starting with PTL+, gradually move
> away from the legacy timing generator and use the VRR timing generator
> for both variable and fixed timings.
>
> Note: For platforms where we always enable the VRR timing generator,
> the LRR fastset is not allowed to avoid live programming of vrr.guardband
> with VRR TG enabled. This effectively breaks the LRR fastset functionality
> for these platforms and needs to be addressed.
>
> v2: Use this for PTL for now to avoid losing LRR fastset for older
> platforms. (Ville)
>
> Signed-off-by: Ankit Nautiyal <ankit.k.nautiyal@intel.com>
Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> ---
> drivers/gpu/drm/i915/display/intel_vrr.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_vrr.c b/drivers/gpu/drm/i915/display/intel_vrr.c
> index c1cdd1918c19..6c6bb868381c 100644
> --- a/drivers/gpu/drm/i915/display/intel_vrr.c
> +++ b/drivers/gpu/drm/i915/display/intel_vrr.c
> @@ -553,7 +553,9 @@ bool intel_vrr_always_use_vrr_tg(struct intel_display *display)
> if (!HAS_VRR(display))
> return false;
>
> - /* #TODO return true for platforms supporting fixed_rr */
> + if (DISPLAY_VER(display) >= 30)
> + return true;
> +
> return false;
> }
>
> --
> 2.45.2
--
Ville Syrjälä
Intel
next prev parent reply other threads:[~2025-03-21 17:47 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-18 7:35 [PATCH 00/16] Use VRR timing generator for fixed refresh rate modes Ankit Nautiyal
2025-03-18 7:35 ` [PATCH 01/16] drm/i915/display: Add fixed_rr to crtc_state dump Ankit Nautiyal
2025-03-18 7:35 ` [PATCH 02/16] drm/i915/vrr: Avoid reading vrr.enable based on fixed_rr check Ankit Nautiyal
2025-03-21 17:34 ` Ville Syrjälä
2025-03-21 17:40 ` Nautiyal, Ankit K
2025-03-21 17:45 ` Ville Syrjälä
2025-03-18 7:35 ` [PATCH 03/16] drm/i915/hdmi: Use VRR Timing generator for HDMI for fixed_rr Ankit Nautiyal
2025-03-18 7:35 ` [PATCH 04/16] drm/i915/dp_mst: Use VRR Timing generator for DP MST " Ankit Nautiyal
2025-03-21 17:42 ` Ville Syrjälä
2025-03-18 7:35 ` [PATCH 05/16] drm/i915/display: Disable PSR before disabling VRR Ankit Nautiyal
2025-03-18 7:35 ` [PATCH 06/16] drm/i915/display: Move intel_psr_post_plane_update() at the later Ankit Nautiyal
2025-03-21 17:43 ` Ville Syrjälä
2025-03-24 6:37 ` Hogander, Jouni
2025-03-18 7:35 ` [PATCH 07/16] drm/i915/vrr: Refactor condition for computing vmax and LRR Ankit Nautiyal
2025-03-18 7:35 ` [PATCH 08/16] drm/i915/vrr: Always set vrr vmax/vmin/flipline in vrr_{enable/disable} Ankit Nautiyal
2025-03-18 7:35 ` [PATCH 09/16] drm/i915/vrr: Set vrr.enable for VRR TG with fixed_rr Ankit Nautiyal
2025-03-21 17:44 ` Ville Syrjälä
2025-03-18 7:35 ` [PATCH 10/16] drm/i915/display: Use fixed_rr timings in modeset sequence Ankit Nautiyal
2025-03-19 14:36 ` Ville Syrjälä
2025-03-20 5:39 ` Nautiyal, Ankit K
2025-03-24 12:10 ` Nautiyal, Ankit K
2025-03-20 4:20 ` Ankit Nautiyal
2025-03-18 7:35 ` [PATCH 11/16] drm/i915/vrr: Use fixed timings for platforms that support VRR Ankit Nautiyal
2025-03-18 7:35 ` [PATCH 12/16] drm/i915/display: Use fixed rr timings in intel_set_transcoder_timings_lrr() Ankit Nautiyal
2025-03-18 7:35 ` [PATCH 13/16] drm/i915/display: Move vrr.guardband/pipeline_full out of !fastset block Ankit Nautiyal
2025-03-18 7:35 ` [PATCH 14/16] drm/i915/vrr: Allow fixed_rr with pipe joiner Ankit Nautiyal
2025-03-18 7:35 ` [PATCH 15/16] drm/i915/vrr: Always use VRR timing generator for PTL+ Ankit Nautiyal
2025-03-21 17:47 ` Ville Syrjälä [this message]
2025-03-18 7:35 ` [PATCH 16/16] drm/i915/vrr: Set trans_vrr_ctl in intel_vrr_set_transcoder_timings() Ankit Nautiyal
2025-03-18 7:57 ` ✗ CI.Patch_applied: failure for Use VRR timing generator for fixed refresh rate modes (rev9) Patchwork
2025-03-18 8:16 ` ✗ Fi.CI.SPARSE: warning for Use VRR timing generator for fixed refresh rate modes (rev14) Patchwork
2025-03-18 8:37 ` ✗ i915.CI.BAT: failure " Patchwork
2025-03-20 5:37 ` ✓ CI.Patch_applied: success for Use VRR timing generator for fixed refresh rate modes (rev10) Patchwork
2025-03-20 5:37 ` ✓ CI.checkpatch: " Patchwork
2025-03-20 5:38 ` ✓ CI.KUnit: " Patchwork
2025-03-20 5:55 ` ✓ CI.Build: " Patchwork
2025-03-20 5:57 ` ✓ CI.Hooks: " Patchwork
2025-03-20 5:58 ` ✗ CI.checksparse: warning " Patchwork
2025-03-20 6:18 ` ✓ Xe.CI.BAT: success " Patchwork
2025-03-20 7:17 ` ✓ Xe.CI.Full: " Patchwork
2025-03-21 6:05 ` ✗ Fi.CI.SPARSE: warning for Use VRR timing generator for fixed refresh rate modes (rev16) Patchwork
2025-03-21 6:26 ` ✓ i915.CI.BAT: success " Patchwork
2025-03-21 8:17 ` ✗ i915.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=Z92mIPHsmQaWuFW5@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.