From: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
To: "Anoop, Vijay" <anoop.c.vijay@intel.com>
Cc: <intel-xe@lists.freedesktop.org>, <badal.nilawar@intel.com>,
<rodrigo.vivi@intel.com>, <aravind.iddamsetty@intel.com>,
<riana.tauro@intel.com>, <anshuman.gupta@intel.com>,
<matthew.d.roper@intel.com>, <michael.j.ruhl@intel.com>,
<paul.e.luse@intel.com>, <mohamed.mansoor.v@intel.com>,
<kam.nasim@intel.com>
Subject: Re: [PATCH v8 2/2] drm/xe/sysctrl: Add helper to check oCode firmware readiness
Date: Fri, 4 Sep 2026 11:18:53 -0700 [thread overview]
Message-ID: <apsLjZcZ5zl89jTo@soc-5CG1426VCC.clients.intel.com> (raw)
In-Reply-To: <20260904134935.674507-6-anoop.c.vijay@intel.com>
On Fri, Sep 04, 2026 at 06:49:37AM -0700, Anoop, Vijay wrote:
>From: Anoop Vijay <anoop.c.vijay@intel.com>
>
>Add xe_sysctrl_is_oobmsm_fw_ready(), a convenience wrapper around
>xe_sysctrl_check_app_status() to check oCode application readiness.
>
>Signed-off-by: Anoop Vijay <anoop.c.vijay@intel.com>
LGTM,
Reviewed-by: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
>---
>v6:
>- New patch — split oCode application readiness helper out of the
> original patch into its own commit
>
>v7: (Umesh)
>- Clarify xe_sysctrl_is_oobmsm_fw_ready() comment for sysctrl-less platforms
>- Add XE_SYSCTRL_APP_OCODE to enum xe_sysctrl_app_id in xe_sysctrl.c
>
>v8: (Umesh, Rodrigo, Mike)
>- Simplify oCode readiness helpers to a single
> XE_SYSCTRL_FIRMWARE_APP_INITIALIZED check
>---
> drivers/gpu/drm/xe/xe_sysctrl.c | 19 +++++++++++++++++++
> drivers/gpu/drm/xe/xe_sysctrl.h | 1 +
> 2 files changed, 20 insertions(+)
>
>diff --git a/drivers/gpu/drm/xe/xe_sysctrl.c b/drivers/gpu/drm/xe/xe_sysctrl.c
>index 3b7fa2c9c333..4067e1dfdcd5 100644
>--- a/drivers/gpu/drm/xe/xe_sysctrl.c
>+++ b/drivers/gpu/drm/xe/xe_sysctrl.c
>@@ -42,6 +42,7 @@
> * application ID.
> */
> enum xe_sysctrl_app_id {
>+ XE_SYSCTRL_APP_OCODE = 0x0C,
> XE_SYSCTRL_APP_DIAG = 0x0D,
> };
>
>@@ -181,6 +182,24 @@ xe_sysctrl_check_app_status(struct xe_device *xe, enum xe_sysctrl_app_id app_id)
> return XE_SYSCTRL_FIRMWARE_APP_INITIALIZED;
> }
>
>+/**
>+ * xe_sysctrl_is_oobmsm_fw_ready() - Check if oCode firmware is fully initialized
>+ * @xe: xe device instance
>+ *
>+ * Returns true if oCode firmware has reached the initialized state, indicating
>+ * it is ready to handle requests.
>+ *
>+ * Callers must only invoke this on platforms where System Controller is
>+ * present (xe->info.has_sysctrl).
>+ *
>+ * Return: true if oCode firmware is initialized, false otherwise
>+ */
>+bool xe_sysctrl_is_oobmsm_fw_ready(struct xe_device *xe)
>+{
>+ return xe_sysctrl_check_app_status(xe, XE_SYSCTRL_APP_OCODE) ==
>+ XE_SYSCTRL_FIRMWARE_APP_INITIALIZED;
>+}
>+
> /**
> * xe_sysctrl_is_diag_fw_ready() - Check if diag firmware is fully initialized
> * @xe: xe device instance
>diff --git a/drivers/gpu/drm/xe/xe_sysctrl.h b/drivers/gpu/drm/xe/xe_sysctrl.h
>index 8dc576796890..b69a3f474236 100644
>--- a/drivers/gpu/drm/xe/xe_sysctrl.h
>+++ b/drivers/gpu/drm/xe/xe_sysctrl.h
>@@ -20,6 +20,7 @@ void xe_sysctrl_event(struct xe_sysctrl *sc);
> int xe_sysctrl_init(struct xe_device *xe);
> void xe_sysctrl_irq_handler(struct xe_device *xe, u32 master_ctl);
> void xe_sysctrl_pm_resume(struct xe_device *xe);
>+bool xe_sysctrl_is_oobmsm_fw_ready(struct xe_device *xe);
> bool xe_sysctrl_is_diag_fw_ready(struct xe_device *xe);
>
> #endif
>--
>2.43.0
>
next prev parent reply other threads:[~2026-09-04 18:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-04 13:49 [PATCH v8 0/2] drm/xe/sysctrl: Add helper to query application status Anoop, Vijay
2026-09-04 13:49 ` [PATCH v8 1/2] " Anoop, Vijay
2026-09-04 15:19 ` Ruhl, Michael J
2026-09-04 18:13 ` Umesh Nerlige Ramappa
2026-09-04 18:18 ` Umesh Nerlige Ramappa
2026-09-04 13:49 ` [PATCH v8 2/2] drm/xe/sysctrl: Add helper to check oCode firmware readiness Anoop, Vijay
2026-09-04 15:19 ` Ruhl, Michael J
2026-09-04 18:18 ` Umesh Nerlige Ramappa [this message]
2026-09-04 13:57 ` ✓ CI.KUnit: success for drm/xe/sysctrl: Add helper to query application status (rev8) Patchwork
2026-09-04 14:49 ` ✓ Xe.CI.BAT: " Patchwork
2026-09-05 0:17 ` ✓ Xe.CI.FULL: " 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=apsLjZcZ5zl89jTo@soc-5CG1426VCC.clients.intel.com \
--to=umesh.nerlige.ramappa@intel.com \
--cc=anoop.c.vijay@intel.com \
--cc=anshuman.gupta@intel.com \
--cc=aravind.iddamsetty@intel.com \
--cc=badal.nilawar@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=kam.nasim@intel.com \
--cc=matthew.d.roper@intel.com \
--cc=michael.j.ruhl@intel.com \
--cc=mohamed.mansoor.v@intel.com \
--cc=paul.e.luse@intel.com \
--cc=riana.tauro@intel.com \
--cc=rodrigo.vivi@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