All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Gupta, Anshuman" <anshuman.gupta@intel.com>
To: "Mun, Gwan-gyeong" <gwan-gyeong.mun@intel.com>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PATCH v3] drm/i915/display: Do not allow DC3CO if PSR SF is enabled
Date: Tue, 23 Feb 2021 10:08:37 +0000	[thread overview]
Message-ID: <fdd0eaaad2f848038286b633d2540d3a@intel.com> (raw)
In-Reply-To: <20210222213006.1609085-1-gwan-gyeong.mun@intel.com>



> -----Original Message-----
> From: Mun, Gwan-gyeong <gwan-gyeong.mun@intel.com>
> Sent: Tuesday, February 23, 2021 3:00 AM
> To: intel-gfx@lists.freedesktop.org
> Cc: Gupta, Anshuman <anshuman.gupta@intel.com>; Souza, Jose
> <jose.souza@intel.com>
> Subject: [PATCH v3] drm/i915/display: Do not allow DC3CO if PSR SF is enabled
> 
> Even though GEN12+ HW supports PSR + DC3CO, DMC's HW DC3CO exit
> mechanism has an issue with using of Selective Fecth and PSR2 manual tracking.
> And as some GEN12+ platforms (RKL, ADL-S) don't support PSR2 HW tracking,
> Selective Fetch will be enabled by default on that platforms.
> Therefore if the system enables PSR Selective Fetch / PSR manual tracking, it
> does not allow DC3CO dc state, in that case.
> 
> When this DC3CO exit issue is addressed while PSR Selective Fetch is enabled,
> this restriction should be removed.
> 
> v2: Address Jose's review comment.
>   - Fix typo
>   - Move check routine of DC3CO ability to
>     tgl_dc3co_exitline_compute_config()
> v3: Change the check routine of enablement of psr2 sel fetch. (Jose)
> 
> Cc: José Roberto de Souza <jose.souza@intel.com>
> Cc: Anshuman Gupta <anshuman.gupta@intel.com>
> Signed-off-by: Gwan-gyeong Mun <gwan-gyeong.mun@intel.com>
> ---
>  drivers/gpu/drm/i915/display/intel_psr.c | 7 +++++++
>  1 file changed, 7 insertions(+)
> 
> diff --git a/drivers/gpu/drm/i915/display/intel_psr.c
> b/drivers/gpu/drm/i915/display/intel_psr.c
> index 7c6e561f86c1..cd434285e3b7 100644
> --- a/drivers/gpu/drm/i915/display/intel_psr.c
> +++ b/drivers/gpu/drm/i915/display/intel_psr.c
> @@ -654,6 +654,13 @@ tgl_dc3co_exitline_compute_config(struct intel_dp
> *intel_dp,
>  	struct drm_i915_private *dev_priv = dp_to_i915(intel_dp);
>  	u32 exit_scanlines;
> 
> +	/*
> +	 * DMC's DC3CO exit mechanism has an issue with Selective Fecth
> +	 * TODO: when the issue is addressed, this restriction should be
> removed.
> +	 */
Earlier when PSR2 H/W tracking was enabled, DC3CO exit and frame updates works on it's own
Supported by DE engine and DMC firmware, but with selective fetch enable  as it disables the PSR2 H/W
Tracking. It requires to get sequence of DC3CO exit while PSR2 H/W tracking disabled.
Br,
Anshuman Gupta.  
> +	if (crtc_state->enable_psr2_sel_fetch)
> +		return;
> +
>  	if (!(dev_priv->csr.allowed_dc_mask & DC_STATE_EN_DC3CO))
>  		return;
> 
> --
> 2.30.0

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2021-02-23 10:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-22 21:30 [Intel-gfx] [PATCH v3] drm/i915/display: Do not allow DC3CO if PSR SF is enabled Gwan-gyeong Mun
2021-02-22 21:29 ` Souza, Jose
2021-02-22 22:16 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/display: Do not allow DC3CO if PSR SF is enabled (rev3) Patchwork
2021-02-22 23:45 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2021-02-23  1:44 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/display: Do not allow DC3CO if PSR SF is enabled (rev4) Patchwork
2021-02-23  2:57 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2021-02-23 16:01   ` Souza, Jose
2021-02-23 10:08 ` Gupta, Anshuman [this message]
2021-02-23 16:23   ` [Intel-gfx] [PATCH v3] drm/i915/display: Do not allow DC3CO if PSR SF is enabled Mun, Gwan-gyeong

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=fdd0eaaad2f848038286b633d2540d3a@intel.com \
    --to=anshuman.gupta@intel.com \
    --cc=gwan-gyeong.mun@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    /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.