Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: "Matthew Brost" <matthew.brost@intel.com>,
	"Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
	"Rodrigo Vivi" <rodrigo.vivi@intel.com>,
	"Raag Jadav" <raag.jadav@intel.com>,
	"Mika Westerberg" <mika.westerberg@linux.intel.com>,
	"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>
Cc: 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 v6 0/3] drm/xe/i2c: alerts and controller enabling modifications
Date: Tue, 28 Jul 2026 17:50:51 +0200	[thread overview]
Message-ID: <amjP22-2VVk0QgyH@black.igk.intel.com> (raw)
In-Reply-To: <20260722133554.2079612-1-heikki.krogerus@linux.intel.com>

On Wed, Jul 22, 2026 at 03:35:51PM +0200, Heikki Krogerus wrote:
> Hi,
> 
> Changed since v5:
> - Leaving the interrupt de-asserting to the firmware.
> - Re-asserting the interrupt before declaring the device wedged.
> - Preventing the SMBus Alert from being masked.
> 
> v5: https://lore.kernel.org/lkml/20260715153153.1243751-1-heikki.krogerus@linux.intel.com/
> v4: https://lore.kernel.org/lkml/20260713155601.711389-1-heikki.krogerus@linux.intel.com/
> v2: https://lore.kernel.org/lkml/20260625125939.429078-1-heikki.krogerus@linux.intel.com/
> v1: https://lore.kernel.org/lkml/20260622114759.3464047-1-heikki.krogerus@linux.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                | 187 +++++++++++++++++++++
>  drivers/gpu/drm/xe/xe_amc.h                |  25 +++
>  drivers/gpu/drm/xe/xe_i2c.c                | 165 +++++++++---------
>  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, 431 insertions(+), 165 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

One more fix is needed for this series. Raag noticed that the i2c
driver accesses the registers after the drm device is declared wedget.
The i2c adapter is suspended after the device is declared wedged, and
the driver's suspend callback then accesses the registers.

Thanks,

-- 
heikki

  parent reply	other threads:[~2026-07-28 15:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-22 13:35 [PATCH v6 0/3] drm/xe/i2c: alerts and controller enabling modifications Heikki Krogerus
2026-07-22 13:35 ` [PATCH v6 1/3] i2c: designware: Global register definitions Heikki Krogerus
2026-07-22 13:35 ` [PATCH v6 2/3] drm/xe/i2c: Fix the interrupt handling Heikki Krogerus
2026-07-29 15:30   ` Raag Jadav
2026-07-22 13:35 ` [PATCH v6 3/3] drm/xe/i2c: Keep the i2c controller always enabled Heikki Krogerus
2026-07-29 15:34   ` Raag Jadav
2026-07-22 16:28 ` ✗ CI.checkpatch: warning for drm/xe/i2c: alerts and controller enabling modifications (rev6) Patchwork
2026-07-22 16:30 ` ✓ CI.KUnit: success " Patchwork
2026-07-22 17:50 ` ✓ Xe.CI.BAT: " Patchwork
2026-07-28 15:50 ` Heikki Krogerus [this message]
2026-07-29 15:24   ` [PATCH v6 0/3] drm/xe/i2c: alerts and controller enabling modifications Raag Jadav

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=amjP22-2VVk0QgyH@black.igk.intel.com \
    --to=heikki.krogerus@linux.intel.com \
    --cc=andi.shyti@kernel.org \
    --cc=andriy.shevchenko@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=rodrigo.vivi@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