All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Badal Nilawar <badal.nilawar@intel.com>
Cc: <intel-xe@lists.freedesktop.org>, <anshuman.gupta@intel.com>,
	<alexander.usyskin@intel.com>, <michael.j.ruhl@intel.com>,
	<daniele.ceraolospurio@intel.com>, <anoop.c.vijay@intel.com>,
	<shamim.begum@intel.com>, <anthony.giardina@intel.com>
Subject: Re: [PATCH v4 0/5] Add ocode late binding support for CRI
Date: Thu, 23 Jul 2026 12:46:55 -0400	[thread overview]
Message-ID: <amJFf3dmdNGxuWv2@intel.com> (raw)
In-Reply-To: <20260723083659.716683-7-badal.nilawar@intel.com>

On Thu, Jul 23, 2026 at 02:07:00PM +0530, Badal Nilawar wrote:
> Ocode is the OOBMSM telemetry/manageability firmware, and on CRI it is
> loaded through late binding flow.
> 
> v2: Dropped "[RFC,3/4] drm/xe/xe_late_bind_fw: Track firmware load status"
> 
> v4:
>   - Fixed most of the comments from Daniele
>   - Rearranged the patches
>   - Introduced new patch to fix firmware leak
>   - Improved "TODO: compatibility check" comments

Please check and fix:
https://sashiko.dev/#/patchset/20260723083659.716683-7-badal.nilawar%40intel.com

> 
> Badal Nilawar (5):
>   drm/xe/xe_late_bind_fw: Fix firmware leak on missing manifest entry
>   drm/xe/xe_late_bind_fw: Convert late bind flag to mask
>   drm/xe/xe_late_bind_fw: Add support to load Ocode firmware
>   drm/xe/xe_late_bind_fw: Enable late binding support for CRI
>   drm/xe/xe_late_bind_fw: Refactor pm flow
> 
>  drivers/gpu/drm/xe/xe_device.c             |   2 +-
>  drivers/gpu/drm/xe/xe_device_types.h       |   4 +-
>  drivers/gpu/drm/xe/xe_late_bind_fw.c       | 118 ++++++++++++++++-----
>  drivers/gpu/drm/xe/xe_late_bind_fw.h       |   4 +-
>  drivers/gpu/drm/xe/xe_late_bind_fw_types.h |   4 +-
>  drivers/gpu/drm/xe/xe_pci.c                |   6 +-
>  drivers/gpu/drm/xe/xe_pci_types.h          |   2 +-
>  drivers/gpu/drm/xe/xe_pm.c                 |   6 +-
>  8 files changed, 106 insertions(+), 40 deletions(-)
> 
> -- 
> 2.54.0
> 

      parent reply	other threads:[~2026-07-23 16:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-23  8:37 [PATCH v4 0/5] Add ocode late binding support for CRI Badal Nilawar
2026-07-23  8:33 ` ✗ CI.checkpatch: warning for Add ocode late binding support for CRI (rev4) Patchwork
2026-07-23  8:35 ` ✓ CI.KUnit: success " Patchwork
2026-07-23  8:37 ` [PATCH v4 1/5] drm/xe/xe_late_bind_fw: Fix firmware leak on missing manifest entry Badal Nilawar
2026-07-23  8:37 ` [PATCH v4 2/5] drm/xe/xe_late_bind_fw: Convert late bind flag to mask Badal Nilawar
2026-07-23  8:37 ` [PATCH v4 3/5] drm/xe/xe_late_bind_fw: Add support to load Ocode firmware Badal Nilawar
2026-07-23  8:37 ` [PATCH v4 4/5] drm/xe/xe_late_bind_fw: Enable late binding support for CRI Badal Nilawar
2026-07-23  8:37 ` [PATCH v4 5/5] drm/xe/xe_late_bind_fw: Refactor pm flow Badal Nilawar
2026-07-23  9:19 ` ✓ Xe.CI.BAT: success for Add ocode late binding support for CRI (rev4) Patchwork
2026-07-23 16:46 ` Rodrigo Vivi [this message]

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=amJFf3dmdNGxuWv2@intel.com \
    --to=rodrigo.vivi@intel.com \
    --cc=alexander.usyskin@intel.com \
    --cc=anoop.c.vijay@intel.com \
    --cc=anshuman.gupta@intel.com \
    --cc=anthony.giardina@intel.com \
    --cc=badal.nilawar@intel.com \
    --cc=daniele.ceraolospurio@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=michael.j.ruhl@intel.com \
    --cc=shamim.begum@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.