From: Kenneth Graunke <kenneth@whitecape.org>
To: Eugeni Dodonov <eugeni.dodonov@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 2/3] drm/i915: gen7: add two more IVB workarounds
Date: Mon, 06 Feb 2012 14:22:35 -0800 [thread overview]
Message-ID: <4F3052AB.40609@whitecape.org> (raw)
In-Reply-To: <1328482026-28420-3-git-send-email-eugeni.dodonov@intel.com>
On 02/05/2012 02:47 PM, Eugeni Dodonov wrote:
> This adds two cache-related workarounds for Ivy Bridge which can lead to
> 3D ring hangs and corruptions.
>
> Signed-off-by: Eugeni Dodonov<eugeni.dodonov@intel.com>
> ---
> drivers/gpu/drm/i915/i915_reg.h | 7 +++++++
> drivers/gpu/drm/i915/intel_display.c | 6 ++++++
> 2 files changed, 13 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_reg.h b/drivers/gpu/drm/i915/i915_reg.h
> index 80fd6b5..92274b1 100644
> --- a/drivers/gpu/drm/i915/i915_reg.h
> +++ b/drivers/gpu/drm/i915/i915_reg.h
> @@ -3028,6 +3028,13 @@
> #define DISP_TILE_SURFACE_SWIZZLING (1<<13)
> #define DISP_FBC_WM_DIS (1<<15)
>
> +/* GEN7 chicken */
> +#define GEN7_COMMON_SLICE_CHICKEN1 0x7010
> +#define GEN7_WA_FOR_GEN7_L3_CONTROL 0x3C4FFF8C
> +
> +#define GEN7_L3_CHICKEN_MODE_REGISTER 0xB030
> +#define GEN7_WA_L3_CHICKEN_MODE 0x20000000
> +
> /* PCH */
>
> /* south display engine interrupt */
> diff --git a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_display.c
> index 1defd42..eee0e75 100644
> --- a/drivers/gpu/drm/i915/intel_display.c
> +++ b/drivers/gpu/drm/i915/intel_display.c
> @@ -8475,6 +8475,12 @@ static void ivybridge_init_clock_gating(struct drm_device *dev)
> CHICKEN3_DGMG_REQ_OUT_FIX_DISABLE |
> CHICKEN3_DGMG_DONE_FIX_DISABLE);
>
> + /* WaApplyL3ControlAndL3ChickenMode requires those two on Ivy Bridge */
> + I915_WRITE(GEN7_COMMON_SLICE_CHICKEN1,
> + GEN7_WA_FOR_GEN7_L3_CONTROL);
> + I915_WRITE(GEN7_L3_CHICKEN_MODE_REGISTER,
> + GEN7_WA_L3_CHICKEN_MODE);
> +
> for_each_pipe(pipe) {
> I915_WRITE(DSPCNTR(pipe),
> I915_READ(DSPCNTR(pipe)) |
Reviewed-by: Kenneth Graunke <kenneth@whitecape.org>
next prev parent reply other threads:[~2012-02-06 22:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-03 20:22 [PATCH] Ivybridge fixes Eugeni Dodonov
2012-02-03 20:22 ` [PATCH 1/4] drm/i915: gen7: implement rczunit workaround Eugeni Dodonov
2012-02-03 20:22 ` [PATCH 2/4] drm/i915: gen7: add two more IVB workarounds Eugeni Dodonov
2012-02-04 0:45 ` Kenneth Graunke
2012-02-04 0:48 ` Kenneth Graunke
2012-02-03 20:22 ` [PATCH 3/4] drm/i915: gen7: work around a system hang on IVB Eugeni Dodonov
2012-02-04 0:50 ` Kenneth Graunke
2012-02-03 20:22 ` [PATCH 4/4] drm/i915: gen7: another IVB workaround Eugeni Dodonov
2012-02-05 22:47 ` [PATCH 0/3] Ivy Bridge hard-hang fixes Eugeni Dodonov
2012-02-05 22:47 ` [PATCH 1/3] drm/i915: gen7: implement rczunit workaround Eugeni Dodonov
2012-02-06 23:33 ` Kenneth Graunke
2012-02-05 22:47 ` [PATCH 2/3] drm/i915: gen7: add two more IVB workarounds Eugeni Dodonov
2012-02-06 22:22 ` Kenneth Graunke [this message]
2012-02-07 19:48 ` Eric Anholt
2012-02-05 22:47 ` [PATCH 3/3] drm/i915: gen7: work around a system hang on IVB Eugeni Dodonov
2012-02-07 19:46 ` Eric Anholt
2012-02-06 23:25 ` [PATCH 0/3] Ivy Bridge hard-hang fixes Keith Packard
2012-02-07 0:01 ` Eugeni Dodonov
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=4F3052AB.40609@whitecape.org \
--to=kenneth@whitecape.org \
--cc=eugeni.dodonov@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