Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Jouni Högander" <jouni.hogander@intel.com>
To: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Cc: "Jouni Högander" <jouni.hogander@intel.com>
Subject: [PATCH 0/8] Selective fetch calculation fixes
Date: Tue, 29 Sep 2026 12:44:26 +0300	[thread overview]
Message-ID: <20260929094434.77129-1-jouni.hogander@intel.com> (raw)

This set contains fixes for selective fetch area calculation.

Fixes in the set:

 - Clear plane selective fetch area on plane state duplicate and keep the
   area consistent on full update.
 - Add enabled pipe planes into the state before the plane checks to keep
   the UV and Y plane linking in place.
 - Set the selective fetch area for the linked Y plane also when selective
   fetch is being disabled.
 - Fix SFF_CTL and CFF_CTL register bit definitions.
 - Skip the plane selective fetch support check for invisible planes.
 - Don't write a zero sized area into the plane selective fetch area
   registers.
 - Remove misleading drm_info_once on zero sized selective fetch area.
 - Don't clip the cursor plane state destination rectangle when
   calculating the selective update area.

Jouni Högander (8):
  drm/i915/psr: Clear selective fetch area when duplicating plane state
  drm/i915/display: Add enabled pipe planes into state for selective
    fetch
  drm/i915/psr: Disable linked plane sel fetch as well
  drm/i915/psr: Fix SFF and CFF CTL register bit definitions
  drm/i915/psr: Skip sel fetch support check for invisible planes
  drm/i915/psr: Don't write 0 size area into plane sel fetch area
    registers
  drm/i915/psr: Remove drm_info_once on failed selective fetch area
  drm/i915/psr: Don't clip plane state destination rectangle

 drivers/gpu/drm/i915/display/intel_plane.c    |  11 ++
 drivers/gpu/drm/i915/display/intel_psr.c      | 106 ++++++++----------
 drivers/gpu/drm/i915/display/intel_psr_regs.h |   4 +-
 .../drm/i915/display/skl_universal_plane.c    |   3 +-
 4 files changed, 61 insertions(+), 63 deletions(-)

-- 
2.43.0


             reply	other threads:[~2026-09-29  9:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-29  9:44 Jouni Högander [this message]
2026-09-29  9:44 ` [PATCH 1/8] drm/i915/psr: Clear selective fetch area when duplicating plane state Jouni Högander
2026-09-29  9:44 ` [PATCH 2/8] drm/i915/display: Add enabled pipe planes into state for selective fetch Jouni Högander
2026-09-29  9:44 ` [PATCH 3/8] drm/i915/psr: Disable linked plane sel fetch as well Jouni Högander
2026-09-29  9:44 ` [PATCH 4/8] drm/i915/psr: Fix SFF and CFF CTL register bit definitions Jouni Högander
2026-09-29  9:44 ` [PATCH 5/8] drm/i915/psr: Skip sel fetch support check for invisible planes Jouni Högander
2026-09-29  9:44 ` [PATCH 6/8] drm/i915/psr: Don't write 0 size area into plane sel fetch area registers Jouni Högander
2026-09-29  9:44 ` [PATCH 7/8] drm/i915/psr: Remove drm_info_once on failed selective fetch area Jouni Högander
2026-09-29  9:44 ` [PATCH 8/8] drm/i915/psr: Don't clip plane state destination rectangle Jouni Högander
2026-09-29  9:53 ` ✓ CI.KUnit: success for Selective fetch calculation fixes Patchwork
2026-09-29 10:39 ` ✓ Xe.CI.BAT: " Patchwork
2026-09-29 12:11 ` ✗ Xe.CI.FULL: 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=20260929094434.77129-1-jouni.hogander@intel.com \
    --to=jouni.hogander@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    /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