All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: deepak.s@intel.com
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 2/2] drm/i915/vlv: Update Wait for FIFO and wait for 20 free entries.
Date: Wed, 27 Nov 2013 19:53:36 +0200	[thread overview]
Message-ID: <20131127175336.GX10036@intel.com> (raw)
In-Reply-To: <1385567202-14706-1-git-send-email-deepak.s@intel.com>

On Wed, Nov 27, 2013 at 09:16:42PM +0530, deepak.s@intel.com wrote:
> From: Deepak S <deepak.s@intel.com>
> 
> On VLV, FIFO will be shared by both SW and HW.

SW I take it means MMIO access coming from the CPU, and HW means eg.
LRI from some CS?

Are there any docs clearly stating this? The Gunit HAS is next to
useless trying to figure out how the internal register accesses
get routed.

> So, we read the
> free entries through register and update dev_priv variable
> and wait for only 20 entries to be free
> 
> Signed-off-by: Deepak S <deepak.s@intel.com>
> ---
>  drivers/gpu/drm/i915/intel_uncore.c | 6 ++++++
>  1 file changed, 6 insertions(+)
> 
> diff --git a/drivers/gpu/drm/i915/intel_uncore.c b/drivers/gpu/drm/i915/intel_uncore.c
> index eac5661..3e7848a 100644
> --- a/drivers/gpu/drm/i915/intel_uncore.c
> +++ b/drivers/gpu/drm/i915/intel_uncore.c
> @@ -147,6 +147,12 @@ static int __gen6_gt_wait_for_fifo(struct drm_i915_private *dev_priv)
>  {
>  	int ret = 0;
>  
> +	/* On VLV, FIFO will be shared by both SW and HW.
> +	 * So, we need to read the FREE_ENTRIES everytime */
> +	if (IS_VALLEYVIEW(dev_priv->dev))
> +		dev_priv->uncore.fifo_count =
> +			__raw_i915_read32(dev_priv, GT_FIFO_FREE_ENTRIES);

This would need to mask the free entries. I sent out a patch to fix the
already existing cases, but you'd need to do it here too.

> +
>  	if (dev_priv->uncore.fifo_count < GT_FIFO_NUM_RESERVED_ENTRIES) {
>  		int loop = 500;
>  		u32 fifo = __raw_i915_read32(dev_priv, GT_FIFO_FREE_ENTRIES);
> -- 
> 1.8.4.2
> 
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx

-- 
Ville Syrjälä
Intel OTC

      reply	other threads:[~2013-11-27 17:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-27 15:46 [PATCH 2/2] drm/i915/vlv: Update Wait for FIFO and wait for 20 free entries deepak.s
2013-11-27 17:53 ` Ville Syrjälä [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=20131127175336.GX10036@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=deepak.s@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    /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.