Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Piotr Piórkowski" <piotr.piorkowski@intel.com>
To: Michal Wajdeczko <michal.wajdeczko@intel.com>
Cc: <intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH 1/4] drm/xe/vf: Support only GuC/HuC firmwares
Date: Thu, 6 Jun 2024 13:29:16 +0200	[thread overview]
Message-ID: <20240606112916.5qsne74isbfkyypr@intel.com> (raw)
In-Reply-To: <20240604212231.1416-2-michal.wajdeczko@intel.com>

Michal Wajdeczko <michal.wajdeczko@intel.com> wrote on wto [2024-cze-04 23:22:28 +0200]:
> Only GuC/HuC firmwares can be used by the VFs, don't claim support
> for any other firmware (like GSC) even if the driver can support it.
> 
> Signed-off-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
> ---
>  drivers/gpu/drm/xe/xe_uc_fw.c | 4 ++++
>  1 file changed, 4 insertions(+)
> 
> diff --git a/drivers/gpu/drm/xe/xe_uc_fw.c b/drivers/gpu/drm/xe/xe_uc_fw.c
> index 12346645a8e5..a69c61f6b064 100644
> --- a/drivers/gpu/drm/xe/xe_uc_fw.c
> +++ b/drivers/gpu/drm/xe/xe_uc_fw.c
> @@ -657,6 +657,10 @@ static int uc_fw_request(struct xe_uc_fw *uc_fw, const struct firmware **firmwar
>  	uc_fw_auto_select(xe, uc_fw);
>  
>  	if (IS_SRIOV_VF(xe)) {
> +		/* Only GuC/HuC are supported */
> +		if (uc_fw->type != XE_UC_FW_TYPE_GUC &&
> +		    uc_fw->type != XE_UC_FW_TYPE_HUC)
> +			uc_fw->path = NULL;
>  		/* VF will support only firmwares that driver can autoselect */
>  		xe_uc_fw_change_status(uc_fw, uc_fw->path ?
>  				       XE_UC_FIRMWARE_PRELOADED :


LGTM:
Reviewed-by: Piotr Piórkowski <piotr.piorkowski@intel.com>

> -- 
> 2.43.0
> 

-- 

  reply	other threads:[~2024-06-06 11:29 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-04 21:22 [PATCH 0/4] VF: Custom init and reset steps Michal Wajdeczko
2024-06-04 21:22 ` [PATCH 1/4] drm/xe/vf: Support only GuC/HuC firmwares Michal Wajdeczko
2024-06-06 11:29   ` Piotr Piórkowski [this message]
2024-06-04 21:22 ` [PATCH 2/4] drm/xe/vf: Custom uC initialization Michal Wajdeczko
2024-06-06 11:37   ` Piotr Piórkowski
2024-06-06 13:34     ` Michal Wajdeczko
2024-06-04 21:22 ` [PATCH 3/4] drm/xe/vf: Custom GuC reset Michal Wajdeczko
2024-06-06 11:38   ` Piotr Piórkowski
2024-06-04 21:22 ` [PATCH 4/4] drm/xe/vf: Custom GT restart Michal Wajdeczko
2024-06-06 11:49   ` Piotr Piórkowski
2024-06-05  5:02 ` ✓ CI.Patch_applied: success for VF: Custom init and reset steps Patchwork
2024-06-05  5:02 ` ✓ CI.checkpatch: " Patchwork
2024-06-05  5:03 ` ✓ CI.KUnit: " Patchwork
2024-06-05  5:15 ` ✓ CI.Build: " Patchwork
2024-06-05  5:15 ` ✗ CI.Hooks: failure " Patchwork
2024-06-05  5:17 ` ✓ CI.checksparse: success " Patchwork
2024-06-05  5:44 ` ✓ CI.BAT: " Patchwork
2024-06-05 15:36 ` ✗ CI.FULL: failure " Patchwork
2024-06-06 13:58   ` Michal Wajdeczko

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=20240606112916.5qsne74isbfkyypr@intel.com \
    --to=piotr.piorkowski@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=michal.wajdeczko@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