All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: deepak.s@linux.intel.com
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915/chv: Implement WaDisableShadowRegForCpd
Date: Tue, 14 Apr 2015 13:59:52 +0300	[thread overview]
Message-ID: <20150414105952.GK11009@intel.com> (raw)
In-Reply-To: <1429007334-31245-1-git-send-email-deepak.s@linux.intel.com>

On Tue, Apr 14, 2015 at 03:58:54PM +0530, deepak.s@linux.intel.com wrote:
> From: Deepak S <deepak.s@linux.intel.com>
> 
> This WA disable usage of shadow register during CPD/RC6 transactions on
> CHV

I suppose is a workaround for the shadow vs. wake FIFO problem... Yeah
hsd seems to agree (after a bit of extra digging).

> 
> Signed-off-by: Deepak S <deepak.s@linux.intel.com>
> ---
>  drivers/gpu/drm/i915/i915_reg.h | 1 +
>  drivers/gpu/drm/i915/intel_pm.c | 4 ++++
>  2 files changed, 5 insertions(+)
> 
> diff --git a/drivers/gpu/drm/i915/i915_reg.h b/drivers/gpu/drm/i915/i915_reg.h
> index 9c97842..bcdb16b 100644
> --- a/drivers/gpu/drm/i915/i915_reg.h
> +++ b/drivers/gpu/drm/i915/i915_reg.h
> @@ -6206,6 +6206,7 @@ enum skl_disp_power_wells {
>  #define  GTFIFOCTL				0x120008
>  #define    GT_FIFO_FREE_ENTRIES_MASK		0x7f
>  #define    GT_FIFO_NUM_RESERVED_ENTRIES		20
> +#define GT_FIFO_CTL_BLOCK_POLICY	(3<<11)

GT_FIFO_CTL_BLOCK_ALL_POLICY_STALL	(1 << 12)
GT_FIFO_CTL_RC6_POLICY_STALL		(1 << 11)

perhaps?

>  
>  #define  HSW_IDICR				0x9008
>  #define    IDIHASHMSK(x)			(((x) & 0x3f) << 16)
> diff --git a/drivers/gpu/drm/i915/intel_pm.c b/drivers/gpu/drm/i915/intel_pm.c
> index 4dd8b41..b9d3c00 100644
> --- a/drivers/gpu/drm/i915/intel_pm.c
> +++ b/drivers/gpu/drm/i915/intel_pm.c
> @@ -6431,6 +6431,10 @@ static void cherryview_init_clock_gating(struct drm_device *dev)
>  	/* WaDisableSDEUnitClockGating:chv */
>  	I915_WRITE(GEN8_UCGCTL6, I915_READ(GEN8_UCGCTL6) |
>  		   GEN8_SDEUNIT_CLOCK_GATE_DISABLE);
> +
> +	/* WaDisableShadowRegForCpd */
> +	I915_WRITE(GTFIFOCTL, I915_READ(GTFIFOCTL) |
> +						  GT_FIFO_CTL_BLOCK_POLICY);

I think __intel_uncore_early_sanitize() might be a better place for
this.

>  }
>  
>  static void g4x_init_clock_gating(struct drm_device *dev)
> -- 
> 1.9.1

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

  reply	other threads:[~2015-04-14 10:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-14 10:28 [PATCH] drm/i915/chv: Implement WaDisableShadowRegForCpd deepak.s
2015-04-14 10:59 ` Ville Syrjälä [this message]
2015-04-15  8:02   ` Deepak S
2015-04-15  8:46     ` [PATCH v2] " deepak.s
2015-04-15 11:18       ` Ville Syrjälä
2015-04-15 13:39         ` Deepak S
2015-04-15 14:11           ` [PATCH v3] " deepak.s
2015-04-15 18:39             ` Ville Syrjälä
2015-04-16  3:19               ` Deepak S
2015-04-16  3:21                 ` [PATCH v4] " deepak.s
2015-04-16 21:05                   ` shuang.he
2015-04-28 14:41                   ` Jani Nikula
2015-04-16  2:36             ` [PATCH v3] " shuang.he
2015-04-15 18:19       ` [PATCH v2] " shuang.he

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=20150414105952.GK11009@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=deepak.s@linux.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.