public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Srivatsa, Anusha" <anusha.srivatsa@intel.com>
To: "Souza, Jose" <jose.souza@intel.com>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PATCH 4/4] drm/i915/display/psr2: Force a PSR exit in the frontbuffer modification flushes
Date: Mon, 26 Jul 2021 21:23:54 +0000	[thread overview]
Message-ID: <1dbf14fb850b4cf79f4d78f07b745676@intel.com> (raw)
In-Reply-To: <20210717011227.204494-4-jose.souza@intel.com>



> -----Original Message-----
> From: Intel-gfx <intel-gfx-bounces@lists.freedesktop.org> On Behalf Of José
> Roberto de Souza
> Sent: Friday, July 16, 2021 6:12 PM
> To: intel-gfx@lists.freedesktop.org
> Subject: [Intel-gfx] [PATCH 4/4] drm/i915/display/psr2: Force a PSR exit in
> the frontbuffer modification flushes
> 
> The CURSURFLIVE() write do not works with PSR2 selective fetch, the only
> way to update screen is to program PSR2 plane and transcoder registers
> during the vblank.
> 
> We could use the frontbuffer dirty areas set by userspace with
> drmModeDirtyFB() but we would still need to wait for the vblank to properly
> update the PSR2 registers.
> What I think is not worthy the development time considering that there is so
> few userspace applications that makes use of this old method.
> 
> So here forcing a PSR exit in this case, this will guaratee that panel will be
s/ guaratee/ guarantee

> properly updated.
> 
> Cc: Gwan-gyeong Mun <gwan-gyeong.mun@intel.com>
> Signed-off-by: José Roberto de Souza <jose.souza@intel.com>
Reviewed-by: Anusha Srivatsa <anusha.srivatsa@intel.com>

> ---
>  drivers/gpu/drm/i915/display/intel_psr.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/gpu/drm/i915/display/intel_psr.c
> b/drivers/gpu/drm/i915/display/intel_psr.c
> index 1c41042841fb1..7316967aba94b 100644
> --- a/drivers/gpu/drm/i915/display/intel_psr.c
> +++ b/drivers/gpu/drm/i915/display/intel_psr.c
> @@ -1448,7 +1448,7 @@ static void psr_force_hw_tracking_exit(struct
> intel_dp *intel_dp)  {
>  	struct drm_i915_private *dev_priv = dp_to_i915(intel_dp);
> 
> -	if (DISPLAY_VER(dev_priv) >= 9)
> +	if (DISPLAY_VER(dev_priv) >= 9 &&
> +!intel_dp->psr.psr2_sel_fetch_enabled)
>  		/*
>  		 * Display WA #0884: skl+
>  		 * This documented WA for bxt can be safely applied
> --
> 2.32.0
> 
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2021-07-26 21:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-17  1:12 [Intel-gfx] [PATCH 1/4] drm/i915/display: Disable FBC when PSR2 is enabled for xelpd platforms José Roberto de Souza
2021-07-17  1:12 ` [Intel-gfx] [PATCH 2/4] drm/i915/display/psr2: Mark as updated all planes that intersect with pipe_clip José Roberto de Souza
2021-07-26 21:15   ` Srivatsa, Anusha
2021-07-17  1:12 ` [Intel-gfx] [PATCH 3/4] drm/i915/display/psr2: Fix cursor updates using legacy apis José Roberto de Souza
2021-07-26 21:19   ` Srivatsa, Anusha
2021-07-17  1:12 ` [Intel-gfx] [PATCH 4/4] drm/i915/display/psr2: Force a PSR exit in the frontbuffer modification flushes José Roberto de Souza
2021-07-26 21:23   ` Srivatsa, Anusha [this message]
2021-07-17  2:03 ` [Intel-gfx] ✗ Fi.CI.DOCS: warning for series starting with [1/4] drm/i915/display: Disable FBC when PSR2 is enabled for xelpd platforms Patchwork
2021-07-17  2:28 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-07-17 12:48 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2021-07-26 23:11   ` Souza, Jose
2021-07-21 18:04 ` [Intel-gfx] [PATCH 1/4] " Srivatsa, Anusha

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=1dbf14fb850b4cf79f4d78f07b745676@intel.com \
    --to=anusha.srivatsa@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jose.souza@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