From: Deepak S <deepak.s@linux.intel.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v3] drm/i915/chv: Implement WaDisableShadowRegForCpd
Date: Thu, 16 Apr 2015 08:49:18 +0530 [thread overview]
Message-ID: <552F2A36.9000109@linux.intel.com> (raw)
In-Reply-To: <20150415183946.GK1237@intel.com>
On Thursday 16 April 2015 12:09 AM, Ville Syrjälä wrote:
> On Wed, Apr 15, 2015 at 07:41:39PM +0530, deepak.s@linux.intel.com wrote:
>> From: Deepak S <deepak.s@linux.intel.com>
>>
>> This WA is avoid problem between shadow vs wake FIFO unload
>> problem during CPD/RC6 transactions on CHV.
>>
>> v2: Define individual bits GTFIFOCTL (Ville)
>>
>> v3: move WA to uncore_early_sanitize (ville)
>>
>> Signed-off-by: Deepak S <deepak.s@linux.intel.com>
>> ---
>> drivers/gpu/drm/i915/i915_reg.h | 2 ++
>> drivers/gpu/drm/i915/intel_uncore.c | 8 ++++++++
>> 2 files changed, 10 insertions(+)
>>
>> diff --git a/drivers/gpu/drm/i915/i915_reg.h b/drivers/gpu/drm/i915/i915_reg.h
>> index 9c97842..a642a58 100644
>> --- a/drivers/gpu/drm/i915/i915_reg.h
>> +++ b/drivers/gpu/drm/i915/i915_reg.h
>> @@ -6206,6 +6206,8 @@ 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_ALL_POLICY_STALL (1 << 12)
>> +#define GT_FIFO_CTL_RC6_POLICY_STALL (1 << 11)
>>
>> #define HSW_IDICR 0x9008
>> #define IDIHASHMSK(x) (((x) & 0x3f) << 16)
>> diff --git a/drivers/gpu/drm/i915/intel_uncore.c b/drivers/gpu/drm/i915/intel_uncore.c
>> index d96d15f..26d6dda 100644
>> --- a/drivers/gpu/drm/i915/intel_uncore.c
>> +++ b/drivers/gpu/drm/i915/intel_uncore.c
>> @@ -360,6 +360,14 @@ static void __intel_uncore_early_sanitize(struct drm_device *dev,
>> __raw_i915_write32(dev_priv, GTFIFODBG,
>> __raw_i915_read32(dev_priv, GTFIFODBG));
>>
>> + /* WaDisableShadowRegForCpd */
> I couldn't find this w/a name anywhere official, but I guess it's fine.
> Should be WaDisableShadowRegForCpd:chv though. Otherwise looks good, so
>
> Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
Thanks Ville for reviewing. I this the WA still not added to the chv list.
>> + if (IS_CHERRYVIEW(dev)) {
>> + __raw_i915_write32(dev_priv, GTFIFOCTL,
>> + __raw_i915_read32(dev_priv, GTFIFOCTL) |
>> + GT_FIFO_CTL_BLOCK_ALL_POLICY_STALL |
>> + GT_FIFO_CTL_RC6_POLICY_STALL);
>> + }
>> +
>> intel_uncore_forcewake_reset(dev, restore_forcewake);
>> }
>>
>> --
>> 1.9.1
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-04-16 3:22 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ä
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 [this message]
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=552F2A36.9000109@linux.intel.com \
--to=deepak.s@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=ville.syrjala@linux.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