All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wilson <chris@chris-wilson.co.uk>
To: Matthew Auld <matthew.william.auld@gmail.com>
Cc: Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: Re: [RFCv2 16/19] drm/i915: Sanity check all registers for matching fw domains
Date: Wed, 11 Jan 2017 18:39:08 +0000	[thread overview]
Message-ID: <20170111183908.GF16278@nuc-i3427.alporthouse.com> (raw)
In-Reply-To: <CAM0jSHPhtHYUvNS6gmk9p7hJmq8-Jmg96knNny+jir4jtxS_AA@mail.gmail.com>

On Wed, Jan 11, 2017 at 06:25:59PM +0000, Matthew Auld wrote:
> On 20 December 2016 at 13:08, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> > +       for_each_set_bit(offset, valid, FW_RANGE) {
> > +               i915_reg_t reg = { offset };
> > +
> > +               intel_uncore_forcewake_reset(dev_priv, false);
> > +               check_for_unclaimed_mmio(dev_priv);
> hmm, what do we need this for ?

It clears the debug register before every test - so that we know the
only thing the debug register is complaining about is the I915_READ()
sandwiched in between. The reset is there to ensure that the fw is
turned off and the timer disabled, so that we have a vanilla state
every time with the powerwell off. Hopefully.
 
> > +
> > +               (void)I915_READ(reg);
> > +               if (check_for_unclaimed_mmio(dev_priv)) {

-- 
Chris Wilson, Intel Open Source Technology Centre
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2017-01-11 18:39 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-20 13:07 [RFCv2 01/19] drm/i915: Provide a hook for selftests Chris Wilson
2016-12-20 13:07 ` [RFCv2 02/19] kselftests: Exercise hw-independent mock tests for i915.ko Chris Wilson
2016-12-20 13:07 ` [RFCv2 03/19] drm/i915: Add some selftests for sg_table manipulation Chris Wilson
2016-12-20 13:07 ` [RFCv2 04/19] drm/i915: Add unit tests for the breadcrumb rbtree, insert/remove Chris Wilson
2016-12-20 13:08 ` [RFCv2 05/19] drm/i915: Add unit tests for the breadcrumb rbtree, completion Chris Wilson
2016-12-20 13:08 ` [RFCv2 06/19] drm/i915: Add unit tests for the breadcrumb rbtree, wakeups Chris Wilson
2016-12-20 13:08 ` [RFCv2 07/19] drm/i915: Mock the GEM device for self-testing Chris Wilson
2017-01-09 15:10   ` Matthew Auld
2016-12-20 13:08 ` [RFCv2 08/19] drm/i915: Mock a GGTT " Chris Wilson
2017-01-09 15:16   ` Matthew Auld
2017-01-10 12:33     ` Chris Wilson
2016-12-20 13:08 ` [RFCv2 09/19] drm/i915: Mock infrastructure for request emission Chris Wilson
2016-12-20 13:08 ` [RFCv2 10/19] drm/i915: Add selftests for i915_gem_request Chris Wilson
2016-12-20 13:08 ` [RFCv2 11/19] drm/i915: Add a simple request selftest for waiting Chris Wilson
2016-12-20 13:08 ` [RFCv2 12/19] drm/i915: Add a simple fence selftest to i915_gem_request Chris Wilson
2016-12-20 13:08 ` [RFCv2 13/19] drm/i915: Add selftests for object allocation, phys Chris Wilson
2016-12-20 13:08 ` [RFCv2 14/19] drm/i915: Move uncore selfchecks to live selftest infrastructure Chris Wilson
2017-01-11 18:21   ` Matthew Auld
2016-12-20 13:08 ` [RFCv2 15/19] drm/i915: Test all fw tables during mock selftests Chris Wilson
2017-01-11 18:22   ` Matthew Auld
2016-12-20 13:08 ` [RFCv2 16/19] drm/i915: Sanity check all registers for matching fw domains Chris Wilson
2017-01-11 18:25   ` Matthew Auld
2017-01-11 18:39     ` Chris Wilson [this message]
2017-01-11 19:08   ` Matthew Auld
2016-12-20 13:08 ` [RFCv2 17/19] drm/i915: Add some mock tests for dmabuf interop Chris Wilson
2017-01-10 19:12   ` Matthew Auld
2016-12-20 13:08 ` [RFCv2 18/19] drm/i915: Add initial selftests for i915_gem_gtt Chris Wilson
2017-01-10 19:32   ` Matthew Auld
2016-12-20 13:08 ` [RFCv2 19/19] drm/i915: Initial selftests for exercising eviction Chris Wilson
2017-01-10 19:49   ` Matthew Auld
2016-12-20 14:16 ` ✓ Fi.CI.BAT: success for series starting with [RFCv2,01/19] drm/i915: Provide a hook for selftests Patchwork
2017-01-11 18:17 ` [RFCv2 01/19] " Tvrtko Ursulin
2017-01-11 18:34   ` Chris Wilson

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=20170111183908.GF16278@nuc-i3427.alporthouse.com \
    --to=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=matthew.william.auld@gmail.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.