From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Rodrigo Vivi <rodrigo.vivi@gmail.com>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH 3/3] drm/i915: HSW FBC WaFbcDisableDpfcClockGating
Date: Wed, 10 Apr 2013 11:07:03 +0300 [thread overview]
Message-ID: <20130410080703.GW4469@intel.com> (raw)
In-Reply-To: <CABVU7+sd9XS4GPu1t11QQLPCSTt6thgUFH_OW_hw2pZJPTQ6ZQ@mail.gmail.com>
On Tue, Apr 09, 2013 at 03:05:10PM -0300, Rodrigo Vivi wrote:
> On Tue, Apr 9, 2013 at 5:37 AM, Ville Syrjälä <ville.syrjala@linux.intel.com
> > wrote:
>
> > On Mon, Apr 08, 2013 at 06:49:44PM -0300, Rodrigo Vivi wrote:
> > > Display register 46500h bit 23 must be set to 1b for the entire time that
> > > Frame Buffer Compression is enabled.
> >
> > So should we enable it again after FBC is disabled to avoid wasting
> > power?
> >
>
> I didn't take the opposite direction because it wasn't explicit.
> I tested to enabled it again after FBC is disabled but I didn't see any
> difference.
> So, you suggestion is to enable back anyway?
Perhaps. The idea was that it might save some tiny amount of power.
>
> >
> > >
> > > Signed-off-by: Rodrigo Vivi <rodrigo.vivi@gmail.com>
> > > ---
> > > drivers/gpu/drm/i915/i915_reg.h | 3 +++
> > > drivers/gpu/drm/i915/intel_pm.c | 2 ++
> > > 2 files changed, 5 insertions(+)
> > >
> > > diff --git a/drivers/gpu/drm/i915/i915_reg.h
> > b/drivers/gpu/drm/i915/i915_reg.h
> > > index 2340bc2..2ef0292 100644
> > > --- a/drivers/gpu/drm/i915/i915_reg.h
> > > +++ b/drivers/gpu/drm/i915/i915_reg.h
> > > @@ -863,6 +863,9 @@
> > > _HSW_PIPE_SLICE_CHICKEN_1_A,
> > + \
> > > _HSW_PIPE_SLICE_CHICKEN_1_B)
> > >
> > > +#define HSW_CLKGATE_DISABLE_PART_1 0x46500
> > > +#define HSW_DPFC_GATING_DISABLE (1<<23)
> > > +
> > > /*
> > > * GPIO regs
> > > */
> > > diff --git a/drivers/gpu/drm/i915/intel_pm.c
> > b/drivers/gpu/drm/i915/intel_pm.c
> > > index 0628a84..f2ce541 100644
> > > --- a/drivers/gpu/drm/i915/intel_pm.c
> > > +++ b/drivers/gpu/drm/i915/intel_pm.c
> > > @@ -281,6 +281,8 @@ static void haswell_enable_fbc(struct drm_crtc
> > *crtc, unsigned long interval)
> > > /* WaFbcAsynchFlipDisableFbcQueue */
> > > I915_WRITE(HSW_PIPE_SLICE_CHICKEN_1(intel_crtc->pipe),
> > > HSW_BYPASS_FBC_QUEUE);
> > > + /* WaFbcDisableDpfcClockGating */
> > > + I915_WRITE(HSW_CLKGATE_DISABLE_PART_1, HSW_DPFC_GATING_DISABLE);
> > >
> > > if (obj->fence_reg != I915_FENCE_REG_NONE) {
> > > I915_WRITE(SNB_DPFC_CTL_SA,
> > > --
> > > 1.8.1.4
> > >
> > > _______________________________________________
> > > Intel-gfx mailing list
> > > Intel-gfx@lists.freedesktop.org
> > > http://lists.freedesktop.org/mailman/listinfo/intel-gfx
> >
> > --
> > Ville Syrjälä
> > Intel OTC
> >
>
>
>
> --
> Rodrigo Vivi
> Blog: http://blog.vivi.eng.br
--
Ville Syrjälä
Intel OTC
next prev parent reply other threads:[~2013-04-10 8:07 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-08 21:49 [PATCH 0/3] Enable HSW FBC Rodrigo Vivi
2013-04-08 21:49 ` [PATCH 1/3] drm/i915: Enable FBC at Haswell Rodrigo Vivi
2013-04-09 8:35 ` Ville Syrjälä
2013-04-09 18:13 ` Rodrigo Vivi
2013-04-10 8:18 ` Ville Syrjälä
2013-04-10 8:52 ` Daniel Vetter
2013-04-10 9:28 ` Chris Wilson
2013-04-15 21:14 ` Rodrigo Vivi
2013-04-16 10:28 ` Ville Syrjälä
2013-04-16 13:23 ` Rodrigo Vivi
2013-04-16 13:37 ` Ville Syrjälä
2013-04-16 13:53 ` Rodrigo Vivi
2013-04-15 23:56 ` [PATCH] " Rodrigo Vivi
2013-04-16 8:06 ` Chris Wilson
2013-04-16 13:26 ` Rodrigo Vivi
2013-04-16 14:52 ` Rodrigo Vivi
2013-04-16 16:33 ` Rodrigo Vivi
2013-04-16 17:49 ` Ville Syrjälä
2013-04-16 20:54 ` Rodrigo Vivi
2013-04-17 15:42 ` Chris Wilson
2013-04-08 21:49 ` [PATCH 2/3] drm/i915: HSW FBC WaFbcAsynchFlipDisableFbcQueue Rodrigo Vivi
2013-04-08 21:49 ` [PATCH 3/3] drm/i915: HSW FBC WaFbcDisableDpfcClockGating Rodrigo Vivi
2013-04-09 8:37 ` Ville Syrjälä
2013-04-09 18:05 ` Rodrigo Vivi
2013-04-10 8:07 ` Ville Syrjälä [this message]
2013-04-16 0:03 ` [PATCH] " 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=20130410080703.GW4469@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=rodrigo.vivi@gmail.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