public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: "José Roberto de Souza" <jose.souza@intel.com>
Cc: intel-gfx@lists.freedesktop.org,
	Lucas De Marchi <lucas.demarchi@intel.com>
Subject: Re: [PATCH 1/4] drm/i915/display: Handle fused off display correctly
Date: Fri, 11 Oct 2019 15:25:03 +0300	[thread overview]
Message-ID: <20191011122503.GO1208@intel.com> (raw)
In-Reply-To: <20191010193241.101401-1-jose.souza@intel.com>

On Thu, Oct 10, 2019 at 12:32:38PM -0700, José Roberto de Souza wrote:
> If all pipes are fused off it means that display is disabled, similar
> like we handle for GEN 7 and 8 right above.
> 
> On GEN 9 the bit 31 is "Internal Graphics Disable" and on newer GENs
> it has another function, probably on GEN 9 when bit 31 is set all
> the 3 pipes disable bit are set, so we can unify the handling.

I'm not sure this is really correct. The description says the pipe will
just output a solid color, so the display hardware may be there to some
degree and if we don't want to waste power we may have to power manage
some of it still.

Not sure how high up we've plugged in the 'pipe_mask==0 -> display not
there' logic. If it's too high up we may leave some power on the floor.

But all that is just speculation on my part. Would probably be good
to get some clarification to the spec about this stuff.

> 
> Cc: Lucas De Marchi <lucas.demarchi@intel.com>
> Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
> Signed-off-by: José Roberto de Souza <jose.souza@intel.com>
> ---
>  drivers/gpu/drm/i915/intel_device_info.c | 11 +++++------
>  1 file changed, 5 insertions(+), 6 deletions(-)
> 
> diff --git a/drivers/gpu/drm/i915/intel_device_info.c b/drivers/gpu/drm/i915/intel_device_info.c
> index 85e480bdc673..c01fccfe3cca 100644
> --- a/drivers/gpu/drm/i915/intel_device_info.c
> +++ b/drivers/gpu/drm/i915/intel_device_info.c
> @@ -972,15 +972,14 @@ void intel_device_info_runtime_init(struct drm_i915_private *dev_priv)
>  			enabled_mask &= ~BIT(PIPE_D);
>  
>  		/*
> -		 * At least one pipe should be enabled and if there are
> -		 * disabled pipes, they should be the last ones, with no holes
> -		 * in the mask.
> +		 * If there are disabled pipes, they should be the last ones,
> +		 * with no holes in the mask.
>  		 */
> -		if (enabled_mask == 0 || !is_power_of_2(enabled_mask + 1))
> +		if (enabled_mask && !is_power_of_2(enabled_mask + 1))
>  			DRM_ERROR("invalid pipe fuse configuration: enabled_mask=0x%x\n",
>  				  enabled_mask);
> -		else
> -			info->pipe_mask = enabled_mask;
> +
> +		info->pipe_mask = enabled_mask;
>  	}
>  
>  	/* Initialize slice/subslice/EU info */
> -- 
> 2.23.0

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

  parent reply	other threads:[~2019-10-11 12:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-10 19:32 [PATCH 1/4] drm/i915/display: Handle fused off display correctly José Roberto de Souza
2019-10-10 19:32 ` [PATCH 2/4] drm/i915/display: Handle fused off HDCP José Roberto de Souza
2019-10-11 12:27   ` Ville Syrjälä
2019-10-10 19:32 ` [PATCH 3/4] drm/i915/display: DFSM CDCLK LIMIT is only available in BXT José Roberto de Souza
2019-10-10 20:45   ` Souza, Jose
2019-10-11 12:31     ` Ville Syrjälä
2019-10-10 19:32 ` [PATCH 4/4] drm/i915/display: Check if FBC and DMC are fused off José Roberto de Souza
2019-10-11 12:29   ` Ville Syrjälä
2019-10-10 20:18 ` ✗ Fi.CI.BAT: failure for series starting with [1/4] drm/i915/display: Handle fused off display correctly Patchwork
2019-10-11  7:16   ` Martin Peres
2019-10-11 19:30     ` Souza, Jose
2019-10-11 12:25 ` Ville Syrjälä [this message]
2019-10-11 15:00   ` [PATCH 1/4] " 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=20191011122503.GO1208@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jose.souza@intel.com \
    --cc=lucas.demarchi@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