From: Mika Kuoppala <mika.kuoppala@linux.intel.com>
To: Matt Roper <matthew.d.roper@intel.com>, intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH v2 5/6] drm/i915: Apply Wa_1406680159:icl, ehl as an engine workaround
Date: Thu, 12 Mar 2020 18:27:24 +0200 [thread overview]
Message-ID: <87a74l1qtv.fsf@gaia.fi.intel.com> (raw)
In-Reply-To: <20200311162300.1838847-6-matthew.d.roper@intel.com>
Matt Roper <matthew.d.roper@intel.com> writes:
> The register this workaround updates is a render engine register in the
> MCR range, so we should initialize this in rcs_engine_wa_init() rather
> than gt_wa_init().
>
> Closes: https://gitlab.freedesktop.org/drm/intel/issues/1222
> Fixes: 36204d80bacb ("drm/i915/icl: Wa_1406680159")
> Cc: Mika Kuoppala <mika.kuoppala@linux.intel.com>
> Signed-off-by: Matt Roper <matthew.d.roper@intel.com>
At some sunny day mcr range verification might appear.
Reviewed-by: Mika Kuoppala <mika.kuoppala@linux.intel.com>
> ---
> drivers/gpu/drm/i915/gt/intel_workarounds.c | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/gt/intel_workarounds.c b/drivers/gpu/drm/i915/gt/intel_workarounds.c
> index 2318b55b9722..cbfc8d5ebb3e 100644
> --- a/drivers/gpu/drm/i915/gt/intel_workarounds.c
> +++ b/drivers/gpu/drm/i915/gt/intel_workarounds.c
> @@ -920,11 +920,6 @@ icl_gt_workarounds_init(struct drm_i915_private *i915, struct i915_wa_list *wal)
> SLICE_UNIT_LEVEL_CLKGATE,
> MSCUNIT_CLKGATE_DIS);
>
> - /* Wa_1406680159:icl */
> - wa_write_or(wal,
> - SUBSLICE_UNIT_LEVEL_CLKGATE,
> - GWUNIT_CLKGATE_DIS);
> -
> /* Wa_1406838659:icl (pre-prod) */
> if (IS_ICL_REVID(i915, ICL_REVID_A0, ICL_REVID_B0))
> wa_write_or(wal,
> @@ -1487,6 +1482,11 @@ rcs_engine_wa_init(struct intel_engine_cs *engine, struct i915_wa_list *wal)
> /* Wa_1407352427:icl,ehl */
> wa_write_or(wal, UNSLICE_UNIT_LEVEL_CLKGATE2,
> PSDUNIT_CLKGATE_DIS);
> +
> + /* Wa_1406680159:icl,ehl */
> + wa_write_or(wal,
> + SUBSLICE_UNIT_LEVEL_CLKGATE,
> + GWUNIT_CLKGATE_DIS);
> }
>
> if (IS_GEN_RANGE(i915, 9, 12)) {
> --
> 2.24.1
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-03-12 16:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200311162300.1838847-1-matthew.d.roper@intel.com>
2020-03-12 1:11 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for Gen11 workarounds (rev2) Patchwork
2020-03-12 3:59 ` Matt Roper
2020-03-12 5:09 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for Gen11 workarounds (rev3) Patchwork
2020-03-12 6:05 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for Gen11 workarounds (rev4) Patchwork
[not found] ` <20200311162300.1838847-2-matthew.d.roper@intel.com>
2020-03-12 16:25 ` [Intel-gfx] [PATCH v2 1/6] drm/i915: Handle all MCR ranges Mika Kuoppala
[not found] ` <20200311162300.1838847-6-matthew.d.roper@intel.com>
2020-03-12 16:27 ` Mika Kuoppala [this message]
[not found] ` <20200311162300.1838847-7-matthew.d.roper@intel.com>
2020-03-12 16:55 ` [Intel-gfx] [PATCH v2 6/6] drm/i915: Add Wa_1605460711 / Wa_1408767742 to ICL and EHL Mika Kuoppala
2020-03-12 18:49 ` [Intel-gfx] ✓ Fi.CI.BAT: success for Gen11 workarounds (rev5) Patchwork
[not found] ` <20200311162300.1838847-3-matthew.d.roper@intel.com>
2020-03-12 21:46 ` [Intel-gfx] [PATCH v2 2/6] drm/i915: Add Wa_1207131216:icl,ehl Souza, Jose
[not found] ` <20200311162300.1838847-5-matthew.d.roper@intel.com>
2020-03-12 22:07 ` [Intel-gfx] [PATCH v2 4/6] drm/i915: Add Wa_1406306137:icl,ehl Souza, Jose
2020-03-12 22:30 ` Souza, Jose
[not found] ` <20200311162300.1838847-4-matthew.d.roper@intel.com>
2020-03-12 22:38 ` [Intel-gfx] [PATCH v2 3/6] drm/i915: Add Wa_1604278689:icl,ehl Souza, Jose
2020-03-13 8:37 ` [Intel-gfx] ✗ Fi.CI.IGT: failure for Gen11 workarounds (rev5) Patchwork
2020-03-13 16:05 ` Matt Roper
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=87a74l1qtv.fsf@gaia.fi.intel.com \
--to=mika.kuoppala@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=matthew.d.roper@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