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 2/2] drm/i915: Drop the forcewake count inc/dec around register read on VLV
Date: Thu, 27 Feb 2014 19:56:23 +0530 [thread overview]
Message-ID: <530F4B0F.2040203@intel.com> (raw)
In-Reply-To: <CAOh5HuU0eA0Pb3q=xDP_T_7N8TfWCbKuHZ==dh2G=V_uQfNZww@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 2/2] drm/i915: Drop the forcewake count
> inc/dec around register read on VLV
> 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>>
>
> VLV is the only platform where we increment/decrement the forcewake
> count around register access. Drop the inc/dec on VLV to make the
> forcewake code a bit more unified.
>
> The inc/dec are not necessary since we hold the uncore lock around
> the whole operation.
>
> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com
> <mailto:ville.syrjala@linux.intel.com>>
> ---
> drivers/gpu/drm/i915/intel_uncore.c | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/intel_uncore.c
> b/drivers/gpu/drm/i915/intel_uncore.c
> index 09fa555..dacb751 100644
> --- a/drivers/gpu/drm/i915/intel_uncore.c
> +++ b/drivers/gpu/drm/i915/intel_uncore.c
> @@ -502,22 +502,22 @@ gen6_read##x(struct drm_i915_private *dev_priv,
> off_t reg, bool trace) { \
> static u##x \
> vlv_read##x(struct drm_i915_private *dev_priv, off_t reg, bool trace) { \
> unsigned fwengine = 0; \
> - unsigned *fwcount; \
> + unsigned fwcount; \
> REG_READ_HEADER(x); \
> if (FORCEWAKE_VLV_RENDER_RANGE_OFFSET(reg)) { \
> fwengine = FORCEWAKE_RENDER; \
> - fwcount = &dev_priv->uncore.fw_rendercount; \
> + fwcount = dev_priv->uncore.fw_rendercount; \
> } \
> else if (FORCEWAKE_VLV_MEDIA_RANGE_OFFSET(reg)) { \
> fwengine = FORCEWAKE_MEDIA; \
> - fwcount = &dev_priv->uncore.fw_mediacount; \
> + fwcount = dev_priv->uncore.fw_mediacount; \
> } \
> if (fwengine != 0) { \
> - if ((*fwcount)++ == 0) \
> + if (fwcount == 0) \
> (dev_priv)->uncore.funcs.force_wake_get(dev_priv, \
>
> fwengine); \
> val = __raw_i915_read##x(dev_priv, reg); \
> - if (--(*fwcount) == 0) \
> + if (fwcount == 0) \
> (dev_priv)->uncore.funcs.force_wake_put(dev_priv, \
> fwengine); \
> } else { \
> --
> 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>
next prev parent reply other threads:[~2014-02-27 14:26 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 ` Fwd: " S, Deepak
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 ` S, Deepak [this message]
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=530F4B0F.2040203@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox