From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: intel-gfx@lists.freedesktop.org, Mika Kuoppala <mika.kuoppala@intel.com>
Subject: Re: [PATCH 8/8] drm/i915: Wait thread status on gen8+ fw sequence
Date: Tue, 11 Nov 2014 19:12:29 +0200 [thread overview]
Message-ID: <20141111171229.GK10649@intel.com> (raw)
In-Reply-To: <1415623970-1795-9-git-send-email-rodrigo.vivi@intel.com>
On Mon, Nov 10, 2014 at 04:52:50AM -0800, Rodrigo Vivi wrote:
> From: Mika Kuoppala <mika.kuoppala@linux.intel.com>
>
> As per latest pm guide, we need to do this also on
> past hsw.
Yep, matches the doc.
Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
BTW I wonder why we also wait for the [18:16] bits to clear on HSW? I don't
see such a thing documented in the HSW PM guide I have here. Maybe we can
just drop the HSW special case?
Also I wonder if we want this on CHV too. I should probably know, but I
dont't. I'll go bash some registers and see what they say...
>
> Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
> Cc: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Damien Lespiau <damien.lespiau@intel.com>
> Signed-off-by: Mika Kuoppala <mika.kuoppala@intel.com>
> Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
> ---
> drivers/gpu/drm/i915/intel_uncore.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/intel_uncore.c b/drivers/gpu/drm/i915/intel_uncore.c
> index 6a0c3fb..86a755a 100644
> --- a/drivers/gpu/drm/i915/intel_uncore.c
> +++ b/drivers/gpu/drm/i915/intel_uncore.c
> @@ -120,8 +120,7 @@ static void __gen7_gt_force_wake_mt_get(struct drm_i915_private *dev_priv,
> DRM_ERROR("Timed out waiting for forcewake to ack request.\n");
>
> /* WaRsForcewakeWaitTC0:ivb,hsw */
> - if (INTEL_INFO(dev_priv->dev)->gen < 8)
> - __gen6_gt_wait_for_thread_c0(dev_priv);
> + __gen6_gt_wait_for_thread_c0(dev_priv);
> }
>
> static void gen6_gt_check_fifodbg(struct drm_i915_private *dev_priv)
> --
> 1.9.3
--
Ville Syrjälä
Intel OTC
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2014-11-11 17:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-10 12:52 [PATCH 0/8] drm-intel-collector - update Rodrigo Vivi
2014-11-10 12:52 ` [PATCH 1/8] drm/i915: Make the physical object coherent with GTT Rodrigo Vivi
2014-11-10 12:52 ` [PATCH 2/8] drm/i915: Specify bsd rings through exec flag Rodrigo Vivi
2014-11-14 0:54 ` Rodrigo Vivi
2014-11-10 12:52 ` [PATCH 3/8] drm/i915: add I915_PARAM_HAS_BSD2 to i915_getparam Rodrigo Vivi
2014-11-14 0:56 ` Rodrigo Vivi
2014-11-10 12:52 ` [PATCH 4/8] drm/i915: Move the ban period onto the context Rodrigo Vivi
2014-11-10 12:52 ` [PATCH 5/8] drm/i915: Add ioctl to set per-context parameters Rodrigo Vivi
2014-11-10 12:52 ` [PATCH 6/8] drm/i915: Put logical pipe_control emission into a helper Rodrigo Vivi
2014-11-10 12:52 ` [PATCH 7/8] drm/i915: Add WaCsStallBeforeStateCacheInvalidate:bdw, chv to logical ring Rodrigo Vivi
2014-11-10 12:52 ` [PATCH 8/8] drm/i915: Wait thread status on gen8+ fw sequence Rodrigo Vivi
2014-11-11 14:57 ` [PATCH 8/8] drm/i915: Wait thread status on gen8+ fw shuang.he
2014-11-11 17:12 ` Ville Syrjälä [this message]
2014-11-11 17:26 ` [PATCH 8/8] drm/i915: Wait thread status on gen8+ fw sequence Ville Syrjälä
2014-11-12 9:28 ` Daniel Vetter
2014-11-12 11:26 ` Ville Syrjälä
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=20141111171229.GK10649@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=mika.kuoppala@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