From: "Limonciello, Mario" <mario.limonciello@amd.com>
To: dridri85@gmail.com, Friedrich Vock <friedrich.vock@gmx.de>,
nmschulte@gmail.com, npliashechnikov@gmail.com
Cc: Natikar Basavaraj <Basavaraj.Natikar@amd.com>,
S-k Shyam-sundar <Shyam-sundar.S-k@amd.com>,
andriy.shevchenko@linux.intel.com,
Hans de Goede <hdegoede@redhat.com>,
open list <linux-kernel@vger.kernel.org>,
open list <linux-gpio@vger.kernel.org>,
Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [PATCH v2 0/4] Fix for interrupt storm on ASUS TUF A16
Date: Fri, 7 Jul 2023 09:09:50 -0500 [thread overview]
Message-ID: <994042dd-9532-0dfb-8f86-98c897db75fd@amd.com> (raw)
In-Reply-To: <CACRpkdbrwg6wRbFKCfr0H766Z5bX5rANZ-YGAfM6P2q3Khk=bw@mail.gmail.com>
On 7/7/2023 08:50, Linus Walleij wrote:
> On Wed, Jul 5, 2023 at 3:30 PM Mario Limonciello
> <mario.limonciello@amd.com> wrote:
>
>> An interrupt storm is reported for the GPIO controller on ASUS TUF A16
>> but only on Linux. In comparing the GPIO registers from Windows and
>> Linux the configuration for several bits specified in _AEI() was never
>> actually loaded into the hardware on Linux.
>
> I queued this up for fixes as it looks pretty urgent, perhaps I will
> even send it to Torvalds before -rc1 if there is positive feedback.
>
> Yours,
> Linus Walleij
Appreciated, thanks!
To all those that reported this issue, the branch that has all the fixes
committed is:
https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl.git/log/?h=fixes
If you can please check this out and confirm everything works as intended.
It should - the patch was split up into 4 but the meat should be the same.
next prev parent reply other threads:[~2023-07-07 14:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-05 13:30 [PATCH v2 0/4] Fix for interrupt storm on ASUS TUF A16 Mario Limonciello
2023-07-05 13:30 ` [PATCH v2 1/4] pinctrl: amd: Only use special debounce behavior for GPIO 0 Mario Limonciello
2023-07-05 13:30 ` [PATCH v2 2/4] pinctrl: amd: Use amd_pinconf_set() for all config options Mario Limonciello
2023-07-06 9:16 ` Andy Shevchenko
2023-07-06 14:30 ` Limonciello, Mario
2023-07-05 13:30 ` [PATCH v2 3/4] pinctrl: amd: Drop pull up select configuration Mario Limonciello
2023-07-05 13:30 ` [PATCH v2 4/4] pinctrl: amd: Unify debounce handling into amd_pinconf_set() Mario Limonciello
2023-07-07 13:50 ` [PATCH v2 0/4] Fix for interrupt storm on ASUS TUF A16 Linus Walleij
2023-07-07 14:09 ` Limonciello, Mario [this message]
2023-07-10 17:49 ` Jan Visser
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=994042dd-9532-0dfb-8f86-98c897db75fd@amd.com \
--to=mario.limonciello@amd.com \
--cc=Basavaraj.Natikar@amd.com \
--cc=Shyam-sundar.S-k@amd.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=dridri85@gmail.com \
--cc=friedrich.vock@gmx.de \
--cc=hdegoede@redhat.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nmschulte@gmail.com \
--cc=npliashechnikov@gmail.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;
as well as URLs for NNTP newsgroup(s).