From: "Jouni Högander" <jouni.hogander@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: Mark Pearson <markpearson@lenovo.com>
Subject: [Intel-gfx] [PATCH v2 0/2] Fixes for selective fetch area calculation
Date: Mon, 9 May 2022 10:24:02 +0300 [thread overview]
Message-ID: <20220509072404.1423018-1-jouni.hogander@intel.com> (raw)
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
and falling back to full 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 | 20 +++++++++++++++-----
1 file changed, 15 insertions(+), 5 deletions(-)
--
2.25.1
next reply other threads:[~2022-05-09 7:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-09 7:24 Jouni Högander [this message]
2022-05-09 7:24 ` [Intel-gfx] [PATCH v2 1/2] drm/i915/psr: Use full update In case of area calculation fails Jouni Högander
2022-05-09 13:32 ` Souza, Jose
2022-05-09 7:24 ` [Intel-gfx] [PATCH v2 2/2] drm/i915: Ensure damage clip area is within pipe area Jouni Högander
2022-05-09 13:40 ` Souza, Jose
2022-05-09 16:27 ` [Intel-gfx] ✓ Fi.CI.BAT: success for Fixes for selective fetch area calculation (rev2) Patchwork
2022-05-09 22:32 ` [Intel-gfx] ✗ Fi.CI.IGT: 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=20220509072404.1423018-1-jouni.hogander@intel.com \
--to=jouni.hogander@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=markpearson@lenovo.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.