mbox series

[v5,0/2] Fixes for selective fetch area calculation

Message ID 20220513142811.779331-1-jouni.hogander@intel.com (mailing list archive)
Headers show
Series Fixes for selective fetch area calculation | expand

Message

Hogander, Jouni May 13, 2022, 2:28 p.m. UTC
Currently selective fetch area calculation ends up as bogus area in
at least following cases:

1. Updated plane is partially or fully outside pipe area
2. Big fb with only part of memory area used for plane

These end up as y1 = 0, y2 = 4 or y2 being outside pipe area. This
patch set addresses these by ensuring update area is within pipe area
or by falling back to full update.

v5:
 - pipeA -> "pipe %c", pipe_name(crtc-pipe)
v4:
 - draw_area -> pipe_src
 - drm_dbg_once dropped and drm_info_once used instead
v3:
 - Add drm_dbg_once* and use it when sel fetch area calculation fails
 - Move drm_rect_intersect to clip_area_update
v2:
 - Update commit message of first patch
 - Set damaged_area x1 and x2 during initialization

Cc: José Roberto de Souza <jose.souza@intel.com>
Cc: Mika Kahola <mika.kahola@intel.com>
Cc: Mark Pearson <markpearson@lenovo.com>

Jouni Högander (2):
  drm/i915/psr: Use full update In case of area calculation fails
  drm/i915: Ensure damage clip area is within pipe area

 drivers/gpu/drm/i915/display/intel_psr.c | 37 +++++++++++++++++++-----
 1 file changed, 30 insertions(+), 7 deletions(-)