Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Badal Nilawar" <badal.nilawar@intel.com>,
	intel-xe@lists.freedesktop.org
Subject: Re: [PATCH v6 2/6] drm/xe/xe_late_bind_fw: Add string mappings of status codes
Date: Fri, 30 Oct 2026 14:55:47 +0000	[thread overview]
Message-ID: <sashiko-outbox-191132@kernel.org> (raw)
In-Reply-To: <20261030144547.2532309-10-badal.nilawar@intel.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] drm/xe: missing BUFFER_TOO_SMALL mapping in xe_late_bind_parse_status()
--

commit d7b67485aab2684a93a389da87365dcc4bead83b
Author: Badal Nilawar <badal.nilawar@intel.com>

drm/xe/xe_late_bind_fw: Add string mappings of status codes

This commit adds string mappings in xe_late_bind_parse_status() for the new
late binding status codes introduced in the mei_lb driver.

> diff --git a/drivers/gpu/drm/xe/xe_late_bind_fw.c b/drivers/gpu/drm/xe/xe_late_bind_fw.c
> index 1bddfaf0fb9f0..b7957e255ccde 100644
> --- a/drivers/gpu/drm/xe/xe_late_bind_fw.c
> +++ b/drivers/gpu/drm/xe/xe_late_bind_fw.c
> @@ -179,6 +179,32 @@ static const char *xe_late_bind_parse_status(uint32_t status)
>  		return "Invalid Payload";
>  	case INTEL_LB_STATUS_TIMEOUT:
>  		return "Timeout";
> +	case INTEL_LB_STATUS_INTERNAL_ERROR:
> +		return "Internal Error";

[Severity: Medium]
Should INTEL_LB_STATUS_BUFFER_TOO_SMALL also be handled here in
xe_late_bind_parse_status()?

Commit 773a43b8627f ("mei: lb: add late binding version 2") added status
codes 8 through 21 to enum intel_lb_status in
include/drm/intel/intel_lb_mei_interface.h:

	INTEL_LB_STATUS_TIMEOUT                              = 7,
	INTEL_LB_STATUS_BUFFER_TOO_SMALL                     = 8,
	INTEL_LB_STATUS_INTERNAL_ERROR                       = 9,

Without a case for INTEL_LB_STATUS_BUFFER_TOO_SMALL, if
late_bind->component.ops->push_payload() returns status 8 to
xe_late_bind_work(), xe_late_bind_parse_status() will fall through to the
default case and report "Unknown error".

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261030144547.2532309-8-badal.nilawar@intel.com?part=2

  reply	other threads:[~2026-10-30 14:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-30 14:45 [PATCH v6 0/6] Add ocode late binding support for CRI Badal Nilawar
2026-10-30 14:45 ` [PATCH v6 1/6] drm/xe/xe_late_bind_fw: Fix firmware leak on missing manifest entry Badal Nilawar
2026-10-30 14:45 ` [PATCH v6 2/6] drm/xe/xe_late_bind_fw: Add string mappings of status codes Badal Nilawar
2026-10-30 14:55   ` sashiko-bot [this message]
2026-10-30 14:45 ` [PATCH v6 3/6] drm/xe/xe_late_bind_fw: Convert late bind flag to mask Badal Nilawar
2026-10-30 14:45 ` [PATCH v6 4/6] drm/xe/xe_late_bind_fw: Add support to load Ocode firmware Badal Nilawar
2026-10-30 14:45 ` [PATCH v6 5/6] drm/xe/xe_late_bind_fw: Enable late binding support for CRI Badal Nilawar
2026-10-30 14:59   ` sashiko-bot
2026-10-30 14:45 ` [PATCH v6 6/6] drm/xe/xe_late_bind_fw: Refactor pm flow Badal Nilawar

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=sashiko-outbox-191132@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=badal.nilawar@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /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