From: Michel Thierry <michel.thierry@intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: [PATCH 2/3] drm/i915: Include GuC fw version in error state
Date: Fri, 24 Feb 2017 11:05:29 -0800 [thread overview]
Message-ID: <20170224190530.31482-2-michel.thierry@intel.com> (raw)
In-Reply-To: <20170224190530.31482-1-michel.thierry@intel.com>
There was no way to check if the platform is running the latest
firmware.
v2: use HAS_GUC and intel_guc* (Michal)
capture before reset (Chris)
Cc: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Michal Wajdeczko <michal.wajdeczko@intel.com>
Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Cc: Arkadiusz Hiler <arkadiusz.hiler@intel.com>
Signed-off-by: Michel Thierry <michel.thierry@intel.com>
---
drivers/gpu/drm/i915/i915_drv.h | 2 ++
drivers/gpu/drm/i915/i915_gpu_error.c | 17 +++++++++++++++++
2 files changed, 19 insertions(+)
diff --git a/drivers/gpu/drm/i915/i915_drv.h b/drivers/gpu/drm/i915/i915_drv.h
index 3b0cff05f5f7..a331c00523bc 100644
--- a/drivers/gpu/drm/i915/i915_drv.h
+++ b/drivers/gpu/drm/i915/i915_drv.h
@@ -956,6 +956,8 @@ struct i915_gpu_state {
/* Firmware load state */
u32 dmc_loaded;
u32 dmc_version;
+ u32 guc_loaded;
+ u32 guc_version;
u32 nfence;
u64 fence[I915_MAX_NUM_FENCES];
diff --git a/drivers/gpu/drm/i915/i915_gpu_error.c b/drivers/gpu/drm/i915/i915_gpu_error.c
index ae6f0092b046..63f1b9606b57 100644
--- a/drivers/gpu/drm/i915/i915_gpu_error.c
+++ b/drivers/gpu/drm/i915/i915_gpu_error.c
@@ -629,6 +629,13 @@ int i915_error_state_to_str(struct drm_i915_error_state_buf *m,
CSR_VERSION_MINOR(error->dmc_version));
}
+ if (HAS_GUC(dev_priv)) {
+ err_printf(m, "GuC loaded: %s\n", yesno(error->guc_loaded));
+ err_printf(m, "GuC fw version: %d.%d\n",
+ error->guc_version >> 16,
+ error->guc_version & 0xffff);
+ }
+
err_printf(m, "EIR: 0x%08x\n", error->eir);
err_printf(m, "IER: 0x%08x\n", error->ier);
for (i = 0; i < error->ngtier; i++)
@@ -1592,6 +1599,16 @@ static void i915_capture_fw_state(struct drm_i915_private *dev_priv,
error->dmc_loaded = (csr->dmc_payload != NULL);
error->dmc_version = csr->version;
}
+
+ if (HAS_GUC(dev_priv)) {
+ struct intel_guc *guc = &dev_priv->guc;
+
+ error->guc_loaded =
+ (guc->fw.load_status == INTEL_UC_FIRMWARE_SUCCESS);
+ error->guc_version =
+ (guc->fw.major_ver_found << 16 |
+ guc->fw.minor_ver_found);
+ }
}
static void i915_error_capture_msg(struct drm_i915_private *dev_priv,
--
2.11.0
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-02-24 19:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-24 19:05 [PATCH 1/3] drm/i915: Capture dmc firmware information before reset Michel Thierry
2017-02-24 19:05 ` Michel Thierry [this message]
2017-02-24 19:24 ` [PATCH 2/3] drm/i915: Include GuC fw version in error state Michal Wajdeczko
2017-02-24 19:05 ` [PATCH 3/3] drm/i915: Include HuC " Michel Thierry
2017-02-24 19:24 ` Chris Wilson
2017-02-24 19:26 ` Michal Wajdeczko
2017-02-24 19:15 ` [PATCH 1/3] drm/i915: Capture dmc firmware information before reset Michal Wajdeczko
2017-02-24 19:22 ` Chris Wilson
2017-02-24 19:25 ` Michel Thierry
2017-02-24 19:34 ` Chris Wilson
2017-02-24 19:38 ` Michel Thierry
2017-02-24 19:52 ` ✓ Fi.CI.BAT: success for series starting with [1/3] " 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=20170224190530.31482-2-michel.thierry@intel.com \
--to=michel.thierry@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