From: John.C.Harrison@Intel.com
To: Intel-GFX@Lists.FreeDesktop.Org
Subject: [PATCH 0/2] Improve whitelist selftest for read-only registers
Date: Tue, 2 Jul 2019 19:06:02 -0700 [thread overview]
Message-ID: <20190703020604.20369-1-John.C.Harrison@Intel.com> (raw)
From: John Harrison <John.C.Harrison@Intel.com>
Follow up patch to earlier whitelist updates. This series adds some
extra sanity checking to the driver and improves the self-test.
John Harrison (2):
drm/i915: Add test for invalid flag bits in whitelist entries
drm/i915: Implement read-only support in whitelist selftest
drivers/gpu/drm/i915/gt/intel_workarounds.c | 29 ++++++++--
.../gpu/drm/i915/gt/selftest_workarounds.c | 57 +++++++++++++------
drivers/gpu/drm/i915/i915_reg.h | 12 +++-
3 files changed, 73 insertions(+), 25 deletions(-)
--
2.21.0.5.gaeb582a983
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2019-07-03 2:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-03 2:06 John.C.Harrison [this message]
2019-07-03 2:06 ` [PATCH 1/2] drm/i915: Add test for invalid flag bits in whitelist entries John.C.Harrison
2019-07-03 13:50 ` Tvrtko Ursulin
2019-07-03 2:06 ` [PATCH 2/2] drm/i915: Implement read-only support in whitelist selftest John.C.Harrison
2019-07-03 8:32 ` Chris Wilson
2019-07-03 19:43 ` John Harrison
2019-07-10 8:21 ` Tvrtko Ursulin
2019-07-04 10:10 ` Tvrtko Ursulin
2019-07-03 2:43 ` ✓ Fi.CI.BAT: success for Improve whitelist selftest for read-only registers Patchwork
2019-07-03 7:50 ` [PATCH 3/3] drm/i915: Add engine name to workaround debug print John.C.Harrison
2019-07-03 13:53 ` Tvrtko Ursulin
2019-07-03 9:36 ` ✓ Fi.CI.BAT: success for Improve whitelist selftest for read-only registers Patchwork
2019-07-03 23:48 ` ✓ Fi.CI.IGT: " Patchwork
2019-07-04 2:31 ` Patchwork
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=20190703020604.20369-1-John.C.Harrison@Intel.com \
--to=john.c.harrison@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox