public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Matt Roper <matthew.d.roper@intel.com>,
	Gustavo Sousa <gustavo.sousa@intel.com>
Cc: intel-gfx@lists.freedesktop.org, Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [Intel-gfx] [PATCH v4 1/2] drm/i915/dg2: Introduce Wa_18018764978
Date: Wed, 18 Jan 2023 09:54:56 +0000	[thread overview]
Message-ID: <d020f333-6309-d343-4f57-e1a3c105ddd4@linux.intel.com> (raw)
In-Reply-To: <Y4T9RqbhLBzgXgP6@mdroper-desk1.amr.corp.intel.com>


On 28/11/2022 18:26, Matt Roper wrote:
> On Wed, Nov 23, 2022 at 04:45:25PM -0300, Gustavo Sousa wrote:
>> On Wed, Nov 23, 2022 at 10:36:47AM -0800, Matt Atwood wrote:
>>> Wa_18018764978 applies to specific steppings of DG2 (G10 C0+,
>>> G11 and G12 A0+). Clean up style in function at the same time.
>>>
>>> Bspec: 66622
>>>
>>> Signed-off-by: Matt Atwood <matthew.s.atwood@intel.com>
>>
>> Reviewed-by: Gustavo Sousa <gustavo.sousa@intel.com>
> 
> Both patches applied to drm-intel-gt-next.  Thanks for the patches and
> review.

Do these need to be sent to 6.2 fixes, given DG2 is out of force probe 
there?

Regards,

Tvrtko

>>> ---
>>>   drivers/gpu/drm/i915/gt/intel_gt_regs.h     | 3 +++
>>>   drivers/gpu/drm/i915/gt/intel_workarounds.c | 7 ++++++-
>>>   2 files changed, 9 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/drivers/gpu/drm/i915/gt/intel_gt_regs.h b/drivers/gpu/drm/i915/gt/intel_gt_regs.h
>>> index 80a979e6f6be..74379d3c5a4d 100644
>>> --- a/drivers/gpu/drm/i915/gt/intel_gt_regs.h
>>> +++ b/drivers/gpu/drm/i915/gt/intel_gt_regs.h
>>> @@ -457,6 +457,9 @@
>>>   #define GEN8_L3CNTLREG				_MMIO(0x7034)
>>>   #define   GEN8_ERRDETBCTRL			(1 << 9)
>>>   
>>> +#define PSS_MODE2				_MMIO(0x703c)
>>> +#define   SCOREBOARD_STALL_FLUSH_CONTROL	REG_BIT(5)
>>> +
>>>   #define GEN7_SC_INSTDONE			_MMIO(0x7100)
>>>   #define GEN12_SC_INSTDONE_EXTRA			_MMIO(0x7104)
>>>   #define GEN12_SC_INSTDONE_EXTRA2		_MMIO(0x7108)
>>> diff --git a/drivers/gpu/drm/i915/gt/intel_workarounds.c b/drivers/gpu/drm/i915/gt/intel_workarounds.c
>>> index 2afb4f80a954..870db5a202dd 100644
>>> --- a/drivers/gpu/drm/i915/gt/intel_workarounds.c
>>> +++ b/drivers/gpu/drm/i915/gt/intel_workarounds.c
>>> @@ -771,9 +771,14 @@ static void dg2_ctx_workarounds_init(struct intel_engine_cs *engine,
>>>   
>>>   	/* Wa_14014947963:dg2 */
>>>   	if (IS_DG2_GRAPHICS_STEP(engine->i915, G10, STEP_B0, STEP_FOREVER) ||
>>> -		IS_DG2_G11(engine->i915) || IS_DG2_G12(engine->i915))
>>> +	    IS_DG2_G11(engine->i915) || IS_DG2_G12(engine->i915))
>>>   		wa_masked_field_set(wal, VF_PREEMPTION, PREEMPTION_VERTEX_COUNT, 0x4000);
>>>   
>>> +	/* Wa_18018764978:dg2 */
>>> +	if (IS_DG2_GRAPHICS_STEP(engine->i915, G10, STEP_C0, STEP_FOREVER) ||
>>> +	    IS_DG2_G11(engine->i915) || IS_DG2_G12(engine->i915))
>>> +		wa_masked_en(wal, PSS_MODE2, SCOREBOARD_STALL_FLUSH_CONTROL);
>>> +
>>>   	/* Wa_15010599737:dg2 */
>>>   	wa_masked_en(wal, CHICKEN_RASTER_1, DIS_SF_ROUND_NEAREST_EVEN);
>>>   }
>>> -- 
>>> 2.38.1
>>>
> 

  reply	other threads:[~2023-01-18  9:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-23 18:36 [Intel-gfx] [PATCH v4 1/2] drm/i915/dg2: Introduce Wa_18018764978 Matt Atwood
2022-11-23 18:36 ` [Intel-gfx] [PATCH v4 2/2] drm/i915/dg2: Introduce Wa_18019271663 Matt Atwood
2022-11-23 19:47   ` Gustavo Sousa
2022-11-23 19:45 ` [Intel-gfx] [PATCH v4 1/2] drm/i915/dg2: Introduce Wa_18018764978 Gustavo Sousa
2022-11-28 18:26   ` Matt Roper
2023-01-18  9:54     ` Tvrtko Ursulin [this message]
2023-01-18 17:01       ` Rodrigo Vivi
2023-01-19 21:22         ` Matt Roper
2023-01-19 22:13           ` Gustavo Sousa
2022-11-23 20:30 ` [Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [v4,1/2] " 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=d020f333-6309-d343-4f57-e1a3c105ddd4@linux.intel.com \
    --to=tvrtko.ursulin@linux.intel.com \
    --cc=gustavo.sousa@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=matthew.d.roper@intel.com \
    --cc=rodrigo.vivi@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