From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
Lucas De Marchi <lucas.demarchi@intel.com>,
intel-gfx@lists.freedesktop.org
Cc: Michel Thierry <michel.thierry@intel.com>
Subject: Re: [PATCH 2/3] drm/i915/tgl: Implement Wa_1604555607
Date: Fri, 26 Jul 2019 14:15:51 +0100 [thread overview]
Message-ID: <54eaffac-0d15-109d-6d9b-98eb6b2a604f@linux.intel.com> (raw)
In-Reply-To: <156409982772.30723.16146937485087701539@skylake-alporthouse-com>
On 26/07/2019 01:10, Chris Wilson wrote:
> Quoting Lucas De Marchi (2019-07-26 01:02:25)
>> From: Michel Thierry <michel.thierry@intel.com>
>>
>> Implement Wa_1604555607 (set the DS pairing timer to 128 cycles).
>> FF_MODE2 is part of the register state context, that's why it is
>> implemented here.
>>
>> Signed-off-by: Michel Thierry <michel.thierry@intel.com>
>> Signed-off-by: Lucas De Marchi <lucas.demarchi@intel.com>
>> ---
>> drivers/gpu/drm/i915/gt/intel_workarounds.c | 7 +++++++
>> drivers/gpu/drm/i915/i915_reg.h | 5 +++++
>> 2 files changed, 12 insertions(+)
>>
>> diff --git a/drivers/gpu/drm/i915/gt/intel_workarounds.c b/drivers/gpu/drm/i915/gt/intel_workarounds.c
>> index a6eb9c6e87ec..3235ef355dfd 100644
>> --- a/drivers/gpu/drm/i915/gt/intel_workarounds.c
>> +++ b/drivers/gpu/drm/i915/gt/intel_workarounds.c
>> @@ -572,6 +572,13 @@ static void icl_ctx_workarounds_init(struct intel_engine_cs *engine,
>> static void tgl_ctx_workarounds_init(struct intel_engine_cs *engine,
>> struct i915_wa_list *wal)
>> {
>> + u32 val;
>> +
>> + /* Wa_1604555607:tgl */
>> + val = intel_uncore_read(engine->uncore, FF_MODE2);
>> + val &= ~FF_MODE2_TDS_TIMER_MASK;
>> + val |= FF_MODE2_TDS_TIMER_128;
>> + wa_write_masked_or(wal, FF_MODE2, FF_MODE2_TDS_TIMER_MASK, val);
>
> It will do a rmw on application, so you just need
> wa_write_masked_or(wal, FF_MODE2,
> FF_MODE2_TDS_TIMER_MASK, FF_MODE2_TDS_TIMER_128);
Not with ctx was unfortunately, no rmw there, just lri.
To be less misleading perhaps:
wa_write(wal, FF_MODE2, val);
?
It only affects verification, do we want to verify the whole register or
just the FF_MODE2_TDS_TIMER_MASK bits. Since the code reads it and sets
it, it may want to check it whole.
Regards,
Tvrtko
>
>> }
>>
>> static void
>> diff --git a/drivers/gpu/drm/i915/i915_reg.h b/drivers/gpu/drm/i915/i915_reg.h
>> index 54ea250000be..fbbb89f6ca2f 100644
>> --- a/drivers/gpu/drm/i915/i915_reg.h
>> +++ b/drivers/gpu/drm/i915/i915_reg.h
>> @@ -7771,6 +7771,11 @@ enum {
>> #define PIXEL_ROUNDING_TRUNC_FB_PASSTHRU (1 << 15)
>> #define PER_PIXEL_ALPHA_BYPASS_EN (1 << 7)
>>
>> +#define FF_MODE2 _MMIO(0x6604)
>> +#define FF_MODE2_TDS_TIMER_SHIFT (16)
>> +#define FF_MODE2_TDS_TIMER_128 (4 << FF_MODE2_TDS_TIMER_SHIFT)
>> +#define FF_MODE2_TDS_TIMER_MASK (0xff << FF_MODE2_TDS_TIMER_SHIFT)
>
> #define FF_MODE2_TDS_TIMER_MASK REG_GENMASK(23, 16)
> #define FF_MODE2_TDS_TIMER_128 REG_FIELD_PREP(FF_MODE2_TDS_TIMER_MASK, 4)
> -Chris
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-07-26 13:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-26 0:02 [PATCH 0/3] Tiger Lake: add workarounds Lucas De Marchi
2019-07-26 0:02 ` [PATCH 1/3] drm/i915/tgl: Introduce initial Tigerlake Workarounds Lucas De Marchi
2019-08-12 22:29 ` Radhakrishna Sripada
2019-08-13 18:07 ` Radhakrishna Sripada
2019-08-16 2:47 ` Lucas De Marchi
2019-07-26 0:02 ` [PATCH 2/3] drm/i915/tgl: Implement Wa_1604555607 Lucas De Marchi
2019-07-26 0:10 ` Chris Wilson
2019-07-26 13:15 ` Tvrtko Ursulin [this message]
2019-07-26 13:20 ` Chris Wilson
2019-07-26 13:34 ` Tvrtko Ursulin
2019-07-26 13:55 ` Chris Wilson
2019-07-26 0:02 ` [PATCH 3/3] drm/i915/tgl: Implement Wa_1406941453 Lucas De Marchi
2019-08-12 22:10 ` Radhakrishna Sripada
2019-07-26 2:47 ` ✓ Fi.CI.BAT: success for Tiger Lake: add workarounds Patchwork
2019-07-27 4:36 ` ✓ Fi.CI.IGT: " 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=54eaffac-0d15-109d-6d9b-98eb6b2a604f@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=lucas.demarchi@intel.com \
--cc=michel.thierry@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