From: Jani Nikula <jani.nikula@linux.intel.com>
To: Badal Nilawar <badal.nilawar@intel.com>, intel-xe@lists.freedesktop.org
Cc: anshuman.gupta@intel.com, rodrigo.vivi@intel.com,
raag.jadav@intel.com, riana.tauro@intel.com,
mallesh.koujalagi@intel.com, aravind.iddamsetty@intel.com,
heikki.krogerus@linux.intel.com, himal.prasad.ghimiray@intel.com
Subject: Re: [PATCH v3] drm/xe/i2c: Expose AMC Alert reason sysfs
Date: Thu, 01 Oct 2026 17:54:29 +0300 [thread overview]
Message-ID: <0ce399b0e0e23f168d5b916cbdcf60ad6fc058c3@intel.com> (raw)
In-Reply-To: <20261001121302.4102629-2-badal.nilawar@intel.com>
On Thu, 01 Oct 2026, Badal Nilawar <badal.nilawar@intel.com> wrote:
> AMC raises an SMBUS alert before performing a power removal or
> power-cycle operation. The xe driver then places the device into
> vendor-specific wedge mode until the recovery is performed.
>
> Expose a read-only xe_amc_alert_reason sysfs attribute to help users
> identify the required recovery action.
>
> Assisted-by: Claude:claude-opus-4.8
> Signed-off-by: Badal Nilawar <badal.nilawar@intel.com>
> ---
> v2:
> - Created sysfs during i2c probe time
> - Fix Documentation (Rodrigo)
> v3:
> - Keep limited information in "DOC:" section (Michal)
> - Handle AMC alert none and unknown cases, document
> in ABI
> - Clear i2c->amc on sysfs creation failure (Sashiko)
> v4:
> - Fix sashiko comments
> - Fix review comments (Michal)
> ---
> .../ABI/testing/sysfs-driver-intel-xe-amc | 24 ++++++
> drivers/gpu/drm/xe/xe_amc.c | 82 ++++++++++++++++---
> 2 files changed, 96 insertions(+), 10 deletions(-)
> create mode 100644 Documentation/ABI/testing/sysfs-driver-intel-xe-amc
>
> diff --git a/Documentation/ABI/testing/sysfs-driver-intel-xe-amc b/Documentation/ABI/testing/sysfs-driver-intel-xe-amc
> new file mode 100644
> index 000000000000..34927fa5dcfe
> --- /dev/null
> +++ b/Documentation/ABI/testing/sysfs-driver-intel-xe-amc
> @@ -0,0 +1,24 @@
> +What: /sys/bus/pci/drivers/xe/.../xe_amc_alert_reason
> +Date: October 2026
> +KernelVersion: 7.4
> +Contact: intel-xe@lists.freedesktop.org
> +Description:
> + This file exposes the reason for the most recent Add-In
> + Management Controller (AMC) alert on supported Intel Xe platforms.
> +
> + An AMC alert is delivered via an SMBUS interrupt and causes the
> + device to be wedged, requiring vendor-specific recovery.
> + The attribute is read-only and available to all users.
> +
> + Read returns a single line containing one of the following
> + alert reasons:
> +
> + "none"
> + No AMC alert has been received
> + "unknown"
> + AMC alert received but with unknown reason
> + "firmware_download"
> + "thermal_trip"
> + "oob_request"
> + "oob_reset"
> + "catastrophic"
> diff --git a/drivers/gpu/drm/xe/xe_amc.c b/drivers/gpu/drm/xe/xe_amc.c
> index edd50bf8261e..7f21044fd1b7 100644
> --- a/drivers/gpu/drm/xe/xe_amc.c
> +++ b/drivers/gpu/drm/xe/xe_amc.c
> @@ -18,6 +18,7 @@
> #include "xe_device.h"
> #include "xe_i2c.h"
> #include "xe_mmio.h"
> +#include "xe_printk.h"
>
> /**
> * DOC: Add-In Management Controller (AMC)
> @@ -46,16 +47,19 @@ enum xe_amc_alert {
> };
>
> static const char * const amc_alert[] = {
> - [AMC_ALERT_FW_DOWNLOAD] = "Firmware Download",
> - [AMC_ALERT_THERMAL_TRIP] = "Thermal Trip",
> - [AMC_ALERT_OOB_REQUEST] = "OOB Request",
> - [AMC_ALERT_OOB_RESET] = "OOB Reset",
> - [AMC_ALERT_CATERR] = "Catastrophic",
> + [AMC_ALERT_UNKNOWN] = "unknown",
> + [AMC_ALERT_FW_DOWNLOAD] = "firmware_download",
> + [AMC_ALERT_THERMAL_TRIP] = "thermal_trip",
> + [AMC_ALERT_OOB_REQUEST] = "oob_request",
> + [AMC_ALERT_OOB_RESET] = "oob_reset",
> + [AMC_ALERT_CATERR] = "catastrophic",
> };
>
> struct xe_amc {
> struct xe_i2c *i2c;
> struct work_struct work;
> + u8 alert_reason;
Why u8 instead of enum xe_amc_alert?
> + bool alert_seen;
> };
>
> struct amc_header {
> @@ -104,6 +108,45 @@ static const struct amc_request amc_get_alert_reason = {
> },
> };
>
> +/**
> + * DOC: AMC Alert Reason
> + *
> + * Expose AMC alert reason through device sysfs
> + *
> + * See Documentation/ABI/testing/sysfs-driver-intel-xe-amc for the ABI
> + * specification.
> + */
> +
> +static ssize_t amc_alert_reason_show(struct device *dev,
> + struct device_attribute *attr, char *buf)
> +{
> + struct xe_device *xe = pdev_to_xe_device(to_pci_dev(dev));
> + struct xe_amc *amc = xe->i2c->amc;
> + u8 alert_reason;
> +
> + if (!amc->alert_seen)
> + return sysfs_emit(buf, "none\n");
> +
> + alert_reason = READ_ONCE(amc->alert_reason);
> +
> + return sysfs_emit(buf, "%s\n", amc_alert[alert_reason]);
Please add a function for returning amc alert reason,
e.g. amc_alert_reason(). You'll thank me later.
> +}
> +static DEVICE_ATTR_RO(amc_alert_reason);
> +
> +static void amc_remove_alert_sysfs(struct xe_i2c *i2c)
> +{
> + struct device *dev = i2c->drm_dev;
> +
> + device_remove_file(dev, &dev_attr_amc_alert_reason);
> +}
> +
> +static int amc_create_alert_sysfs(struct xe_i2c *i2c)
> +{
> + struct device *dev = i2c->drm_dev;
> +
> + return device_create_file(dev, &dev_attr_amc_alert_reason);
> +}
> +
> static void xe_amc_work(struct work_struct *work)
> {
> const struct amc_request *request = &amc_get_alert_reason;
> @@ -153,17 +196,26 @@ static void xe_amc_work(struct work_struct *work)
> out_reassert_interrupt:
> xe_mmio_rmw32(amc->i2c->mmio, I2C_CONFIG_CMD, PCI_COMMAND_INTX_DISABLE, 0);
>
> + amc->alert_seen = true;
> +
> switch (alert_reason) {
> case AMC_ALERT_FW_DOWNLOAD:
> case AMC_ALERT_THERMAL_TRIP:
> case AMC_ALERT_OOB_REQUEST:
> case AMC_ALERT_OOB_RESET:
> - case AMC_ALERT_CATERR:
> - dev_warn(amc->i2c->drm_dev, "AMC Alert: %s\n", amc_alert[alert_reason]);
> - xe_device_declare_wedged(i2c_client_to_xe_device(client));
> + case AMC_ALERT_CATERR: {
> + struct xe_device *xe = i2c_client_to_xe_device(client);
> +
> + WRITE_ONCE(amc->alert_reason, alert_reason);
> + dev_warn(amc->i2c->drm_dev,
> + "AMC Alert: %s (%u)\n", amc_alert[alert_reason], alert_reason);
> + xe_device_set_wedged_method(xe, DRM_WEDGE_RECOVERY_VENDOR);
> + xe_device_declare_wedged(xe);
> break;
> + }
> default:
> - dev_warn(amc->i2c->drm_dev, "unknown AMC alert: %d\n", alert_reason);
> + WRITE_ONCE(amc->alert_reason, AMC_ALERT_UNKNOWN);
> + dev_warn(amc->i2c->drm_dev, "AMC Alert: unknown (%u)\n", alert_reason);
> break;
> }
> }
> @@ -176,6 +228,7 @@ void xe_amc_handle_alert(struct xe_i2c *i2c)
> int xe_amc_init(struct xe_i2c *i2c)
> {
> struct xe_amc *amc;
> + int ret;
>
> amc = kzalloc_obj(*amc);
> if (!amc)
> @@ -185,13 +238,22 @@ int xe_amc_init(struct xe_i2c *i2c)
> i2c->amc = amc;
> amc->i2c = i2c;
>
> - return 0;
> + amc->alert_seen = false;
> + ret = amc_create_alert_sysfs(i2c);
> + if (ret) {
> + kfree(i2c->amc);
> + i2c->amc = NULL;
> + }
> +
> + return ret;
> }
>
> void xe_amc_exit(struct xe_i2c *i2c)
> {
> if (i2c->amc) {
> + amc_remove_alert_sysfs(i2c);
> cancel_work_sync(&i2c->amc->work);
> kfree(i2c->amc);
> + i2c->amc = NULL;
> }
> }
--
Jani Nikula, Intel
next prev parent reply other threads:[~2026-10-01 14:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-01 12:13 [PATCH v3] drm/xe/i2c: Expose AMC Alert reason sysfs Badal Nilawar
2026-10-01 12:02 ` ✗ CI.checkpatch: warning for " Patchwork
2026-10-01 12:04 ` ✓ CI.KUnit: success " Patchwork
2026-10-01 12:07 ` [PATCH v3] " sashiko-bot
2026-10-01 13:29 ` Nilawar, Badal
2026-10-01 14:17 ` Nilawar, Badal
2026-10-01 14:54 ` Jani Nikula [this message]
2026-10-01 16:26 ` ✓ Xe.CI.BAT: success for " Patchwork
2026-10-01 19:33 ` ✗ 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=0ce399b0e0e23f168d5b916cbdcf60ad6fc058c3@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=anshuman.gupta@intel.com \
--cc=aravind.iddamsetty@intel.com \
--cc=badal.nilawar@intel.com \
--cc=heikki.krogerus@linux.intel.com \
--cc=himal.prasad.ghimiray@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=mallesh.koujalagi@intel.com \
--cc=raag.jadav@intel.com \
--cc=riana.tauro@intel.com \
--cc=rodrigo.vivi@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