All of lore.kernel.org
 help / color / mirror / Atom feed
From: "S, Deepak" <deepak.s@intel.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>,
	intel-gfx@lists.freedesktop.org
Subject: Re: Fwd: [PATCH 1/2] drm/i915: Fix VLV forcewake after reset
Date: Thu, 27 Feb 2014 19:54:49 +0530	[thread overview]
Message-ID: <530F4AB1.8000701@intel.com> (raw)
In-Reply-To: <CAOh5HuXvv4Kcp+mCYCPp+hb06M_CxZ-Z+hivB7TOcn72tsaBcQ@mail.gmail.com>


On Wed, Jan 29, 2014 at 9:55 AM, ville syrjala
>
>
> ---------- Forwarded message ----------
> From: ** <ville.syrjala@linux.intel.com
> <mailto:ville.syrjala@linux.intel.com>>
> Date: Mon, Feb 24, 2014 at 8:32 PM
> Subject: [Intel-gfx] [PATCH 1/2] drm/i915: Fix VLV forcewake after reset
> To: intel-gfx@lists.freedesktop.org <mailto:intel-gfx@lists.freedesktop.org>
>
>
> From: Ville Syrjälä <ville.syrjala@linux.intel.com
> <mailto:ville.syrjala@linux.intel.com>>
>
> Use the render/media specific forcewake counts to properly restore the
> forcewake status after a GPU reset on VLV.
>
> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com
> <mailto:ville.syrjala@linux.intel.com>>
> ---
>   drivers/gpu/drm/i915/intel_uncore.c | 20 ++++++++++++++++----
>   1 file changed, 16 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/intel_uncore.c
> b/drivers/gpu/drm/i915/intel_uncore.c
> index c628414..09fa555 100644
> --- a/drivers/gpu/drm/i915/intel_uncore.c
> +++ b/drivers/gpu/drm/i915/intel_uncore.c
> @@ -967,10 +967,22 @@ static int gen6_do_reset(struct drm_device *dev)
>          intel_uncore_forcewake_reset(dev);
>
>          /* If reset with a user forcewake, try to restore, otherwise
> turn it off */
> -       if (dev_priv->uncore.forcewake_count)
> -               dev_priv->uncore.funcs.force_wake_get(dev_priv,
> FORCEWAKE_ALL);
> -       else
> -               dev_priv->uncore.funcs.force_wake_put(dev_priv,
> FORCEWAKE_ALL);
> +       if (IS_VALLEYVIEW(dev)) {
> +               if (dev_priv->uncore.fw_rendercount)
> +                       dev_priv->uncore.funcs.force_wake_get(dev_priv,
> FORCEWAKE_RENDER);
> +               else
> +                       dev_priv->uncore.funcs.force_wake_put(dev_priv,
> FORCEWAKE_RENDER);
> +
> +               if (dev_priv->uncore.fw_mediacount)
> +                       dev_priv->uncore.funcs.force_wake_get(dev_priv,
> FORCEWAKE_MEDIA);
> +               else
> +                       dev_priv->uncore.funcs.force_wake_put(dev_priv,
> FORCEWAKE_MEDIA);
> +       } else {
> +               if (dev_priv->uncore.forcewake_count)
> +                       dev_priv->uncore.funcs.force_wake_get(dev_priv,
> FORCEWAKE_ALL);
> +               else
> +                       dev_priv->uncore.funcs.force_wake_put(dev_priv,
> FORCEWAKE_ALL);
> +       }
>
>          /* Restore fifo count */
>          dev_priv->uncore.fifo_count = __raw_i915_read32(dev_priv,
> GTFIFOCTL) & GT_FIFO_FREE_ENTRIES_MASK;
> --
> 1.8.3.2
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org <mailto:Intel-gfx@lists.freedesktop.org>
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
>

Reviewed-by: Deepak S <deepak.s@intel.com>

  parent reply	other threads:[~2014-02-27 14:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-24 15:02 [PATCH 0/2] drm/i915: VLV forcewake fixes ville.syrjala
2014-02-24 15:02 ` [PATCH 1/2] drm/i915: Fix VLV forcewake after reset ville.syrjala
     [not found]   ` <CAOh5HuXvv4Kcp+mCYCPp+hb06M_CxZ-Z+hivB7TOcn72tsaBcQ@mail.gmail.com>
2014-02-27 14:24     ` S, Deepak [this message]
2014-03-05 14:00   ` Daniel Vetter
2014-02-24 15:02 ` [PATCH 2/2] drm/i915: Drop the forcewake count inc/dec around register read on VLV ville.syrjala
     [not found]   ` <CAOh5HuU0eA0Pb3q=xDP_T_7N8TfWCbKuHZ==dh2G=V_uQfNZww@mail.gmail.com>
2014-02-27 14:26     ` Fwd: " S, Deepak
2014-02-27 20:07 ` [PATCH 3/2] drm/i915: Streamline VLV forcewake handling ville.syrjala
2014-02-28 14:26   ` S, Deepak
2014-02-28 14:51     ` Ville Syrjälä
2014-03-05 14:03       ` Daniel Vetter

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=530F4AB1.8000701@intel.com \
    --to=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 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.