From: Zhanjun Dong <zhanjun.dong@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: Zhanjun Dong <zhanjun.dong@intel.com>
Subject: [Intel-xe] [PATCH] drm/xe: Add patch version on guc firmware init
Date: Tue, 15 Aug 2023 16:56:06 -0700 [thread overview]
Message-ID: <20230815235606.804366-1-zhanjun.dong@intel.com> (raw)
Add patch version info on GuC firmware init. This is required info for
GuC log decoder.
Signed-off-by: Zhanjun Dong <zhanjun.dong@intel.com>
---
drivers/gpu/drm/xe/xe_uc_fw.c | 7 +++++--
drivers/gpu/drm/xe/xe_uc_fw_types.h | 2 ++
2 files changed, 7 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/xe/xe_uc_fw.c b/drivers/gpu/drm/xe/xe_uc_fw.c
index 6c95a3e4c3f2..408b816f9e40 100644
--- a/drivers/gpu/drm/xe/xe_uc_fw.c
+++ b/drivers/gpu/drm/xe/xe_uc_fw.c
@@ -403,11 +403,14 @@ int xe_uc_fw_init(struct xe_uc_fw *uc_fw)
css->sw_version);
uc_fw->minor_ver_found = FIELD_GET(CSS_SW_VERSION_UC_MINOR,
css->sw_version);
+ uc_fw->patch_ver_found = FIELD_GET(CSS_SW_VERSION_UC_PATCH,
+ css->sw_version);
- drm_info(&xe->drm, "Using %s firmware (%u.%u) from %s\n",
+ drm_info(&xe->drm, "Using %s firmware (%u.%u) from %s version %u.%u.%u\n",
xe_uc_fw_type_repr(uc_fw->type),
uc_fw->major_ver_found, uc_fw->minor_ver_found,
- uc_fw->path);
+ uc_fw->path,
+ uc_fw->major_ver_found, uc_fw->minor_ver_found, uc_fw->patch_ver_found);
err = uc_fw_check_version_requirements(uc_fw);
if (err)
diff --git a/drivers/gpu/drm/xe/xe_uc_fw_types.h b/drivers/gpu/drm/xe/xe_uc_fw_types.h
index 837f49a2347e..444bff83cdbe 100644
--- a/drivers/gpu/drm/xe/xe_uc_fw_types.h
+++ b/drivers/gpu/drm/xe/xe_uc_fw_types.h
@@ -106,6 +106,8 @@ struct xe_uc_fw {
u16 major_ver_found;
/** @minor_ver_found: major version found in firmware blob */
u16 minor_ver_found;
+ /** @patch_ver_found: patch version found in firmware blob */
+ u16 patch_ver_found;
/** @rsa_size: RSA size */
u32 rsa_size;
--
2.34.1
next reply other threads:[~2023-08-15 23:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-15 23:56 Zhanjun Dong [this message]
2023-08-15 23:58 ` [Intel-xe] ✓ CI.Patch_applied: success for drm/xe: Add patch version on guc firmware init Patchwork
2023-08-15 23:58 ` [Intel-xe] ✗ CI.checkpatch: warning " Patchwork
2023-08-15 23:59 ` [Intel-xe] ✓ CI.KUnit: success " Patchwork
2023-08-16 0:03 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-08-16 0:04 ` [Intel-xe] ✓ CI.Hooks: " Patchwork
2023-08-16 0:04 ` [Intel-xe] ✗ CI.checksparse: warning " Patchwork
2023-08-16 0:36 ` [Intel-xe] ✗ CI.BAT: failure " Patchwork
2023-08-16 20:46 ` [Intel-xe] [PATCH] " Ceraolo Spurio, Daniele
2023-08-17 0:48 ` Dong, Zhanjun
2023-08-17 18:21 ` Ceraolo Spurio, Daniele
-- strict thread matches above, loose matches on Subject: below --
2023-08-17 21:30 Zhanjun Dong
2023-08-18 18:45 ` Ceraolo Spurio, Daniele
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=20230815235606.804366-1-zhanjun.dong@intel.com \
--to=zhanjun.dong@intel.com \
--cc=intel-xe@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