From: Anoop Vijay <anoop.c.vijay@intel.com>
To: <intel-xe@lists.freedesktop.org>
Cc: <umesh.nerlige.ramappa@intel.com>, <badal.nilawar@intel.com>,
<rodrigo.vivi@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 0/5] drm/xe/fwctl: Add FWCTL interface for Xe firmware management
Date: Tue, 28 Apr 2026 05:42:20 +0530 [thread overview]
Message-ID: <cc728ee0-2617-49c9-a35a-20ec2881f7e5@intel.com> (raw)
In-Reply-To: <20260320072528.1780651-7-anoop.c.vijay@intel.com>
[-- Attachment #1: Type: text/plain, Size: 3460 bytes --]
Hi,
Bumping this RFC series and requesting a review.
Feedback on the proposed interface and overall approach would be greatly
appreciated before I proceed to the next revision.
Thanks,
Anoop
On 20-03-2026 12:55, Anoop, Vijay wrote:
> From: Anoop Vijay<anoop.c.vijay@intel.com>
>
> This series builds on top of System Controller series[1] and adds FWCTL
> framework support for System Controller firmware access on Intel Xe discrete
> GPUs.
>
> Patches introduce generic FWCTL infrastructure with pluggable firmware
> backend support, implementing initial System Controller backend to enable
> userspace firmware management through standard FWCTL device interfaces.
>
> Key features introduced:
> - Generic xe_fw_ops interface for firmware backend implementations
> - FWCTL device registration and ioctl handlers (info, rpc)
> - System Controller FWCTL backend with scope validation and RPC execution
> - Userspace-accessible firmware RPCs through /dev/fwctl/fwctl<N>
>
> [1]https://patchwork.freedesktop.org/series/163196/
>
> Anoop Vijay (5):
> drm/xe/xe_sysctrl: Add System Controller support
> drm/xe/fwctl: Add uAPI definitions for Xe FWCTL support
> drm/xe/fwctl: Add Xe FWCTL type definitions
> drm/xe/fwctl: Add Xe FWCTL infrastructure support
> drm/xe/fwctl: Add System Controller FWCTL RPC handler
>
> Documentation/userspace-api/fwctl/index.rst | 1 +
> drivers/gpu/drm/xe/Kconfig | 1 +
> drivers/gpu/drm/xe/Makefile | 4 +
> drivers/gpu/drm/xe/abi/xe_sysctrl_abi.h | 94 ++++
> drivers/gpu/drm/xe/regs/xe_sysctrl_regs.h | 36 ++
> drivers/gpu/drm/xe/xe_device.c | 10 +
> drivers/gpu/drm/xe/xe_device_types.h | 10 +
> drivers/gpu/drm/xe/xe_fwctl.c | 206 +++++++++
> drivers/gpu/drm/xe/xe_fwctl.h | 15 +
> drivers/gpu/drm/xe/xe_fwctl_types.h | 52 +++
> drivers/gpu/drm/xe/xe_pci.c | 2 +
> drivers/gpu/drm/xe/xe_pci_types.h | 1 +
> drivers/gpu/drm/xe/xe_pm.c | 11 +
> drivers/gpu/drm/xe/xe_sysctrl.c | 128 ++++++
> drivers/gpu/drm/xe/xe_sysctrl.h | 23 +
> drivers/gpu/drm/xe/xe_sysctrl_fwctl.c | 136 ++++++
> drivers/gpu/drm/xe/xe_sysctrl_mailbox.c | 400 ++++++++++++++++++
> drivers/gpu/drm/xe/xe_sysctrl_mailbox.h | 33 ++
> drivers/gpu/drm/xe/xe_sysctrl_mailbox_types.h | 40 ++
> drivers/gpu/drm/xe/xe_sysctrl_types.h | 32 ++
> include/uapi/fwctl/fwctl.h | 1 +
> include/uapi/fwctl/xe.h | 65 +++
> 22 files changed, 1301 insertions(+)
> create mode 100644 drivers/gpu/drm/xe/abi/xe_sysctrl_abi.h
> create mode 100644 drivers/gpu/drm/xe/regs/xe_sysctrl_regs.h
> create mode 100644 drivers/gpu/drm/xe/xe_fwctl.c
> create mode 100644 drivers/gpu/drm/xe/xe_fwctl.h
> create mode 100644 drivers/gpu/drm/xe/xe_fwctl_types.h
> create mode 100644 drivers/gpu/drm/xe/xe_sysctrl.c
> create mode 100644 drivers/gpu/drm/xe/xe_sysctrl.h
> create mode 100644 drivers/gpu/drm/xe/xe_sysctrl_fwctl.c
> create mode 100644 drivers/gpu/drm/xe/xe_sysctrl_mailbox.c
> create mode 100644 drivers/gpu/drm/xe/xe_sysctrl_mailbox.h
> create mode 100644 drivers/gpu/drm/xe/xe_sysctrl_mailbox_types.h
> create mode 100644 drivers/gpu/drm/xe/xe_sysctrl_types.h
> create mode 100644 include/uapi/fwctl/xe.h
>
[-- Attachment #2: Type: text/html, Size: 4336 bytes --]
prev parent reply other threads:[~2026-04-28 0:12 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
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 ` Anoop Vijay [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=cc728ee0-2617-49c9-a35a-20ec2881f7e5@intel.com \
--to=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=rodrigo.vivi@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