All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Aaron Ma" <aaron.ma@canonical.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915/psr: Skip PSR exit for legacy cursor updates on LNL
Date: Tue, 23 Jun 2026 08:52:38 +0000	[thread overview]
Message-ID: <20260623085239.5A0541F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260623084137.3421894-1-aaron.ma@canonical.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] Unconditionally skipping PSR flush/exit for legacy cursor updates reintroduces cursor trailing artifacts on pre-LNL platforms with PSR2 selective fetch.
--

commit 2fb445d4d3ce6ed075913638e7c06b17876c62bb
Author: Aaron Ma <aaron.ma@canonical.com>
drm/i915/psr: Skip PSR exit for legacy cursor updates on LNL

This commit modifies the PSR flush handler to unconditionally skip the
PSR exit path for legacy cursor updates. It removes the selective fetch
check to resolve visual artifacts during exit/re-enable transitions on LNL.

> diff --git a/drivers/gpu/drm/i915/display/intel_psr.c b/drivers/gpu/drm/i915/display/intel_psr.c
> index e138982dc91f6..32bee6c03b754 100644
> --- a/drivers/gpu/drm/i915/display/intel_psr.c
> +++ b/drivers/gpu/drm/i915/display/intel_psr.c
> @@ -3771,8 +3771,7 @@ void intel_psr_flush(struct intel_display *display,
>  			goto unlock;
>  
>  		if (origin == ORIGIN_FLIP ||
> -		    (origin == ORIGIN_CURSOR_UPDATE &&
> -		     !intel_dp->psr.psr2_sel_fetch_enabled)) {
> +		    origin == ORIGIN_CURSOR_UPDATE) {

[Severity: Medium]
Will unconditionally removing the !intel_dp->psr.psr2_sel_fetch_enabled
guard reintroduce cursor trailing artifacts on pre-LNL platforms?

The commit message mentions skipping PSR exit for LNL, but the change applies
to all platforms.

Any legacy cursor update on pre-LNL platforms with PSR2 selective fetch
enabled will now trigger intel_legacy_cursor_update(), which issues
ORIGIN_CURSOR_UPDATE and bypasses the full-frame fallback update in
_psr_flush_handle().

Could this revert the behavior introduced in commit ef39826c12b4 for older
platforms?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260623084137.3421894-1-aaron.ma@canonical.com?part=1

  reply	other threads:[~2026-06-23  8:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-23  8:41 [PATCH] drm/i915/psr: Skip PSR exit for legacy cursor updates on LNL Aaron Ma
2026-06-23  8:52 ` sashiko-bot [this message]
2026-06-23  9:19 ` ✗ Fi.CI.BUILD: failure for " 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=20260623085239.5A0541F000E9@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=aaron.ma@canonical.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /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.