From: Badal Nilawar <badal.nilawar@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: anshuman.gupta@intel.com, rodrigo.vivi@intel.com,
alexander.usyskin@intel.com, michael.j.ruhl@intel.com,
daniele.ceraolospurio@intel.com
Subject: [RFC PATCH 0/4] Add ocode late binding support for CRI
Date: Thu, 5 Mar 2026 16:14:41 +0530 [thread overview]
Message-ID: <20260305104441.2857181-6-badal.nilawar@intel.com> (raw)
Ocode is the OOBMSM telemetry/manageability firmware, and on CRI it is
loaded through late binding flow.
Dependancy: There is dependancy on mei side of patches to support ocode late binding,
which are not upstreamed yet. Hence, this patch is marked as RFC.
Badal Nilawar (4):
drm/xe/xe_late_bind_fw: Refactor pm flow
drm/xe/xe_late_bind_fw: Add support to load Ocode firmware on CRI
drm/xe/xe_late_bind_fw: Track firmware load status
drm/xe/xe_late_bind_fw: Enable late binding support for CRI
drivers/gpu/drm/xe/xe_late_bind_fw.c | 143 ++++++++++++++++++---
drivers/gpu/drm/xe/xe_late_bind_fw.h | 7 +-
drivers/gpu/drm/xe/xe_late_bind_fw_types.h | 25 ++++
drivers/gpu/drm/xe/xe_pci.c | 1 +
drivers/gpu/drm/xe/xe_pm.c | 9 +-
5 files changed, 161 insertions(+), 24 deletions(-)
--
2.52.0
next reply other threads:[~2026-03-05 10:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-05 10:44 Badal Nilawar [this message]
2026-03-05 10:44 ` [RFC PATCH 1/4] drm/xe/xe_late_bind_fw: Refactor pm flow Badal Nilawar
2026-03-05 14:20 ` Rodrigo Vivi
2026-03-05 10:44 ` [RFC PATCH 2/4] drm/xe/xe_late_bind_fw: Add support to load Ocode firmware on CRI Badal Nilawar
2026-03-05 23:38 ` Daniele Ceraolo Spurio
2026-03-05 10:44 ` [RFC PATCH 3/4] drm/xe/xe_late_bind_fw: Track firmware load status Badal Nilawar
2026-03-05 23:52 ` Daniele Ceraolo Spurio
2026-03-05 10:44 ` [RFC PATCH 4/4] drm/xe/xe_late_bind_fw: Enable late binding support for CRI Badal Nilawar
2026-03-06 11:26 ` ✗ CI.KUnit: failure for Add ocode " 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=20260305104441.2857181-6-badal.nilawar@intel.com \
--to=badal.nilawar@intel.com \
--cc=alexander.usyskin@intel.com \
--cc=anshuman.gupta@intel.com \
--cc=daniele.ceraolospurio@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=michael.j.ruhl@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