Currently we have some corner cases where area calculation fails. For
these sel fetch are calculation ends up having update area as y1 = 0,
y2 = 4. Instead of these values safer option is full update.
Cc: José Roberto de Souza <jose.so...@intel.com>
Cc: Mika Kahola <mika.kah...@intel.com>
Tested-by: Mark Pearson <markpear...@lenovo.com>
Signed-off-by: Jouni Högander <jouni.hogan...@intel.com>
---
drivers/gpu/drm/i915/display/intel_psr.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/gpu/drm/i915/display/intel_psr.c
b/drivers/gpu/drm/i915/display/intel_psr.c
index 06db407e2749..8c099d24de86 100644
--- a/drivers/gpu/drm/i915/display/intel_psr.c
+++ b/drivers/gpu/drm/i915/display/intel_psr.c
@@ -1770,6 +1770,9 @@ int intel_psr2_sel_fetch_update(struct intel_atomic_state
*state,
clip_area_update(&pipe_clip, &damaged_area);
}
+ if (pipe_clip.y1 == -1)
+ full_update = true;
+
if (full_update)
goto skip_sel_fetch_set_loop;
--
2.25.1
