From: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
To: Badal Nilawar <badal.nilawar@intel.com>,
<intel-xe@lists.freedesktop.org>
Cc: <anshuman.gupta@intel.com>, <rodrigo.vivi@intel.com>,
<alexander.usyskin@intel.com>, <michael.j.ruhl@intel.com>
Subject: Re: [PATCH v3 1/3] drm/xe/xe_late_bind_fw: Add support to load Ocode firmware
Date: Tue, 14 Jul 2026 16:24:50 -0700 [thread overview]
Message-ID: <31701a38-4cd9-4e9a-bb5a-2cce86bdd258@intel.com> (raw)
In-Reply-To: <39aab72f-e933-46d3-950d-f7575a7be156@intel.com>
<snip>
>> --- a/drivers/gpu/drm/xe/xe_late_bind_fw_types.h
>> +++ b/drivers/gpu/drm/xe/xe_late_bind_fw_types.h
>> @@ -21,6 +21,8 @@
>> enum xe_late_bind_fw_id {
>> /** @XE_LB_FW_FAN_CONTROL: Fan control */
>> XE_LB_FW_FAN_CONTROL = 0,
>> + /** @XE_LB_FW_OCODE: Ocode firmware */
>> + XE_LB_FW_OCODE,
>
> in the review of the RFC version of this patch, we agreed to modify
> has_late_bind to be a mask so that we could set FAN_CONTROL for BMG
> and OCODE for CRI. Is that still planned?
Never mind, just saw this is in the next patch. sorry for the noise.
>
> Daniele
>
>> /** @XE_LB_FW_MAX_ID: Number of IDs */
>> XE_LB_FW_MAX_ID
>> };
>
next prev parent reply other threads:[~2026-07-14 23:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-09 14:39 [PATCH v3 0/3] Add ocode late binding support for CRI Badal Nilawar
2026-07-09 14:35 ` ✓ CI.KUnit: success for Add ocode late binding support for CRI (rev3) Patchwork
2026-07-09 14:39 ` [PATCH v3 1/3] drm/xe/xe_late_bind_fw: Add support to load Ocode firmware Badal Nilawar
2026-07-14 23:23 ` Daniele Ceraolo Spurio
2026-07-14 23:24 ` Daniele Ceraolo Spurio [this message]
2026-07-09 14:39 ` [PATCH v3 2/3] drm/xe/xe_late_bind_fw: Enable late binding support for CRI Badal Nilawar
2026-07-14 23:35 ` Daniele Ceraolo Spurio
2026-07-09 14:39 ` [PATCH v3 3/3] drm/xe/xe_late_bind_fw: Refactor pm flow Badal Nilawar
2026-07-09 15:25 ` ✓ Xe.CI.BAT: success for Add ocode late binding support for CRI (rev3) Patchwork
2026-07-09 18:14 ` ✓ 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=31701a38-4cd9-4e9a-bb5a-2cce86bdd258@intel.com \
--to=daniele.ceraolospurio@intel.com \
--cc=alexander.usyskin@intel.com \
--cc=anshuman.gupta@intel.com \
--cc=badal.nilawar@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