From: Jordan Justen <jordan.l.justen@intel.com>
To: intel-gfx <intel-gfx@lists.freedesktop.org>
Cc: dri-devel <dri-devel@lists.freedesktop.org>
Subject: [Intel-gfx] [PATCH 0/4] GuC HWCONFIG with documentation
Date: Mon, 7 Feb 2022 11:28:50 -0800 [thread overview]
Message-ID: <20220207192854.862959-1-jordan.l.justen@intel.com> (raw)
This is John/Rodrigo's 2 patches with some minor changes, and I added
2 patches.
"drm/i915/uapi: Add query for hwconfig blob" was changed:
* Rename DRM_I915_QUERY_HWCONFIG_TABLE to DRM_I915_QUERY_HWCONFIG_BLOB
as requested by Joonas.
* Reword commit message
* I added Acked-by to this patch, but this only applies in the
context of this version of the patchset. If my changes are
rejected, then please *do not* add my Acked-by to the other series.
In particular, I do not want my Acked-by on the patch if the patch
mentions the HWCONFIG format, but is not willing to add that to the
actual uAPI.
I also do not want my Acked-by on it if it mentions "consolidation"
of this data. Since we are dealing with open source projects (aside
from GuC), this doesn't seem appropriate.
"drm/i915/uapi: Add struct drm_i915_query_hwconfig_blob_item" adds a
struct to the uAPI and documents the return value for
DRM_I915_QUERY_HWCONFIG_BLOB. (Except, keys / values are still
deferred to the PRM.)
"drm/i915/guc: Verify hwconfig blob matches supported format" does the
simple verification of the blob to make sure it matches what the uAPI
documents.
John Harrison (1):
drm/i915/guc: Add fetch of hwconfig table
Jordan Justen (2):
drm/i915/uapi: Add struct drm_i915_query_hwconfig_blob_item
drm/i915/guc: Verify hwconfig blob matches supported format
Rodrigo Vivi (1):
drm/i915/uapi: Add query for hwconfig blob
drivers/gpu/drm/i915/Makefile | 1 +
.../gpu/drm/i915/gt/uc/abi/guc_actions_abi.h | 1 +
.../gpu/drm/i915/gt/uc/abi/guc_errors_abi.h | 4 +
drivers/gpu/drm/i915/gt/uc/intel_guc.h | 3 +
.../gpu/drm/i915/gt/uc/intel_guc_hwconfig.c | 177 ++++++++++++++++++
.../gpu/drm/i915/gt/uc/intel_guc_hwconfig.h | 19 ++
drivers/gpu/drm/i915/gt/uc/intel_uc.c | 6 +
drivers/gpu/drm/i915/i915_query.c | 23 +++
include/uapi/drm/i915_drm.h | 25 +++
9 files changed, 259 insertions(+)
create mode 100644 drivers/gpu/drm/i915/gt/uc/intel_guc_hwconfig.c
create mode 100644 drivers/gpu/drm/i915/gt/uc/intel_guc_hwconfig.h
--
2.34.1
next reply other threads:[~2022-02-07 19:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-07 19:28 Jordan Justen [this message]
2022-02-07 19:28 ` [Intel-gfx] [PATCH 1/4] drm/i915/guc: Add fetch of hwconfig table Jordan Justen
2022-02-07 19:28 ` [Intel-gfx] [PATCH 2/4] drm/i915/uapi: Add query for hwconfig blob Jordan Justen
2022-02-07 19:28 ` [Intel-gfx] [PATCH 3/4] drm/i915/uapi: Add struct drm_i915_query_hwconfig_blob_item Jordan Justen
2022-02-08 0:07 ` kernel test robot
2022-02-08 9:19 ` Tvrtko Ursulin
2022-02-07 19:28 ` [Intel-gfx] [PATCH 4/4] drm/i915/guc: Verify hwconfig blob matches supported format Jordan Justen
2022-02-07 22:45 ` kernel test robot
2022-02-07 22:45 ` kernel test robot
2022-02-07 23:36 ` kernel test robot
2022-02-08 9:36 ` Tvrtko Ursulin
2022-02-08 22:45 ` Jordan Justen
2022-02-07 19:59 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for GuC HWCONFIG with documentation 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=20220207192854.862959-1-jordan.l.justen@intel.com \
--to=jordan.l.justen@intel.com \
--cc=dri-devel@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