Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
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, anoop.c.vijay@intel.com
Subject: [PATCH v2 0/2] drm/xe/sysctrl: Add fwctl support for System Controller
Date: Thu,  6 Aug 2026 05:03:10 -0700	[thread overview]
Message-ID: <20260806120310.2054212-4-anoop.c.vijay@intel.com> (raw)

From: Anoop Vijay <anoop.c.vijay@intel.com>

This series adds FWCTL support for the Xe System Controller (sysctrl)
firmware.

The Xe System Controller is a firmware-managed entity responsible for
selected platform-level control and coordination tasks on Intel Xe3p
discrete GPU platforms. This series registers a
FWCTL_DEVICE_TYPE_XE_SYSCTRL device so userspace can query sysctrl
capabilities and issue RPC requests through the generic
/dev/fwctl/fwctlN interface.

Supported operations are ECC status query, RAS error-injection
capability query, and RAS error injection, each gated by the
appropriate FWCTL_RPC scope and a per-context capability bit.

---
v2: (Rodrigo)
- Rename FWCTL_DEVICE_TYPE_XE to FWCTL_DEVICE_TYPE_XE_SYSCTRL, one type
  per firmware instead of a shared Xe-wide type
- Rename xe.h to xe_sysctrl.h to match
- Squash uapi and type definitions into a single patch
- Replace validate_scope() with explicit per-op scope/capability checks
  in xe_sysctrl_fwctl_rpc()
---

Anoop Vijay (2):
  drm/xe/sysctrl: Add System Controller get application status
  drm/xe/sysctrl: Add fwctl support for System Controller

 Documentation/userspace-api/fwctl/index.rst   |   1 +
 .../userspace-api/fwctl/xe_sysctrl.rst        | 120 +++++++++
 drivers/gpu/drm/xe/Kconfig                    |   1 +
 drivers/gpu/drm/xe/Makefile                   |   1 +
 drivers/gpu/drm/xe/xe_device.c                |   5 +
 drivers/gpu/drm/xe/xe_sysctrl.c               |  82 ++++++
 drivers/gpu/drm/xe/xe_sysctrl.h               |   2 +
 drivers/gpu/drm/xe/xe_sysctrl_fwctl.c         | 251 ++++++++++++++++++
 drivers/gpu/drm/xe/xe_sysctrl_fwctl.h         |  13 +
 drivers/gpu/drm/xe/xe_sysctrl_mailbox_types.h | 151 +++++++++++
 include/uapi/fwctl/fwctl.h                    |   1 +
 include/uapi/fwctl/xe_sysctrl.h               | 117 ++++++++
 12 files changed, 745 insertions(+)
 create mode 100644 Documentation/userspace-api/fwctl/xe_sysctrl.rst
 create mode 100644 drivers/gpu/drm/xe/xe_sysctrl_fwctl.c
 create mode 100644 drivers/gpu/drm/xe/xe_sysctrl_fwctl.h
 create mode 100644 include/uapi/fwctl/xe_sysctrl.h

-- 
2.43.0


             reply	other threads:[~2026-08-06 12:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-06 12:03 Anoop, Vijay [this message]
2026-08-06 12:03 ` [PATCH v2 1/2] drm/xe/sysctrl: Add System Controller get application status Anoop, Vijay
2026-08-06 12:03 ` [PATCH v2 2/2] drm/xe/sysctrl: Add fwctl support for System Controller Anoop, Vijay
2026-08-10 21:11   ` Umesh Nerlige Ramappa
2026-08-25 21:51     ` Rodrigo Vivi
2026-08-26  4:55       ` Umesh Nerlige Ramappa
2026-08-06 12:09 ` ✗ CI.checkpatch: warning for " Patchwork
2026-08-06 12:10 ` ✓ CI.KUnit: success " Patchwork
2026-08-06 13:26 ` ✓ Xe.CI.BAT: " Patchwork
2026-08-06 23:02 ` ✗ Xe.CI.FULL: failure " Patchwork

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=20260806120310.2054212-4-anoop.c.vijay@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