From: Jani Nikula <jani.nikula@linux.intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [PATCH 1/5] drm/i915: Organize Fence registers for future enablement.
Date: Thu, 04 Dec 2014 09:47:57 +0200 [thread overview]
Message-ID: <87vblrn9ea.fsf@intel.com> (raw)
In-Reply-To: <1417611329-6056-2-git-send-email-rodrigo.vivi@intel.com>
On Wed, 03 Dec 2014, Rodrigo Vivi <rodrigo.vivi@intel.com> wrote:
> Let's be optimistic that for future platforms this will remain the same
> and reorg a bit.
> This reorg in if blocks instead of switch make life easier for future
> platform support addition.
>
> Cc: Damien Lespiau <damien.lespiau@intel.com>
> Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
> ---
> drivers/gpu/drm/i915/i915_gem.c | 17 ++++++----------
> drivers/gpu/drm/i915/i915_gpu_error.c | 37 ++++++++++++-----------------------
> 2 files changed, 19 insertions(+), 35 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_gem.c b/drivers/gpu/drm/i915/i915_gem.c
> index 9d362d3..1b320bd 100644
> --- a/drivers/gpu/drm/i915/i915_gem.c
> +++ b/drivers/gpu/drm/i915/i915_gem.c
> @@ -3271,17 +3271,12 @@ static void i915_gem_write_fence(struct drm_device *dev, int reg,
> "bogus fence setup with stride: 0x%x, tiling mode: %i\n",
> obj->stride, obj->tiling_mode);
>
> - switch (INTEL_INFO(dev)->gen) {
> - case 9:
> - case 8:
> - case 7:
> - case 6:
> - case 5:
> - case 4: i965_write_fence_reg(dev, reg, obj); break;
> - case 3: i915_write_fence_reg(dev, reg, obj); break;
> - case 2: i830_write_fence_reg(dev, reg, obj); break;
> - default: BUG();
> - }
> + if (IS_GEN2(dev))
> + i830_write_fence_reg(dev, reg, obj);
> + else if (IS_GEN3(dev))
> + i915_write_fence_reg(dev, reg, obj);
> + else if (INTEL_INFO(dev)->gen >= 4)
> + i965_write_fence_reg(dev, reg, obj);
>
> /* And similarly be paranoid that no direct access to this region
> * is reordered to before the fence is installed.
> diff --git a/drivers/gpu/drm/i915/i915_gpu_error.c b/drivers/gpu/drm/i915/i915_gpu_error.c
> index c4536e1..f117a1d 100644
> --- a/drivers/gpu/drm/i915/i915_gpu_error.c
> +++ b/drivers/gpu/drm/i915/i915_gpu_error.c
> @@ -766,32 +766,21 @@ static void i915_gem_record_fences(struct drm_device *dev,
> struct drm_i915_private *dev_priv = dev->dev_private;
> int i;
>
> - /* Fences */
> - switch (INTEL_INFO(dev)->gen) {
> - case 9:
> - case 8:
> - case 7:
> - case 6:
> - for (i = 0; i < dev_priv->num_fence_regs; i++)
> - error->fence[i] = I915_READ64(FENCE_REG_SANDYBRIDGE_0 + (i * 8));
> - break;
> - case 5:
> - case 4:
> - for (i = 0; i < 16; i++)
> - error->fence[i] = I915_READ64(FENCE_REG_965_0 + (i * 8));
> - break;
> - case 3:
> - if (IS_I945G(dev) || IS_I945GM(dev) || IS_G33(dev))
> - for (i = 0; i < 8; i++)
> - error->fence[i+8] = I915_READ(FENCE_REG_945_8 + (i * 4));
> - case 2:
> + if (IS_I945G(dev) || IS_I945GM(dev) || IS_G33(dev))
> + for (i = 0; i < 8; i++)
> + error->fence[i+8] = I915_READ(FENCE_REG_945_8 +
> + (i * 4));
Do note the fallthrough from case 3 to case 2 in the original. For these
platforms you'll also need the ones below. Maybe add two loops or loop
to 16 and add an if (i < 8) inside?
BR,
Jani.
> + else if (IS_GEN3(dev) || IS_GEN2(dev))
> for (i = 0; i < 8; i++)
> error->fence[i] = I915_READ(FENCE_REG_830_0 + (i * 4));
> - break;
> -
> - default:
> - BUG();
> - }
> + else if (IS_GEN5(dev) || IS_GEN4(dev))
> + for (i = 0; i < 16; i++)
> + error->fence[i] = I915_READ64(FENCE_REG_965_0 +
> + (i * 8));
> + else if (INTEL_INFO(dev)->gen >= 6)
> + for (i = 0; i < dev_priv->num_fence_regs; i++)
> + error->fence[i] = I915_READ64(FENCE_REG_SANDYBRIDGE_0 +
> + (i * 8));
> }
>
>
> --
> 1.9.3
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2014-12-04 7:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-03 12:55 [PATCH 0/5] reorg for future Rodrigo Vivi
2014-12-03 12:55 ` [PATCH 1/5] drm/i915: Organize Fence registers for future enablement Rodrigo Vivi
2014-12-04 7:47 ` Jani Nikula [this message]
2014-12-04 14:48 ` [PATCH] " Rodrigo Vivi
2014-12-05 5:33 ` shuang.he
2014-12-16 19:55 ` Paulo Zanoni
2014-12-03 12:55 ` [PATCH 2/5] drm/i915: Organize PPGTT init Rodrigo Vivi
2014-12-03 12:55 ` [PATCH 3/5] drm/i915: Organize PDP regs report for future Rodrigo Vivi
2014-12-03 12:55 ` [PATCH 4/5] drm/i915: Organize INSTDONE " Rodrigo Vivi
2014-12-03 12:55 ` [PATCH 5/5] drm/i915: Organize bind_vma funcs Rodrigo Vivi
2014-12-04 13:51 ` shuang.he
2014-12-16 20:12 ` [PATCH 0/5] reorg for future Paulo Zanoni
2014-12-17 17:19 ` 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=87vblrn9ea.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=rodrigo.vivi@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.