From: Wolfram Sang <wsa@kernel.org>
To: Jarkko Nikula <jarkko.nikula@linux.intel.com>
Cc: linux-i2c@vger.kernel.org,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Jan Dabros <jsd@semihalf.com>, Samuel Clark <slc2015@gmail.com>,
stable@vger.kernel.org
Subject: Re: [PATCH] i2c: designware: Fix handling of real but unexpected device interrupts
Date: Wed, 5 Oct 2022 21:01:25 +0200 [thread overview]
Message-ID: <Yz3Uhe3roLepyzfr@shikoro> (raw)
In-Reply-To: <20220927135644.1656369-1-jarkko.nikula@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 2286 bytes --]
On Tue, Sep 27, 2022 at 04:56:44PM +0300, Jarkko Nikula wrote:
> Commit c7b79a752871 ("mfd: intel-lpss: Add Intel Alder Lake PCH-S PCI
> IDs") caused a regression on certain Gigabyte motherboards for Intel
> Alder Lake-S where system crashes to NULL pointer dereference in
> i2c_dw_xfer_msg() when system resumes from S3 sleep state ("deep").
>
> I was able to debug the issue on Gigabyte Z690 AORUS ELITE and made
> following notes:
>
> - Issue happens when resuming from S3 but not when resuming from
> "s2idle"
> - PCI device 00:15.0 == i2c_designware.0 is already in D0 state when
> system enters into pci_pm_resume_noirq() while all other i2c_designware
> PCI devices are in D3. Devices were runtime suspended and in D3 prior
> entering into suspend
> - Interrupt comes after pci_pm_resume_noirq() when device interrupts are
> re-enabled
> - According to register dump the interrupt really comes from the
> i2c_designware.0. Controller is enabled, I2C target address register
> points to a one detectable I2C device address 0x60 and the
> DW_IC_RAW_INTR_STAT register START_DET, STOP_DET, ACTIVITY and
> TX_EMPTY bits are set indicating completed I2C transaction.
>
> My guess is that the firmware uses this controller to communicate with
> an on-board I2C device during resume but does not disable the controller
> before giving control to an operating system.
>
> I was told the UEFI update fixes this but never the less it revealed the
> driver is not ready to handle TX_EMPTY (or RX_FULL) interrupt when device
> is supposed to be idle and state variables are not set (especially the
> dev->msgs pointer which may point to NULL or stale old data).
>
> Introduce a new software status flag STATUS_ACTIVE indicating when the
> controller is active in driver point of view. Now treat all interrupts
> that occur when is not set as unexpected and mask all interrupts from
> the controller.
>
> Fixes: c7b79a752871 ("mfd: intel-lpss: Add Intel Alder Lake PCH-S PCI IDs")
> Reported-by: Samuel Clark <slc2015@gmail.com>
> Link: https://bugzilla.kernel.org/show_bug.cgi?id=215907
> Cc: stable@vger.kernel.org # v5.12+
> Signed-off-by: Jarkko Nikula <jarkko.nikula@linux.intel.com>
Applied to for-current, thanks!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2022-10-05 19:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-27 13:56 [PATCH] i2c: designware: Fix handling of real but unexpected device interrupts Jarkko Nikula
2022-09-27 14:35 ` Andy Shevchenko
2022-09-28 5:49 ` Jarkko Nikula
2022-09-28 8:13 ` Hans de Goede
2022-10-01 22:40 ` Wolfram Sang
2022-10-02 8:10 ` Hans de Goede
2022-10-05 19:01 ` Wolfram Sang [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=Yz3Uhe3roLepyzfr@shikoro \
--to=wsa@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=jarkko.nikula@linux.intel.com \
--cc=jsd@semihalf.com \
--cc=linux-i2c@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=slc2015@gmail.com \
--cc=stable@vger.kernel.org \
/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