Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: "Jouni Högander" <jouni.hogander@intel.com>
Cc: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Subject: Re: [PATCH v4 0/3] Selective Fetch and async flip
Date: Tue, 9 Dec 2025 20:26:25 +0200	[thread overview]
Message-ID: <aThp0YZOjgWyA9DW@intel.com> (raw)
In-Reply-To: <20251204070718.1090778-1-jouni.hogander@intel.com>

On Thu, Dec 04, 2025 at 09:07:15AM +0200, Jouni Högander wrote:
> This patch set contains fixes for Selective Fetch async flip
> sequences. On async flip selective fetch is choosing full frame
> update. Also subsequent flip/update is still using full frame update
> to ensure plane with pending async flip is not taken in to selective
> fetch/update.
> 
> v4:
>   - rework if-else if to if-if
>   - added comment updated
>   - check crtc_state->async_flip_planes in
>     psr2_sel_fetch_pipe_state_supported
> v3:
>   - rebase
>   - fix old_crtc_state->pipe_srcsz_early_tpt
>   - fix using intel_atomic_get_new_crtc_state
> v2:
>   - check also crtc_state->async_flip_planes in
>     psr2_sel_fetch_plane_state_supported
> 
> Jouni Högander (3):
>   drm/i915/psr: Set plane id bit in crtc_state->async_flip_planes for
>     PSR
>   drm/i915/psr: Perform full frame update on async flip
>   drm/i915/psr: Allow async flip when Selective Fetch enabled

Series is
Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>

When testing this I saw that we get stuck into full frame mode
all the time. But that seems to be a pre-existing issues caused
by the broken selective fetch area calculation code. I suppose
now that I have a laptop with a PSR2 panel I might have to dig out
that branch of mine where I attempted to rewrite the whoile thing
and figure out what was wrong with it...

> 
>  drivers/gpu/drm/i915/display/intel_display.c |  8 --------
>  drivers/gpu/drm/i915/display/intel_plane.c   | 10 ++++++----
>  drivers/gpu/drm/i915/display/intel_psr.c     |  3 ++-
>  3 files changed, 8 insertions(+), 13 deletions(-)
> 
> -- 
> 2.43.0

-- 
Ville Syrjälä
Intel

  parent reply	other threads:[~2025-12-09 18:26 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-04  7:07 [PATCH v4 0/3] Selective Fetch and async flip Jouni Högander
2025-12-04  7:07 ` [PATCH v4 1/3] drm/i915/psr: Set plane id bit in crtc_state->async_flip_planes for PSR Jouni Högander
2025-12-04  7:07 ` [PATCH v4 2/3] drm/i915/psr: Perform full frame update on async flip Jouni Högander
2025-12-04  7:07 ` [PATCH v4 3/3] drm/i915/psr: Allow async flip when Selective Fetch enabled Jouni Högander
2025-12-04  7:58 ` ✓ CI.KUnit: success for Selective Fetch and async flip (rev4) Patchwork
2025-12-04  8:13 ` ✗ CI.checksparse: warning " Patchwork
2025-12-04  9:00 ` ✓ Xe.CI.BAT: success " Patchwork
2025-12-04 10:32 ` ✓ Xe.CI.Full: " Patchwork
2025-12-09 18:26 ` Ville Syrjälä [this message]
2025-12-10  6:23   ` [PATCH v4 0/3] Selective Fetch and async flip Hogander, Jouni
2025-12-10  6:31     ` Hogander, Jouni
2025-12-10  6:46       ` Ville Syrjälä
2025-12-10  6:42     ` Ville Syrjälä
2025-12-10  6:57       ` Hogander, Jouni
2025-12-10  7:06         ` Ville Syrjälä
2025-12-16 10:22       ` Hogander, Jouni
2025-12-10 13:41   ` Hogander, Jouni

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=aThp0YZOjgWyA9DW@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jouni.hogander@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox