intel-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Cc: mika.kuoppala@intel.com
Subject: Re: [PATCH 3/4] drm/i915: Remove posting-read for forcewake put
Date: Wed, 22 Mar 2017 11:16:30 +0200	[thread overview]
Message-ID: <1490174190.2802.4.camel@linux.intel.com> (raw)
In-Reply-To: <20170322003947.6304-3-chris@chris-wilson.co.uk>

On ke, 2017-03-22 at 00:39 +0000, Chris Wilson wrote:
> We can relax the requirement upon ourselves that the forcewake is
> released immediately and just allow it to occur naturally following our
> mmio request.
> 
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>

Could use T-b.

Reviewed-by: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>

Regards, Joonas
-- 
Joonas Lahtinen
Open Source Technology Center
Intel Corporation
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2017-03-22  9:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-22  0:39 [PATCH 1/4] drm/i915: Eliminate per-fw_domain i915 backpointer Chris Wilson
2017-03-22  0:39 ` [PATCH 2/4] drm/i915: Skip unused fw_domains Chris Wilson
2017-03-22  0:39 ` [PATCH 3/4] drm/i915: Remove posting-read for forcewake put Chris Wilson
2017-03-22  9:16   ` Joonas Lahtinen [this message]
2017-03-22  0:39 ` [PATCH 4/4] drm/i915: All fw_domains share the same set/clear/reset values Chris Wilson
2017-03-22  9:14   ` Joonas Lahtinen
2017-03-22  1:08 ` ✓ Fi.CI.BAT: success for series starting with [1/4] drm/i915: Eliminate per-fw_domain i915 backpointer Patchwork
2017-03-22  8:20 ` [PATCH 1/4] " Joonas Lahtinen

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=1490174190.2802.4.camel@linux.intel.com \
    --to=joonas.lahtinen@linux.intel.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=mika.kuoppala@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;
as well as URLs for NNTP newsgroup(s).