From: Daniel Vetter <daniel@ffwll.ch>
To: Nick Hoath <nicholas.hoath@intel.com>
Cc: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH 4/4] drm/i915/bxt: Clean up bxt_init_clock_gating
Date: Mon, 7 Sep 2015 18:19:42 +0200 [thread overview]
Message-ID: <20150907161942.GA32505@phenom.ffwll.local> (raw)
In-Reply-To: <55ED973C.2000104@intel.com>
On Mon, Sep 07, 2015 at 02:55:08PM +0100, Nick Hoath wrote:
> On 29/06/2015 15:29, Mika Kuoppala wrote:
> >Nick Hoath <nicholas.hoath@intel.com> writes:
> >
> >>Add stepping check for A0 workarounds, and remove the associated
> >>FIXME tags.
> >>Split out unrelated WAs for later condition checking.
> >>
> >>v2: Fixed format (PeterL)
> >>v3: Corrected stepping check for WaDisableSDEUnitClockGating
> >> - Ignoring comment, following hardware spec instead. (ChrisH)
> >> Added description for TILECTL setting (JonB)
> >>
> >>Cc: Peter Lawthers <peter.lawthers@intel.com>
> >>Cc: Chris Harris <chris.harris@intel.com>
> >>Cc: Jon Bloomfield <jon.bloomfield@intel.com>
> >>Signed-off-by: Nick Hoath <nicholas.hoath@intel.com>
> >>---
> >> drivers/gpu/drm/i915/intel_pm.c | 16 +++++++++++-----
> >> 1 file changed, 11 insertions(+), 5 deletions(-)
> >>
> >>diff --git a/drivers/gpu/drm/i915/intel_pm.c b/drivers/gpu/drm/i915/intel_pm.c
> >>index 26ef146..86a4ced 100644
> >>--- a/drivers/gpu/drm/i915/intel_pm.c
> >>+++ b/drivers/gpu/drm/i915/intel_pm.c
> >>@@ -115,18 +115,24 @@ static void bxt_init_clock_gating(struct drm_device *dev)
> >>
> >> gen9_init_clock_gating(dev);
> >>
> >>+ /* WaDisableSDEUnitClockGating:bxt */
> >>+ I915_WRITE(GEN8_UCGCTL6, I915_READ(GEN8_UCGCTL6) |
> >>+ GEN8_SDEUNIT_CLOCK_GATE_DISABLE);
> >>+
> >> /*
> >> * FIXME:
> >>- * GEN8_SDEUNIT_CLOCK_GATE_DISABLE applies on A0 only.
> >> * GEN8_HDCUNIT_CLOCK_GATE_DISABLE_HDCREQ applies on 3x6 GT SKUs only.
> >> */
> >>- /* WaDisableSDEUnitClockGating:bxt */
> >> I915_WRITE(GEN8_UCGCTL6, I915_READ(GEN8_UCGCTL6) |
> >>- GEN8_SDEUNIT_CLOCK_GATE_DISABLE |
> >> GEN8_HDCUNIT_CLOCK_GATE_DISABLE_HDCREQ);
> >>
> >
> >I guess you decided not to combine the writes due to FIXME.
> >
> >Reviewed-by: Mika Kuoppala <mika.kuoppala@intel.com>
>
> Looks like this one has fallen through the cracks & not been merged...
Thanks for the ping, applied to dinq.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-09-07 16:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-29 13:07 [PATCH 1/4] drm/i915/bxt: Enable WaVSRefCountFullforceMissDisable Nick Hoath
2015-06-29 13:07 ` [PATCH 2/4] drm/i915/bxt: Enable WaDSRefCountFullforceMissDisable Nick Hoath
2015-06-29 13:07 ` [PATCH 3/4] drm/i915/bxt: Enable WaOCLCoherentLineFlush Nick Hoath
2015-06-29 13:07 ` [PATCH 4/4] drm/i915/bxt: Clean up bxt_init_clock_gating Nick Hoath
2015-06-29 14:29 ` Mika Kuoppala
2015-09-07 13:55 ` Nick Hoath
2015-09-07 16:19 ` Daniel Vetter [this message]
2015-06-30 2:56 ` shuang.he
2015-06-29 14:08 ` [PATCH 1/4] drm/i915/bxt: Enable WaVSRefCountFullforceMissDisable Mika Kuoppala
2015-06-29 14:19 ` Nick Hoath
2015-06-29 14:44 ` Mika Kuoppala
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=20150907161942.GA32505@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=nicholas.hoath@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