public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Matt Roper <matthew.d.roper@intel.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915/gen11: Add Wa_1604278689:icl,ehl
Date: Mon, 19 Aug 2019 09:46:06 -0700	[thread overview]
Message-ID: <20190819164606.GF27240@mdroper-desk.amr.corp.intel.com> (raw)
In-Reply-To: <20190819161356.GV5942@intel.com>

On Mon, Aug 19, 2019 at 07:13:56PM +0300, Ville Syrjälä wrote:
> On Thu, Aug 15, 2019 at 02:58:59PM -0700, Matt Roper wrote:
> > From the bspec:
> > 
> >         "SW must always program the FBC_RT_BASE_ADDR_REGISTER_* register
> >         in Render Engine to a reserved value (0xFFFF_FFFF) such that the
> >         programmed value doesn’t match the render target surface address
> >         programmed. This would disable render engine from generating
> >         modify messages to FBC unit in display."
> 
> This looks a bit peculiar. That magic value seems to imply that the
> RT_VALID bit no longer functions as intended. I filed a spec issue to
> get some clarification on this.

Yeah, this worried me as well, although I figured their logic was that
turning on the 'valid' bit was okay as long as the address comparisons
always returned a mismatch.  However CI starts failing with this
workaround applied, and experimentation with trybot indicates that
the failures go away when I add a "& ~RT_VALID" to the RT_BASE register
value.  I'll submit an updated version that turns that bit off in a bit.


Matt

> 
> > 
> > Bspec: 11388
> > Bspec: 33451
> > Cc: José Roberto de Souza <jose.souza@intel.com>
> > Signed-off-by: Matt Roper <matthew.d.roper@intel.com>
> > ---
> >  drivers/gpu/drm/i915/gt/intel_workarounds.c | 6 ++++++
> >  drivers/gpu/drm/i915/i915_reg.h             | 1 +
> >  2 files changed, 7 insertions(+)
> > 
> > diff --git a/drivers/gpu/drm/i915/gt/intel_workarounds.c b/drivers/gpu/drm/i915/gt/intel_workarounds.c
> > index 704ace01e7f5..29b50e2c0627 100644
> > --- a/drivers/gpu/drm/i915/gt/intel_workarounds.c
> > +++ b/drivers/gpu/drm/i915/gt/intel_workarounds.c
> > @@ -567,6 +567,12 @@ static void icl_ctx_workarounds_init(struct intel_engine_cs *engine,
> >  	/* allow headerless messages for preemptible GPGPU context */
> >  	WA_SET_BIT_MASKED(GEN10_SAMPLER_MODE,
> >  			  GEN11_SAMPLER_ENABLE_HEADLESS_MSG);
> > +
> > +	/* Wa_1604278689:icl,ehl */
> > +	wa_write_masked_or(wal, IVB_FBC_RT_BASE_UPPER,
> > +			   0, /* write-only register; skip validation */
> > +			   0xFFFFFFFF);
> > +	wa_write(wal, IVB_FBC_RT_BASE, 0xFFFFFFFF);
> >  }
> >  
> >  static void
> > diff --git a/drivers/gpu/drm/i915/i915_reg.h b/drivers/gpu/drm/i915/i915_reg.h
> > index def6dbdc7e2e..14af1b1dc0d3 100644
> > --- a/drivers/gpu/drm/i915/i915_reg.h
> > +++ b/drivers/gpu/drm/i915/i915_reg.h
> > @@ -3214,6 +3214,7 @@ enum i915_power_well_id {
> >  
> >  /* Framebuffer compression for Ivybridge */
> >  #define IVB_FBC_RT_BASE			_MMIO(0x7020)
> > +#define IVB_FBC_RT_BASE_UPPER		_MMIO(0x7024)
> 
> That register seems to be BDW+ actually.
> 
> >  
> >  #define IPS_CTL		_MMIO(0x43408)
> >  #define   IPS_ENABLE	(1 << 31)
> > -- 
> > 2.20.1
> > 
> > _______________________________________________
> > Intel-gfx mailing list
> > Intel-gfx@lists.freedesktop.org
> > https://lists.freedesktop.org/mailman/listinfo/intel-gfx
> 
> -- 
> Ville Syrjälä
> Intel

-- 
Matt Roper
Graphics Software Engineer
VTT-OSGC Platform Enablement
Intel Corporation
(916) 356-2795
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2019-08-19 16:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-15 21:58 [PATCH] drm/i915/gen11: Add Wa_1604278689:icl,ehl Matt Roper
2019-08-15 22:19 ` Chris Wilson
2019-08-15 22:24   ` Matt Roper
2019-08-15 23:52 ` ✗ Fi.CI.BAT: failure for " Patchwork
2019-08-16  7:07   ` Chris Wilson
2019-08-16 16:29     ` Matt Roper
2019-08-16 16:38       ` Chris Wilson
2019-08-19 16:13 ` [PATCH] " Ville Syrjälä
2019-08-19 16:46   ` Matt Roper [this message]
2019-08-19 18:08     ` [PATCH v2] " Matt Roper
2019-08-19 20:48 ` ✓ Fi.CI.BAT: success for drm/i915/gen11: Add Wa_1604278689:icl,ehl (rev2) Patchwork
2019-08-20  5:06 ` ✓ 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=20190819164606.GF27240@mdroper-desk.amr.corp.intel.com \
    --to=matthew.d.roper@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