Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Hogander, Jouni" <jouni.hogander@intel.com>
To: "intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>,
	"Souza, Jose" <jose.souza@intel.com>
Cc: "Nikula, Jani" <jani.nikula@intel.com>
Subject: Re: [Intel-gfx] [PATCH] drm/i915/display: Fix handling of enable_psr parameter
Date: Thu, 9 Jun 2022 05:34:39 +0000	[thread overview]
Message-ID: <6c509856e04efc8edf731eb1530434aac99e0243.camel@intel.com> (raw)
In-Reply-To: <20220608203344.513082-1-jose.souza@intel.com>

On Wed, 2022-06-08 at 13:33 -0700, José Roberto de Souza wrote:
> Commit 3cf050762534 ("drm/i915/bios: Split VBT data into per-panel
> vs.
> global parts") cause PSR to be disabled when enable_psr has the
> default value and there is at least one DP port that do not supports
> PSR.
> 
> That was happening because intel_psr_init() is called for every DP
> port and then enable_psr is globaly set to 0 based on the PSR support
> of the DP port.
> 
> Here dropping the enable_psr overwritten and using the VBT PSR value
> when enable_psr is set as default.

Reviewed-by: Jouni Högander <jouni.hogander@intel.com>

> 
> Fixes: 3cf050762534 ("drm/i915/bios: Split VBT data into per-panel
> vs. global parts")
> Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
> Cc: Jani Nikula <jani.nikula@intel.com>
> Cc: Jouni Högander <jouni.hogander@intel.com>
> Cc: Mika Kahola <mika.kahola@intel.com>
> Signed-off-by: José Roberto de Souza <jose.souza@intel.com>
> ---
>  drivers/gpu/drm/i915/display/intel_psr.c | 7 +++----
>  1 file changed, 3 insertions(+), 4 deletions(-)
> 
> diff --git a/drivers/gpu/drm/i915/display/intel_psr.c
> b/drivers/gpu/drm/i915/display/intel_psr.c
> index aedb3e0e69ecd..7d61c55184e51 100644
> --- a/drivers/gpu/drm/i915/display/intel_psr.c
> +++ b/drivers/gpu/drm/i915/display/intel_psr.c
> @@ -86,10 +86,13 @@
>  
>  static bool psr_global_enabled(struct intel_dp *intel_dp)
>  {
> +	struct intel_connector *connector = intel_dp-
> >attached_connector;
>  	struct drm_i915_private *i915 = dp_to_i915(intel_dp);
>  
>  	switch (intel_dp->psr.debug & I915_PSR_DEBUG_MODE_MASK) {
>  	case I915_PSR_DEBUG_DEFAULT:
> +		if (i915->params.enable_psr == -1)
> +			return connector->panel.vbt.psr.enable;
>  		return i915->params.enable_psr;
>  	case I915_PSR_DEBUG_DISABLE:
>  		return false;
> @@ -2394,10 +2397,6 @@ void intel_psr_init(struct intel_dp *intel_dp)
>  
>  	intel_dp->psr.source_support = true;
>  
> -	if (dev_priv->params.enable_psr == -1)
> -		if (!connector->panel.vbt.psr.enable)
> -			dev_priv->params.enable_psr = 0;
> -
>  	/* Set link_standby x link_off defaults */
>  	if (DISPLAY_VER(dev_priv) < 12)
>  		/* For new platforms up to TGL let's respect VBT back
> again */


  parent reply	other threads:[~2022-06-09  5:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-08 20:33 [Intel-gfx] [PATCH] drm/i915/display: Fix handling of enable_psr parameter José Roberto de Souza
2022-06-09  0:45 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2022-06-09  5:34 ` Hogander, Jouni [this message]
2022-06-09 17:01 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-06-09 19:26   ` 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=6c509856e04efc8edf731eb1530434aac99e0243.camel@intel.com \
    --to=jouni.hogander@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@intel.com \
    --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