From: Ankit Nautiyal <ankit.k.nautiyal@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: intel-xe@lists.freedesktop.org, jani.nikula@linux.intel.com,
ville.syrjala@linux.intel.com,
mitulkumar.ajitkumar.golani@intel.com
Subject: [RESEND PATCH 3/8] drm/i915/vrr: Make helpers for cmrr and vrr timings
Date: Tue, 11 Mar 2025 15:07:46 +0530 [thread overview]
Message-ID: <20250311093751.1329043-4-ankit.k.nautiyal@intel.com> (raw)
In-Reply-To: <20250311093751.1329043-1-ankit.k.nautiyal@intel.com>
Separate out functions for computing cmrr and vrr timings.
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 | 45 +++++++++++++++---------
1 file changed, 28 insertions(+), 17 deletions(-)
diff --git a/drivers/gpu/drm/i915/display/intel_vrr.c b/drivers/gpu/drm/i915/display/intel_vrr.c
index a88b77114867..db0ea206e26e 100644
--- a/drivers/gpu/drm/i915/display/intel_vrr.c
+++ b/drivers/gpu/drm/i915/display/intel_vrr.c
@@ -222,6 +222,30 @@ cmrr_get_vtotal(struct intel_crtc_state *crtc_state, bool video_mode_required)
return vtotal;
}
+static
+void intel_vrr_compute_cmrr_timings(struct intel_crtc_state *crtc_state)
+{
+ crtc_state->vrr.enable = true;
+ crtc_state->cmrr.enable = true;
+ /*
+ * TODO: Compute precise target refresh rate to determine
+ * if video_mode_required should be true. Currently set to
+ * false due to uncertainty about the precise target
+ * refresh Rate.
+ */
+ crtc_state->vrr.vmax = cmrr_get_vtotal(crtc_state, false);
+ crtc_state->vrr.vmin = crtc_state->vrr.vmax;
+ crtc_state->vrr.flipline = crtc_state->vrr.vmin;
+ crtc_state->mode_flags |= I915_MODE_FLAG_VRR;
+}
+
+static
+void intel_vrr_compute_vrr_timings(struct intel_crtc_state *crtc_state)
+{
+ crtc_state->vrr.enable = true;
+ crtc_state->mode_flags |= I915_MODE_FLAG_VRR;
+}
+
static
int intel_vrr_compute_vmin(struct intel_connector *connector,
const struct drm_display_mode *adjusted_mode)
@@ -298,23 +322,10 @@ 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) {
- crtc_state->vrr.enable = true;
- crtc_state->mode_flags |= I915_MODE_FLAG_VRR;
- } else if (is_cmrr_frac_required(crtc_state) && is_edp) {
- crtc_state->vrr.enable = true;
- crtc_state->cmrr.enable = true;
- /*
- * TODO: Compute precise target refresh rate to determine
- * if video_mode_required should be true. Currently set to
- * false due to uncertainty about the precise target
- * refresh Rate.
- */
- crtc_state->vrr.vmax = cmrr_get_vtotal(crtc_state, false);
- crtc_state->vrr.vmin = crtc_state->vrr.vmax;
- crtc_state->vrr.flipline = crtc_state->vrr.vmin;
- crtc_state->mode_flags |= I915_MODE_FLAG_VRR;
- }
+ if (crtc_state->uapi.vrr_enabled)
+ intel_vrr_compute_vrr_timings(crtc_state);
+ else if (is_cmrr_frac_required(crtc_state) && is_edp)
+ intel_vrr_compute_cmrr_timings(crtc_state);
if (HAS_AS_SDP(display)) {
crtc_state->vrr.vsync_start =
--
2.45.2
next prev parent reply other threads:[~2025-03-11 9:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-11 9:37 [RESEND PATCH 0/8] VRR Refactor Ankit Nautiyal
2025-03-11 9:37 ` [RESEND PATCH 1/8] drm/i915/vrr: Remove unwanted comment Ankit Nautiyal
2025-03-11 9:37 ` [RESEND PATCH 2/8] drm/i915:vrr: Separate out functions to compute vmin and vmax Ankit Nautiyal
2025-03-11 9:37 ` Ankit Nautiyal [this message]
2025-03-11 9:37 ` [RESEND PATCH 4/8] drm/i915/vrr: Disable CMRR Ankit Nautiyal
2025-03-11 9:37 ` [RESEND PATCH 5/8] drm/i915/vrr: Track vrr.enable only for variable timing Ankit Nautiyal
2025-03-11 9:37 ` [RESEND PATCH 6/8] drm/i915/vrr: Use crtc_vtotal for vmin Ankit Nautiyal
2025-03-11 9:37 ` [RESEND PATCH 7/8] drm/i915/vrr: Prepare for fixed refresh rate timings Ankit Nautiyal
2025-03-11 9:37 ` [RESEND PATCH 8/8] drm/i915/display: Enable MSA Ignore Timing PAR only when in not fixed_rr mode Ankit Nautiyal
2025-03-11 9:57 ` ✓ CI.Patch_applied: success for VRR Refactor Patchwork
2025-03-11 9:58 ` ✓ CI.checkpatch: " Patchwork
2025-03-11 10:00 ` ✓ CI.KUnit: " Patchwork
2025-03-11 10:19 ` ✓ CI.Build: " Patchwork
2025-03-11 10:21 ` ✓ CI.Hooks: " Patchwork
2025-03-11 10:22 ` ✓ CI.checksparse: " Patchwork
2025-03-11 10:44 ` ✓ Xe.CI.BAT: " Patchwork
2025-03-12 3:44 ` ✗ Xe.CI.Full: failure " Patchwork
2025-03-13 13:31 ` [RESEND PATCH 0/8] " Nautiyal, Ankit K
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=20250311093751.1329043-4-ankit.k.nautiyal@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