public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: "José Roberto de Souza" <jose.souza@intel.com>
Cc: intel-gfx@lists.freedesktop.org,
	Dhinakaran Pandiyan <dhinakaran.pandiyan@intel.com>
Subject: Re: [PATCH] drm/i915/psr: Force manual PSR exit in older gens
Date: Mon, 17 Jun 2019 13:14:31 -0700	[thread overview]
Message-ID: <20190617201431.GG30528@intel.com> (raw)
In-Reply-To: <20190617195154.30292-1-jose.souza@intel.com>

On Mon, Jun 17, 2019 at 12:51:54PM -0700, José Roberto de Souza wrote:
> To do frontbuffer tracking we are depending on Display WA #0884 to
> exit PSR when there is a frontbuffer modification but according to
> user reports a write to CURSURFLIVE do not cause PSR to exit in older
> gens so lets force a PSR exit.
> 
> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=110799

:(

Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>

and if bugs persist or this brings back older bugs it is time
to consider removing psr support at all for gen < 9  :-/

> Cc: Dhinakaran Pandiyan <dhinakaran.pandiyan@intel.com>
> Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
> Signed-off-by: José Roberto de Souza <jose.souza@intel.com>
> ---
>  drivers/gpu/drm/i915/display/intel_psr.c | 36 +++++++++++++++++-------
>  1 file changed, 26 insertions(+), 10 deletions(-)
> 
> diff --git a/drivers/gpu/drm/i915/display/intel_psr.c b/drivers/gpu/drm/i915/display/intel_psr.c
> index 69709df4a648..69d908e6a050 100644
> --- a/drivers/gpu/drm/i915/display/intel_psr.c
> +++ b/drivers/gpu/drm/i915/display/intel_psr.c
> @@ -863,16 +863,23 @@ void intel_psr_disable(struct intel_dp *intel_dp,
>  
>  static void psr_force_hw_tracking_exit(struct drm_i915_private *dev_priv)
>  {
> -	/*
> -	 * Display WA #0884: all
> -	 * This documented WA for bxt can be safely applied
> -	 * broadly so we can force HW tracking to exit PSR
> -	 * instead of disabling and re-enabling.
> -	 * Workaround tells us to write 0 to CUR_SURFLIVE_A,
> -	 * but it makes more sense write to the current active
> -	 * pipe.
> -	 */
> -	I915_WRITE(CURSURFLIVE(dev_priv->psr.pipe), 0);
> +	if (INTEL_GEN(dev_priv) >= 9)
> +		/*
> +		 * Display WA #0884: skl+
> +		 * This documented WA for bxt can be safely applied
> +		 * broadly so we can force HW tracking to exit PSR
> +		 * instead of disabling and re-enabling.
> +		 * Workaround tells us to write 0 to CUR_SURFLIVE_A,
> +		 * but it makes more sense write to the current active
> +		 * pipe.
> +		 */
> +		I915_WRITE(CURSURFLIVE(dev_priv->psr.pipe), 0);
> +	else
> +		/*
> +		 * A write to CURSURFLIVE do not cause HW tracking to exit PSR
> +		 * on older gens so doing the manual exit instead.
> +		 */
> +		intel_psr_exit(dev_priv);
>  }
>  
>  /**
> @@ -903,6 +910,15 @@ void intel_psr_update(struct intel_dp *intel_dp,
>  		/* Force a PSR exit when enabling CRC to avoid CRC timeouts */
>  		if (crtc_state->crc_enabled && psr->enabled)
>  			psr_force_hw_tracking_exit(dev_priv);
> +		else if (INTEL_GEN(dev_priv) < 9 && psr->enabled) {
> +			/*
> +			 * Activate PSR again after a force exit when enabling
> +			 * CRC in older gens
> +			 */
> +			if (!dev_priv->psr.active &&
> +			    !dev_priv->psr.busy_frontbuffer_bits)
> +				schedule_work(&dev_priv->psr.work);
> +		}
>  
>  		goto unlock;
>  	}
> -- 
> 2.22.0
> 
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2019-06-17 20:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-17 19:51 [PATCH] drm/i915/psr: Force manual PSR exit in older gens José Roberto de Souza
2019-06-17 20:14 ` Rodrigo Vivi [this message]
2019-06-17 20:28 ` ✓ Fi.CI.BAT: success for " Patchwork
2019-06-18 12:00 ` ✗ Fi.CI.IGT: failure " Patchwork
2019-06-18 19:36   ` Souza, Jose

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=20190617201431.GG30528@intel.com \
    --to=rodrigo.vivi@intel.com \
    --cc=dhinakaran.pandiyan@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