From: Paulo Zanoni <paulo.r.zanoni@intel.com>
To: Rodrigo Vivi <rodrigo.vivi@gmail.com>,
Jani Nikula <jani.nikula@intel.com>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>,
Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [PATCH] drm/i915/cnl: WaFbcSkipSegments
Date: Mon, 04 Sep 2017 15:05:52 -0300 [thread overview]
Message-ID: <1504548352.2824.2.camel@intel.com> (raw)
In-Reply-To: <CABVU7+sDugxHf_utaqD+-b5Sj8zdfT9vHV47pGqMDdBdonaUFA@mail.gmail.com>
Em Sex, 2017-09-01 às 14:31 -0700, Rodrigo Vivi escreveu:
> On Fri, Sep 1, 2017 at 2:04 PM, Paulo Zanoni <paulo.r.zanoni@intel.co
> m> wrote:
> > Em Ter, 2017-08-29 às 16:08 -0700, Rodrigo Vivi escreveu:
> > > Skip compressing 1 segment at the end of the frame,
> > > avoid a pixel count mismatch nuke event when last active
> > > pixel and dummy pixel has same color for Odd Plane
> > > Width / Height.
> > >
> > > Cc: Paulo Zanoni <paulo.r.zanoni@intel.com>
> > > Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
> > > ---
> > > drivers/gpu/drm/i915/i915_reg.h | 2 ++
> > > drivers/gpu/drm/i915/intel_pm.c | 4 ++++
> > > 2 files changed, 6 insertions(+)
> > >
> > > diff --git a/drivers/gpu/drm/i915/i915_reg.h
> > > b/drivers/gpu/drm/i915/i915_reg.h
> > > index e2908ae34004..0072ef79bf34 100644
> > > --- a/drivers/gpu/drm/i915/i915_reg.h
> > > +++ b/drivers/gpu/drm/i915/i915_reg.h
> > > @@ -2939,6 +2939,8 @@ enum i915_power_well_id {
> > > #define ILK_DPFC_CHICKEN _MMIO(0x43224)
> > > #define ILK_DPFC_DISABLE_DUMMY0 (1<<8)
> > > #define ILK_DPFC_NUKE_ON_ANY_MODIFICATION (1<<23)
> > > +#define CNL_SKIP_SEG_EN (1<<12)
> > > +#define CNL_SKIP_SEG_COUNT (1<<10)
> >
> > #define CNL_SKIP_SEG_COUNT_MASK (3 << 10)
> > #define CNL_SKIP_SEG_COUNT(x) ((x) << 10)
>
> By the definition we should add the SHIFT then as well?
> Although we are not going to read ever?!
I don't see the point in adding it if we're not using it. Most of the
times where we have the function-like macro we don't need _SHIFT, but
_MASK is needed due to the RMW.
>
> >
> > Also, since you're going to submit v2 anyway, I wouldn't complain
> > if
> > you drive-by fixed the definitions of ILK_DPFC_CHICKEN bits to use
> > spaces as documented in the beginning of the file. If we fix every
> > time
> > we touch a reg, we may at some point be consistent :).
>
> Last patch I tried to fix the style on the same patch Jani nacked it.
> So I wonder if we need a bit patch to fix all the style entirely.
I just gave a suggestion, fixing the spacing is not required in this
patch.
>
> >
> >
> > > #define ILK_FBC_RT_BASE _MMIO(0x2128)
> > > #define ILK_FBC_RT_VALID (1<<0)
> > > #define SNB_FBC_FRONT_BUFFER (1<<1)
> > > diff --git a/drivers/gpu/drm/i915/intel_pm.c
> > > b/drivers/gpu/drm/i915/intel_pm.c
> > > index d5ff0b9f999f..acf793256507 100644
> > > --- a/drivers/gpu/drm/i915/intel_pm.c
> > > +++ b/drivers/gpu/drm/i915/intel_pm.c
> > > @@ -8283,6 +8283,10 @@ static void
> > > cannonlake_init_clock_gating(struct drm_i915_private *dev_priv)
> > > I915_WRITE(SLICE_UNIT_LEVEL_CLKGATE,
> > > I915_READ(SLICE_UNIT_LEVEL_CLKGATE) |
> > > SARBUNIT_CLKGATE_DIS);
> > > +
> > > + /* WaFbcSkipSegments:cnl */
> >
> > Since this is also documented in BSpec but it doesn't include the
> > WA
> > name, can you please also document that this is WA #1133 in this
> > comment? I'd do something like:
> >
> > /* Display WA #1133: WaFbcSkipSegments:cnl,glk. */
>
> good idea!
>
> >
> > Please notice that we also need to apply this WA for GLK.
>
> hm... indeed...
> >
> >
> > > + I915_WRITE(ILK_DPFC_CHICKEN, I915_READ(ILK_DPFC_CHICKEN) |
> > > + CNL_SKIP_SEG_EN | CNL_SKIP_SEG_COUNT);
> >
> > Need to clear bit 11 too.
>
> ouch! yeap!
>
> Thanks,
> Rodrigo.
>
> >
> > val = READ();
> > val &= ~CNL_SKIP_SEG_COUNT_MASK;
> > val |= CNL_SKIP_SEG_EN | CNL_SKIP_SEG_COUNT(1);
> >
> > > }
> > >
> > > static void kabylake_init_clock_gating(struct drm_i915_private
> > > *dev_priv)
> >
> > _______________________________________________
> > 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:[~2017-09-04 18:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-29 23:08 [PATCH] drm/i915/cnl: WaFbcSkipSegments Rodrigo Vivi
2017-08-29 23:59 ` ✓ Fi.CI.BAT: success for " Patchwork
2017-08-30 3:40 ` ✗ Fi.CI.IGT: failure " Patchwork
2017-09-01 21:04 ` [PATCH] " Paulo Zanoni
2017-09-01 21:31 ` Rodrigo Vivi
2017-09-04 18:05 ` Paulo Zanoni [this message]
2017-09-05 17:56 ` Rodrigo Vivi
2017-09-05 18:05 ` [PATCH] drm/i915: Display WA #1133 WaFbcSkipSegments:cnl, glk Rodrigo Vivi
2017-09-05 18:59 ` Paulo Zanoni
2017-09-05 19:07 ` Rodrigo Vivi
2017-09-05 19:16 ` Paulo Zanoni
2017-09-05 18:23 ` ✓ Fi.CI.BAT: success for drm/i915/cnl: WaFbcSkipSegments (rev3) Patchwork
2017-09-05 19:26 ` ✓ Fi.CI.BAT: success for drm/i915/cnl: WaFbcSkipSegments (rev4) Patchwork
2017-09-05 20:43 ` ✗ Fi.CI.IGT: warning for drm/i915/cnl: WaFbcSkipSegments (rev3) Patchwork
2017-09-05 22:19 ` ✗ Fi.CI.IGT: failure for drm/i915/cnl: WaFbcSkipSegments (rev4) Patchwork
[not found] <Message-id: <1504638961.2824.38.camel@intel.com>
2017-09-05 19:30 ` [PATCH] drm/i915: Display WA #1133 WaFbcSkipSegments:cnl, glk Rodrigo Vivi
2017-09-06 20:43 ` Rodrigo Vivi
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=1504548352.2824.2.camel@intel.com \
--to=paulo.r.zanoni@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=rodrigo.vivi@gmail.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