Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: "Anoop, Vijay" <anoop.c.vijay@intel.com>
Cc: <intel-xe@lists.freedesktop.org>,
	<umesh.nerlige.ramappa@intel.com>, <badal.nilawar@intel.com>,
	<aravind.iddamsetty@intel.com>, <riana.tauro@intel.com>,
	<anshuman.gupta@intel.com>, <matthew.d.roper@intel.com>,
	<michael.j.ruhl@intel.com>, <paul.e.luse@intel.com>,
	<mohamed.mansoor.v@intel.com>, <kam.nasim@intel.com>
Subject: Re: [RFC v1 2/5] drm/xe/fwctl: Add uAPI definitions for Xe FWCTL support
Date: Thu, 7 May 2026 17:05:43 -0400	[thread overview]
Message-ID: <afz-pzOEAVlwg4m8@intel.com> (raw)
In-Reply-To: <20260320072528.1780651-9-anoop.c.vijay@intel.com>

On Fri, Mar 20, 2026 at 12:25:30AM -0700, Anoop, Vijay wrote:
> From: Anoop Vijay <anoop.c.vijay@intel.com>
> 
> Add Xe-specific uAPI definitions for FWCTL support. Introduce
> include/uapi/fwctl/xe.h to describe userspace ABI for Xe firmware
> control operations, and extend core FWCTL uAPI to recognize
> Xe device type.
> 
> This patch adds uAPI definitions only. No functional kernel code
> is introduced.
> 
> Signed-off-by: Anoop Vijay <anoop.c.vijay@intel.com>
> ---
>  include/uapi/fwctl/fwctl.h |  1 +
>  include/uapi/fwctl/xe.h    | 38 ++++++++++++++++++++++++++++++++++++++
>  2 files changed, 39 insertions(+)
>  create mode 100644 include/uapi/fwctl/xe.h
> 
> diff --git a/include/uapi/fwctl/fwctl.h b/include/uapi/fwctl/fwctl.h
> index 716ac0eee42d..c63bc15159d3 100644
> --- a/include/uapi/fwctl/fwctl.h
> +++ b/include/uapi/fwctl/fwctl.h
> @@ -45,6 +45,7 @@ enum fwctl_device_type {
>  	FWCTL_DEVICE_TYPE_MLX5 = 1,
>  	FWCTL_DEVICE_TYPE_CXL = 2,
>  	FWCTL_DEVICE_TYPE_PDS = 4,
> +	FWCTL_DEVICE_TYPE_XE = 5,

I don't believe we should have a generic XE component here, but one per
FW since we have many different FW underneath and each one with its
own different Mailboxes.

Check: https://lore.kernel.org/intel-xe/20250429073804.972137-10-badal.nilawar@intel.com/

>  };
>  
>  /**
> diff --git a/include/uapi/fwctl/xe.h b/include/uapi/fwctl/xe.h
> new file mode 100644
> index 000000000000..fb5612dec610
> --- /dev/null
> +++ b/include/uapi/fwctl/xe.h
> @@ -0,0 +1,38 @@
> +/* SPDX-License-Identifier: MIT */
> +/*
> + * Copyright © 2026 Intel Corporation
> + */
> +
> +#ifndef _UAPI_FWCTL_XE_H_
> +#define _UAPI_FWCTL_XE_H_
> +
> +#include <linux/types.h>
> +
> +/**
> + * DOC: Xe FWCTL Interface
> + *
> + * The Xe FWCTL interface provides userspace access to firmware subsystems
> + * on Intel Xe discrete GPUs. It exposes firmware management capabilities
> + * through the kernel FWCTL framework.
> + */
> +
> +/**
> + * struct fwctl_info_xe - FWCTL Information struct for Xe
> + *
> + * @fw_caps: Firmware capability bitmap
> + * @platform: Platform type
> + */
> +struct fwctl_info_xe {
> +	__u32 fw_caps;
> +	__u32 platform;
> +};
> +
> +/**
> + * struct fwctl_rpc_xe - Common Xe FWCTL RPC header
> + * @firmware_type: Firmware type
> + */
> +struct fwctl_rpc_xe {
> +	__u32 firmware_type;
> +};
> +
> +#endif
> -- 
> 2.43.0
> 

  reply	other threads:[~2026-05-07 21:05 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-20  7:25 [RFC v1 0/5] drm/xe/fwctl: Add FWCTL interface for Xe firmware management Anoop, Vijay
2026-03-20  7:25 ` [RFC v1 1/5] drm/xe/xe_sysctrl: Add System Controller support Anoop, Vijay
2026-03-20  7:25 ` [RFC v1 2/5] drm/xe/fwctl: Add uAPI definitions for Xe FWCTL support Anoop, Vijay
2026-05-07 21:05   ` Rodrigo Vivi [this message]
2026-03-20  7:25 ` [RFC v1 3/5] drm/xe/fwctl: Add Xe FWCTL type definitions Anoop, Vijay
2026-05-07 21:07   ` Rodrigo Vivi
2026-03-20  7:25 ` [RFC v1 4/5] drm/xe/fwctl: Add Xe FWCTL infrastructure support Anoop, Vijay
2026-03-20  7:25 ` [RFC v1 5/5] drm/xe/fwctl: Add System Controller FWCTL RPC handler Anoop, Vijay
2026-05-07 21:12   ` Rodrigo Vivi
2026-03-20  7:30 ` ✗ CI.checkpatch: warning for drm/xe/fwctl: Add FWCTL interface for Xe firmware management Patchwork
2026-03-20  7:32 ` ✓ CI.KUnit: success " Patchwork
2026-03-20  7:46 ` ✗ CI.checksparse: warning " Patchwork
2026-03-20  8:20 ` ✓ Xe.CI.BAT: success " Patchwork
2026-03-21  3:59 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-04-28  0:12 ` [RFC v1 0/5] " Anoop Vijay

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=afz-pzOEAVlwg4m8@intel.com \
    --to=rodrigo.vivi@intel.com \
    --cc=anoop.c.vijay@intel.com \
    --cc=anshuman.gupta@intel.com \
    --cc=aravind.iddamsetty@intel.com \
    --cc=badal.nilawar@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=kam.nasim@intel.com \
    --cc=matthew.d.roper@intel.com \
    --cc=michael.j.ruhl@intel.com \
    --cc=mohamed.mansoor.v@intel.com \
    --cc=paul.e.luse@intel.com \
    --cc=riana.tauro@intel.com \
    --cc=umesh.nerlige.ramappa@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