All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Souza, Jose" <jose.souza@intel.com>
To: "intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>,
	"Hogander, Jouni" <jouni.hogander@intel.com>
Cc: "markpearson@lenovo.com" <markpearson@lenovo.com>
Subject: Re: [Intel-gfx] [PATCH v2 1/2] drm/i915/psr: Use full update In case of area calculation fails
Date: Mon, 9 May 2022 13:32:35 +0000	[thread overview]
Message-ID: <ee93f276c4116da6384fcb225148881ef91a30ce.camel@intel.com> (raw)
In-Reply-To: <20220509072404.1423018-2-jouni.hogander@intel.com>

On Mon, 2022-05-09 at 10:24 +0300, Jouni Högander wrote:
> Currently we have some corner cases where area calculation fails.  For
> these sel fetch area calculation ends up having update area as y1 = 0,
> y2 = 4. Instead of these values safer option is full update.
> 
> One of such for example is big fb with offset. We don't have usable
> offset in psr2_sel_fetch_update. Currently it's open what is the
> proper way to fix this corner case. Use full update for now.
> 
> v2: Commit message modified
> 
> Cc: José Roberto de Souza <jose.souza@intel.com>
> Cc: Mika Kahola <mika.kahola@intel.com>
> Tested-by: Mark Pearson <markpearson@lenovo.com>
> Signed-off-by: Jouni Högander <jouni.hogander@intel.com>
> ---
>  drivers/gpu/drm/i915/display/intel_psr.c | 3 +++
>  1 file changed, 3 insertions(+)
> 
> diff --git a/drivers/gpu/drm/i915/display/intel_psr.c b/drivers/gpu/drm/i915/display/intel_psr.c
> index 06db407e2749..8c099d24de86 100644
> --- a/drivers/gpu/drm/i915/display/intel_psr.c
> +++ b/drivers/gpu/drm/i915/display/intel_psr.c
> @@ -1770,6 +1770,9 @@ int intel_psr2_sel_fetch_update(struct intel_atomic_state *state,
>  		clip_area_update(&pipe_clip, &damaged_area);
>  	}
>  
> +	if (pipe_clip.y1 == -1)
> +		full_update = true;

Left the debug_once and the TODO out, for a regular reader this looks like a normal code path... what is not the case.

> +
>  	if (full_update)
>  		goto skip_sel_fetch_set_loop;
>  


  reply	other threads:[~2022-05-09 13:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-09  7:24 [Intel-gfx] [PATCH v2 0/2] Fixes for selective fetch area calculation Jouni Högander
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 [this message]
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=ee93f276c4116da6384fcb225148881ef91a30ce.camel@intel.com \
    --to=jose.souza@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jouni.hogander@intel.com \
    --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.