From: Mika Kuoppala <mika.kuoppala@linux.intel.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: intel-gfx@lists.freedesktop.org, miku@iki.fi
Subject: Re: [PATCH 5/5] drm/i915: No need to put forcewake after a reset
Date: Wed, 05 Mar 2014 18:11:43 +0200 [thread overview]
Message-ID: <87iorspqv4.fsf@gaia.fi.intel.com> (raw)
In-Reply-To: <20140305145807.GC17001@phenom.ffwll.local>
Daniel Vetter <daniel@ffwll.ch> writes:
> On Fri, Feb 21, 2014 at 05:32:03PM +0200, mika.kuoppala@intel.com wrote:
>> From: Mika Kuoppala <mika.kuoppala@intel.com>
>>
>> As we now have intel_uncore_forcewake_reset() no need
>> to do explicit put after reset.
>>
>> Signed-off-by: Mika Kuoppala <mika.kuoppala@intel.com>
>
> I've merged patches 2-4 from this series now too (patch 1 is already
> merged). But this one conflicts badly with Ville's patch, can you please
> respin?
Didn't find 4/5 from dinq so rebased 4 and 5 on top of dinq at:
1394035700-19630-1-git-send-email-mika.kuoppala@intel.com
-Mika
> Thanks, Daniel
> --
> Daniel Vetter
> Software Engineer, Intel Corporation
> +41 (0) 79 365 57 48 - http://blog.ffwll.ch
prev parent reply other threads:[~2014-03-05 16:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-21 15:31 [PATCH 0/5] bdw forcewake fixes mika.kuoppala
2014-02-21 15:31 ` [PATCH 1/5] drm/i915: Fix forcewake counts for gen8 mika.kuoppala
2014-02-21 19:38 ` Ben Widawsky
2014-02-21 19:42 ` Ben Widawsky
2014-02-21 19:54 ` Chris Wilson
2014-02-24 11:27 ` Ville Syrjälä
2014-02-24 20:29 ` Ben Widawsky
2014-02-21 15:32 ` [PATCH 2/5] drm/i915: Do forcewake reset on gen8 mika.kuoppala
2014-02-21 15:32 ` [PATCH 3/5] drm/i915: Don't access fifodbg registers " mika.kuoppala
2014-02-21 15:36 ` Chris Wilson
2014-02-21 16:47 ` Mika Kuoppala
2014-02-21 15:32 ` [PATCH 4/5] drm/i915: Always set fifo count to zero in gen6_reset mika.kuoppala
2014-02-21 15:32 ` [PATCH 5/5] drm/i915: No need to put forcewake after a reset mika.kuoppala
2014-03-05 14:58 ` Daniel Vetter
2014-03-05 16:11 ` Mika Kuoppala [this message]
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=87iorspqv4.fsf@gaia.fi.intel.com \
--to=mika.kuoppala@linux.intel.com \
--cc=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=miku@iki.fi \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.