drm/i915: Indicate which pipe failed the fastset check overall
authorVille Syrjälä <ville.syrjala@linux.intel.com>
Thu, 15 Feb 2024 16:40:44 +0000 (18:40 +0200)
committerVille Syrjälä <ville.syrjala@linux.intel.com>
Fri, 15 Mar 2024 12:19:21 +0000 (14:19 +0200)
intel_crtc_check_fastset() is done per-pipe, so it would be nice
to know which pipe it was that failed its checkup.

Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20240215164055.30585-2-ville.syrjala@linux.intel.com
Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
drivers/gpu/drm/i915/display/intel_display.c

index b88f214e111ae9177029010fc43047f046a4fcc1..8868f7496f48dba2cf88e5495e1218461ab98d37 100644 (file)
@@ -5576,14 +5576,16 @@ static int intel_modeset_checks(struct intel_atomic_state *state)
 static void intel_crtc_check_fastset(const struct intel_crtc_state *old_crtc_state,
                                     struct intel_crtc_state *new_crtc_state)
 {
-       struct drm_i915_private *i915 = to_i915(old_crtc_state->uapi.crtc->dev);
+       struct intel_crtc *crtc = to_intel_crtc(new_crtc_state->uapi.crtc);
+       struct drm_i915_private *i915 = to_i915(crtc->base.dev);
 
        /* only allow LRR when the timings stay within the VRR range */
        if (old_crtc_state->vrr.in_range != new_crtc_state->vrr.in_range)
                new_crtc_state->update_lrr = false;
 
        if (!intel_pipe_config_compare(old_crtc_state, new_crtc_state, true))
-               drm_dbg_kms(&i915->drm, "fastset requirement not met, forcing full modeset\n");
+               drm_dbg_kms(&i915->drm, "[CRTC:%d:%s] fastset requirement not met, forcing full modeset\n",
+                           crtc->base.base.id, crtc->base.name);
        else
                new_crtc_state->uapi.mode_changed = false;