intel-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Damien Lespiau <damien.lespiau@intel.com>
To: Gabriel Feceoru <gabriel.feceoru@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v2] drm/i915: Handle PipeC fused off on GEN7+
Date: Wed, 13 Jan 2016 14:50:15 +0000	[thread overview]
Message-ID: <20160113145015.GA14604@strange.ger.corp.intel.com> (raw)
In-Reply-To: <1452696403-18625-1-git-send-email-gabriel.feceoru@intel.com>

On Wed, Jan 13, 2016 at 04:46:43PM +0200, Gabriel Feceoru wrote:
> Starting with Gen7 (IVB) Display PipeC can be fused off on some production
> parts. When disabled, display hardware will prevent the pipe C register bit
> from being set to 1.
> 
> Fixed by adjusting pipe_count to reflect this.

The title is misleading, it's really just IVB/HSW/BDW not gen7+

You want to add the changelog of the patch in the commit message as
well, eg.

v2: Rename HSW_PIPE_C_DISABLE to IVB_PIPE_C_DISABLE as it already exists
    on ivybridge (Ville)

also, we can get rid of the MMIO access (see below)

-- 
Damien

> Signed-off-by: Gabriel Feceoru <gabriel.feceoru@intel.com>
> ---
>  drivers/gpu/drm/i915/i915_dma.c | 3 +++
>  drivers/gpu/drm/i915/i915_reg.h | 1 +
>  2 files changed, 4 insertions(+)
> 
> diff --git a/drivers/gpu/drm/i915/i915_dma.c b/drivers/gpu/drm/i915/i915_dma.c
> index 44a896c..c3b93e7 100644
> --- a/drivers/gpu/drm/i915/i915_dma.c
> +++ b/drivers/gpu/drm/i915/i915_dma.c
> @@ -813,6 +813,9 @@ static void intel_device_info_runtime_init(struct drm_device *dev)
>  		     !(sfuse_strap & SFUSE_STRAP_FUSE_LOCK))) {
>  			DRM_INFO("Display fused off, disabling\n");
>  			info->num_pipes = 0;
> +		} else if (I915_READ(FUSE_STRAP) & IVB_PIPE_C_DISABLE) {
> +			DRM_INFO("PipeC fused off\n");
> +			info->num_pipes -= 1;


FUSE_STRAP is alreay read above, it's in the fuse_trap variable.

HTH,

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

  reply	other threads:[~2016-01-13 14:50 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-21 11:57 [PATCH] drm/i915: Handle PipeC fused off on HSW Gabriel Feceoru
2015-12-21 13:13 ` ✗ warning: Fi.CI.BAT Patchwork
2015-12-21 13:14 ` Patchwork
2016-01-11 17:56 ` [PATCH] drm/i915: Handle PipeC fused off on HSW Ville Syrjälä
2016-01-12 15:00   ` Gabriel Feceoru
2016-01-12 15:08     ` Ville Syrjälä
2016-01-13 14:46 ` [PATCH v2] drm/i915: Handle PipeC fused off on GEN7+ Gabriel Feceoru
2016-01-13 14:50   ` Damien Lespiau [this message]
2016-01-13 15:41 ` ✓ success: Fi.CI.BAT Patchwork
2016-01-13 16:02 ` [PATCH v3] drm/i915: Handle PipeC fused off on IVB/HSW/BDW Gabriel Feceoru
2016-01-19 16:09   ` Patrik Jakobsson
2016-01-13 16:49 ` ✗ warning: Fi.CI.BAT Patchwork
2016-01-22 11:28 ` [PATCH v4] drm/i915: Handle PipeC fused off on IVB/HSW/BDW Gabriel Feceoru
2016-02-01 14:20   ` Patrik Jakobsson
2016-02-10  7:29     ` Daniel Vetter
2016-01-22 11:46 ` ✗ Fi.CI.BAT: warning for drm/i915: Handle PipeC fused off on HSW (rev4) Patchwork

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=20160113145015.GA14604@strange.ger.corp.intel.com \
    --to=damien.lespiau@intel.com \
    --cc=gabriel.feceoru@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).