From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Heikki Krogerus <heikki.krogerus@linux.intel.com>
Cc: "Matthew Brost" <matthew.brost@intel.com>,
"Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
"Raag Jadav" <raag.jadav@intel.com>,
"Mika Westerberg" <mika.westerberg@linux.intel.com>,
"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
"Andi Shyti" <andi.shyti@kernel.org>,
"Ramesh Babu B" <ramesh.babu.b@intel.com>,
"Michael J. Ruhl" <michael.j.ruhl@intel.com>,
linux-kernel@vger.kernel.org, intel-xe@lists.freedesktop.org,
stable@vger.kernel.org
Subject: Re: [PATCH v4 0/3] drm/xe/i2c: alerts and controller enabling modifications
Date: Tue, 14 Jul 2026 11:54:16 -0400 [thread overview]
Message-ID: <alZbqH51wJjm_CVC@intel.com> (raw)
In-Reply-To: <20260713155601.711389-1-heikki.krogerus@linux.intel.com>
On Mon, Jul 13, 2026 at 05:55:58PM +0200, Heikki Krogerus wrote:
> Hi,
>
> The hardware challenges that these patches address are so severe that I'm
> marking both of them as fixes. In both cases the GPU may silently end up in
> unresponsive state (or worse). The second patch has been refactored so that it
> includes the direct AMC alert handling in Xe instead of the normal alert handler
> registration. The subject lines were also changed to highlight the fact that
> these are fixes. Ramesh helped me with the testing and with the implementation
> for the AMC alert handling.
>
> Changed since v2:
> - Added Fixes tag to both patches.
> - i2c-designware is no longer supplied with an interrupt so it will be in
> polling mode (ACCESS_POLLING will be enabled). The IRQ path in hardware can't
> handle the amount of interrupts the i2c controller generates. Only the
> interrupts from the SMBus Alert line are left enabled.
> - The registration of the default smbus alert handler is dropped.
> - The AMC alerts are handled directly in Xe. All the alerts will cause the
> device to be declared as wedged at least for now.
> - Cleanups proposed by Raag.
>
> v2: https://lore.kernel.org/lkml/20260625125939.429078-1-heikki.krogerus@linux.intel.com/
>
> Changed since v1:
> - Global header for the DesignWare I2C registers which meant a bit of
> patch refactoring.
> - Selecting CONFIG_SMBUS in CONFIG_XE and handling smbus in xe_i2c.c instead of
> separate file.
> - Storing the alert device to the client array and providing enum for the
> clients.
> - Allowing other fields in the IC_ENABLE register to be updated except the
> Enable bit.
> - Can't sleep in xe_i2c_disable() so using udelay().
>
> v1: https://lore.kernel.org/lkml/20260622114759.3464047-1-heikki.krogerus@linux.intel.com/
>
> This includes support for the SMBus alerts, and special handling for the
> IC_ENABLE register.
>
> Thanks,
Please take a look to Shashiko review and let us know in case of false positives:
https://sashiko.dev/#/patchset/20260713155601.711389-1-heikki.krogerus%40linux.intel.com
>
> Heikki Krogerus (3):
> i2c: designware: Global register definitions
> drm/xe/i2c: Fix the interrupt handling
> drm/xe/i2c: Keep the i2c controller always enabled
>
> MAINTAINERS | 1 +
> drivers/gpu/drm/xe/Makefile | 4 +-
> drivers/gpu/drm/xe/regs/xe_i2c_regs.h | 2 +
> drivers/gpu/drm/xe/xe_amc.c | 173 +++++++++++++++++++++
> drivers/gpu/drm/xe/xe_amc.h | 25 +++
> drivers/gpu/drm/xe/xe_i2c.c | 136 +++++++++-------
> drivers/gpu/drm/xe/xe_i2c.h | 14 +-
> drivers/i2c/busses/i2c-designware-common.c | 2 +
> drivers/i2c/busses/i2c-designware-core.h | 85 +---------
> drivers/i2c/busses/i2c-designware-master.c | 2 +
> drivers/i2c/busses/i2c-designware-slave.c | 2 +
> include/linux/designware_i2c.h | 107 +++++++++++++
> 12 files changed, 405 insertions(+), 148 deletions(-)
> create mode 100644 drivers/gpu/drm/xe/xe_amc.c
> create mode 100644 drivers/gpu/drm/xe/xe_amc.h
> create mode 100644 include/linux/designware_i2c.h
>
> --
> 2.50.1
>
next prev parent reply other threads:[~2026-07-14 15:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-13 15:55 [PATCH v4 0/3] drm/xe/i2c: alerts and controller enabling modifications Heikki Krogerus
2026-07-13 15:55 ` [PATCH v4 1/3] i2c: designware: Global register definitions Heikki Krogerus
2026-07-13 15:56 ` [PATCH v4 2/3] drm/xe/i2c: Fix the interrupt handling Heikki Krogerus
2026-07-15 6:26 ` Raag Jadav
2026-07-15 9:53 ` Heikki Krogerus
2026-07-15 11:55 ` Raag Jadav
2026-07-15 12:59 ` Heikki Krogerus
2026-07-15 14:00 ` Heikki Krogerus
2026-07-15 14:59 ` Heikki Krogerus
2026-07-13 15:56 ` [PATCH v4 3/3] drm/xe/i2c: Keep the i2c controller always enabled Heikki Krogerus
2026-07-15 6:33 ` Raag Jadav
2026-07-15 9:45 ` Heikki Krogerus
2026-07-13 16:02 ` ✗ CI.checkpatch: warning for drm/xe/i2c: alerts and controller enabling modifications (rev3) Patchwork
2026-07-13 16:03 ` ✓ CI.KUnit: success " Patchwork
2026-07-13 16:56 ` ✓ Xe.CI.BAT: " Patchwork
2026-07-13 19:39 ` ✓ Xe.CI.FULL: " Patchwork
2026-07-14 15:54 ` Rodrigo Vivi [this message]
2026-07-15 10:00 ` [PATCH v4 0/3] drm/xe/i2c: alerts and controller enabling modifications Heikki Krogerus
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=alZbqH51wJjm_CVC@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=andi.shyti@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=heikki.krogerus@linux.intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew.brost@intel.com \
--cc=michael.j.ruhl@intel.com \
--cc=mika.westerberg@linux.intel.com \
--cc=raag.jadav@intel.com \
--cc=ramesh.babu.b@intel.com \
--cc=stable@vger.kernel.org \
--cc=thomas.hellstrom@linux.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