stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Limonciello, Mario" <mario.limonciello@amd.com>
To: "stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Interrupt storm on some gaming laptops
Date: Mon, 17 Jul 2023 15:17:48 -0500	[thread overview]
Message-ID: <10fef988-8460-f96a-2d3d-cc8c6a37f3eb@amd.com> (raw)

Hi,

An interrupt storm was reported on some gaming laptops [1].
This is fixed by a series of commits that has gone into 6.5-rc2.
This interrupt storm causes a pretty dramatic issue of unable to use the 
internal keyboard, so IMO a good idea to take the solution back to 
stable kernels as well.

Here is the series needed for 6.4.y:
968ab9261627 pinctrl: amd: Detect internal GPIO0 debounce handling
a855724dc08b pinctrl: amd: Fix mistake in handling clearing pins at startup
0cf9e48ff22e pinctrl: amd: Detect and mask spurious interrupts
65f6c7c91cb2 pinctrl: amd: Revert "pinctrl: amd: disable and mask 
interrupts on probe"
0d5ace1a07f7 pinctrl: amd: Only use special debounce behavior for GPIO 0
635a750d958e pinctrl: amd: Use amd_pinconf_set() for all config options
3f62312d04d4 pinctrl: amd: Drop pull up select configuration
283c5ce7da0a pinctrl: amd: Unify debounce handling into amd_pinconf_set()

Here is the series needed for 6.1.y:
df72b4a692b6 pinctrl: amd: Add Z-state wake control bits
75358cf3319d pinctrl: amd: Adjust debugfs output
010f493d90ee pinctrl: amd: Add fields for interrupt status and wake status
968ab9261627 pinctrl: amd: Detect internal GPIO0 debounce handling
a855724dc08b pinctrl: amd: Fix mistake in handling clearing pins at startup
0cf9e48ff22e pinctrl: amd: Detect and mask spurious interrupts
65f6c7c91cb2 pinctrl: amd: Revert "pinctrl: amd: disable and mask 
interrupts on probe"
0d5ace1a07f7 pinctrl: amd: Only use special debounce behavior for GPIO 0
635a750d958e pinctrl: amd: Use amd_pinconf_set() for all config options
3f62312d04d4 pinctrl: amd: Drop pull up select configuration
283c5ce7da0a pinctrl: amd: Unify debounce handling into amd_pinconf_set()

[1] https://bugzilla.kernel.org/show_bug.cgi?id=217336

Thanks,

             reply	other threads:[~2023-07-17 20:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-17 20:17 Limonciello, Mario [this message]
2023-07-21  4:33 ` Interrupt storm on some gaming laptops Greg KH

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=10fef988-8460-f96a-2d3d-cc8c6a37f3eb@amd.com \
    --to=mario.limonciello@amd.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;
as well as URLs for NNTP newsgroup(s).