From: Mika Kuoppala <mika.kuoppala@linux.intel.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: "S, Deepak" <deepak.s@intel.com>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Wait old forcewake ack to clear on vlv
Date: Wed, 05 Nov 2014 12:13:40 +0200 [thread overview]
Message-ID: <87k33at0ob.fsf@gaia.fi.intel.com> (raw)
In-Reply-To: <20141105085342.GM10649@intel.com>
Ville Syrjälä <ville.syrjala@linux.intel.com> writes:
> On Wed, Nov 05, 2014 at 10:18:46AM +0200, Mika Kuoppala wrote:
>> Don't rush into getting new fw until the clearing
>> of old one has been acked.
>>
>> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=85684
>> Tested-by: lu hua <huax.lu@intel.com>
>> Signed-off-by: Mika Kuoppala <mika.kuoppala@intel.com>
>
> This is just a revert of
> commit 5cb13c07dae73380d8b3ddc792740487b8742938
> Author: Deepak S <deepak.s@linux.intel.com>
> Date: Thu Sep 18 18:51:50 2014 +0530
>
> drm/i915/vlv: Remove check for Old Ack during forcewake
>
> except you left the comment behind.
I failed at archeology. There is even nice comment from Deepak on
top I managed to miss.
But after reading this comment and the workaround description, I
think that this WaRsDontPollForAckOnClearingFWBits is not valid for
our use case.
We use only one bit per engine, so our use case is not multithreaded
in that sense.
-Mika
> Would be nice to have some kind of real explanation what is going on
> here. Deepak, any ideas?
>
>> ---
>> drivers/gpu/drm/i915/intel_uncore.c | 9 +++++++++
>> 1 file changed, 9 insertions(+)
>>
>> diff --git a/drivers/gpu/drm/i915/intel_uncore.c b/drivers/gpu/drm/i915/intel_uncore.c
>> index 9427641..5259b38 100644
>> --- a/drivers/gpu/drm/i915/intel_uncore.c
>> +++ b/drivers/gpu/drm/i915/intel_uncore.c
>> @@ -204,6 +204,10 @@ static void __vlv_force_wake_get(struct drm_i915_private *dev_priv,
>> /* Check for Render Engine */
>> if (FORCEWAKE_RENDER & fw_engine) {
>>
>> + if (wait_for_atomic((__raw_i915_read32(dev_priv, FORCEWAKE_ACK_VLV) &
>> + FORCEWAKE_KERNEL) == 0, FORCEWAKE_ACK_TIMEOUT_MS))
>> + DRM_ERROR("Timed out: waiting for old Render ack to clear.\n");
>> +
>> __raw_i915_write32(dev_priv, FORCEWAKE_VLV,
>> _MASKED_BIT_ENABLE(FORCEWAKE_KERNEL));
>>
>> @@ -217,6 +221,11 @@ static void __vlv_force_wake_get(struct drm_i915_private *dev_priv,
>> /* Check for Media Engine */
>> if (FORCEWAKE_MEDIA & fw_engine) {
>>
>> + if (wait_for_atomic((__raw_i915_read32(dev_priv, FORCEWAKE_ACK_MEDIA_VLV) &
>> + FORCEWAKE_KERNEL) == 0, FORCEWAKE_ACK_TIMEOUT_MS))
>> + DRM_ERROR("Timed out: waiting for old media ack to clear.\n");
>> +
>> +
>> __raw_i915_write32(dev_priv, FORCEWAKE_MEDIA_VLV,
>> _MASKED_BIT_ENABLE(FORCEWAKE_KERNEL));
>>
>> --
>> 1.9.1
>>
>> _______________________________________________
>> Intel-gfx mailing list
>> Intel-gfx@lists.freedesktop.org
>> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
>
> --
> 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-05 10:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-05 8:18 [PATCH] drm/i915: Wait old forcewake ack to clear on vlv Mika Kuoppala
2014-11-05 8:25 ` Chris Wilson
2014-11-05 15:13 ` Mika Kuoppala
2014-11-05 8:53 ` Ville Syrjälä
2014-11-05 9:26 ` S, Deepak
2014-11-05 10:13 ` Mika Kuoppala [this message]
2014-11-05 12:42 ` Daniel Vetter
2014-11-05 15:30 ` [PATCH] Revert "drm/i915/vlv: Remove check for Old Ack during forcewake" Mika Kuoppala
2014-11-06 14:09 ` Daniel Vetter
2014-11-07 14:58 ` Dave Gordon
2014-11-11 10:24 ` Daniel Vetter
2014-11-05 12:47 ` [PATCH] drm/i915: Wait old forcewake ack to clear on vlv S, Deepak
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=87k33at0ob.fsf@gaia.fi.intel.com \
--to=mika.kuoppala@linux.intel.com \
--cc=deepak.s@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=ville.syrjala@linux.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