From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Mario Limonciello <mario.limonciello@amd.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <brgl@bgdev.pl>,
linux-gpio@vger.kernel.org, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] gpiolib: acpi: Add support to ignore programming an interrupt
Date: Fri, 26 Aug 2022 20:31:35 +0300 [thread overview]
Message-ID: <YwkDd+mAhyoSwVeq@smile.fi.intel.com> (raw)
In-Reply-To: <efb83a0c-7617-894e-a34d-37280238d5aa@redhat.com>
On Wed, Aug 03, 2022 at 05:07:15PM +0200, Hans de Goede wrote:
> On 8/3/22 06:24, Mario Limonciello wrote:
> > gpiolib-acpi already had support for ignoring a pin for wakeup, but
> > if an OEM configures a floating pin as an interrupt source then
> > stopping it from being a wakeup won't do much good to stop the
> > interrupt storm.
> >
> > Add support for a module parameter and quirk infrastructure to
> > ignore interrupts as well.
> >
> > Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
>
> Thanks, patch looks good to me:
>
> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
Pushed to my review and testing queue, thanks!
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2022-08-26 17:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-03 4:24 [PATCH v2 1/2] gpiolib: acpi: Add support to ignore programming an interrupt Mario Limonciello
2022-08-03 4:25 ` [PATCH v2 2/2] gpiolib: acpi: Add a quirk for Asus UM325UAZ Mario Limonciello
2022-08-03 9:50 ` Mika Westerberg
2022-08-03 9:47 ` [PATCH v2 1/2] gpiolib: acpi: Add support to ignore programming an interrupt Mika Westerberg
2022-08-03 15:07 ` Hans de Goede
2022-08-26 17:31 ` Andy Shevchenko [this message]
2022-08-29 18:16 ` Limonciello, Mario
2022-08-29 19:26 ` Andy Shevchenko
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=YwkDd+mAhyoSwVeq@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=brgl@bgdev.pl \
--cc=hdegoede@redhat.com \
--cc=linus.walleij@linaro.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=mika.westerberg@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.