From: John.C.Harrison@Intel.com
To: IGT-Dev@Lists.FreeDesktop.Org
Cc: Intel-GFX@Lists.FreeDesktop.Org
Subject: [Intel-gfx] [PATCH v5 i-g-t 0/3] Update DRM UAPI and add test for new hw info query
Date: Fri, 3 Jun 2022 09:25:49 -0700 [thread overview]
Message-ID: <20220603162552.2254187-1-John.C.Harrison@Intel.com> (raw)
From: John Harrison <John.C.Harrison@Intel.com>
Various UMDs require hardware configuration information about the
current platform. A new interface has been added to the KMD to return
this information. So, add a test for the new interface.
Also, update to the latest DRM UAPI header file that contains the new
query enums.
Lastly, none of the query tests had description entries. So made some
up.
v2: Rebased to newer baseline.
v3: Update UAPI header file.
v4: Use correct method for updating header file.
v5: Add descriptions to all the query tests.
Signed-off-by: John Harrison <John.C.Harrison@Intel.com>
John Harrison (2):
include/drm-uapi: Update to latest i915_drm.h
tests/i915/query: Add descriptions to existing tests
Rodrigo Vivi (1):
tests/i915/query: Query, parse and validate the hwconfig table
include/drm-uapi/i915_drm.h | 398 ++++++++++++++++++++++++++++--------
lib/intel_hwconfig_types.h | 118 +++++++++++
tests/i915/i915_query.c | 192 +++++++++++++++++
3 files changed, 622 insertions(+), 86 deletions(-)
create mode 100644 lib/intel_hwconfig_types.h
--
2.36.0
next reply other threads:[~2022-06-03 16:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-03 16:25 John.C.Harrison [this message]
2022-06-03 16:25 ` [Intel-gfx] [PATCH v5 i-g-t 1/3] include/drm-uapi: Update to latest i915_drm.h John.C.Harrison
2022-06-03 16:25 ` [Intel-gfx] [PATCH v5 i-g-t 2/3] tests/i915/query: Add descriptions to existing tests John.C.Harrison
2022-06-06 8:06 ` [Intel-gfx] [igt-dev] " Kamil Konieczny
2022-06-06 8:09 ` [Intel-gfx] " Petri Latvala
2022-06-03 16:25 ` [Intel-gfx] [PATCH v5 i-g-t 3/3] tests/i915/query: Query, parse and validate the hwconfig table John.C.Harrison
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=20220603162552.2254187-1-John.C.Harrison@Intel.com \
--to=john.c.harrison@intel.com \
--cc=IGT-Dev@Lists.FreeDesktop.Org \
--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;
as well as URLs for NNTP newsgroup(s).