From: "Ceraolo Spurio, Daniele" <daniele.ceraolospurio@intel.com>
To: Zhanjun Dong <zhanjun.dong@intel.com>, <intel-xe@lists.freedesktop.org>
Subject: Re: [Intel-xe] [PATCH] drm/xe: Add patch version on guc firmware init
Date: Fri, 18 Aug 2023 11:45:10 -0700 [thread overview]
Message-ID: <25e0f9e9-a46d-6556-e27f-2a528248f944@intel.com> (raw)
In-Reply-To: <20230817213028.838531-1-zhanjun.dong@intel.com>
On 8/17/2023 2:30 PM, Zhanjun Dong wrote:
> 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>
Reviewed-by: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
Daniele
> ---
> drivers/gpu/drm/xe/xe_uc_fw.c | 13 +++++++------
> drivers/gpu/drm/xe/xe_uc_fw_types.h | 2 ++
> 2 files changed, 9 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_uc_fw.c b/drivers/gpu/drm/xe/xe_uc_fw.c
> index 6c95a3e4c3f2..2111b3ef4975 100644
> --- a/drivers/gpu/drm/xe/xe_uc_fw.c
> +++ b/drivers/gpu/drm/xe/xe_uc_fw.c
> @@ -403,11 +403,12 @@ 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",
> - xe_uc_fw_type_repr(uc_fw->type),
> - uc_fw->major_ver_found, uc_fw->minor_ver_found,
> - uc_fw->path);
> + drm_info(&xe->drm, "Using %s firmware from %s version %u.%u.%u\n",
> + xe_uc_fw_type_repr(uc_fw->type), 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)
> @@ -540,9 +541,9 @@ void xe_uc_fw_print(struct xe_uc_fw *uc_fw, struct drm_printer *p)
> xe_uc_fw_type_repr(uc_fw->type), uc_fw->path);
> drm_printf(p, "\tstatus: %s\n",
> xe_uc_fw_status_repr(uc_fw->status));
> - drm_printf(p, "\tversion: wanted %u.%u, found %u.%u\n",
> + drm_printf(p, "\tversion: wanted %u.%u, found %u.%u.%u\n",
> uc_fw->major_ver_wanted, uc_fw->minor_ver_wanted,
> - uc_fw->major_ver_found, uc_fw->minor_ver_found);
> + uc_fw->major_ver_found, uc_fw->minor_ver_found, uc_fw->patch_ver_found);
> drm_printf(p, "\tuCode: %u bytes\n", uc_fw->ucode_size);
> drm_printf(p, "\tRSA: %u bytes\n", uc_fw->rsa_size);
>
> 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;
next prev parent reply other threads:[~2023-08-18 18:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-17 21:30 [Intel-xe] [PATCH] drm/xe: Add patch version on guc firmware init Zhanjun Dong
2023-08-17 21:32 ` [Intel-xe] ✓ CI.Patch_applied: success for drm/xe: Add patch version on guc firmware init (rev2) Patchwork
2023-08-17 21:32 ` [Intel-xe] ✗ CI.checkpatch: warning " Patchwork
2023-08-17 21:33 ` [Intel-xe] ✓ CI.KUnit: success " Patchwork
2023-08-17 21:37 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-08-17 21:38 ` [Intel-xe] ✓ CI.Hooks: " Patchwork
2023-08-17 21:38 ` [Intel-xe] ✗ CI.checksparse: warning " Patchwork
2023-08-17 22:05 ` [Intel-xe] ✓ CI.BAT: success " Patchwork
2023-08-18 18:45 ` Ceraolo Spurio, Daniele [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-15 23:56 [Intel-xe] [PATCH] drm/xe: Add patch version on guc firmware init Zhanjun Dong
2023-08-16 20:46 ` Ceraolo Spurio, Daniele
2023-08-17 0:48 ` Dong, Zhanjun
2023-08-17 18:21 ` 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=25e0f9e9-a46d-6556-e27f-2a528248f944@intel.com \
--to=daniele.ceraolospurio@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=zhanjun.dong@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox