From: Mario Limonciello <mario.limonciello@amd.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Benjamin Tissoires <benjamin.tissoires@redhat.com>,
Raul E Rangel <rrangel@chromium.org>,
<linux-gpio@vger.kernel.org>, <linux-acpi@vger.kernel.org>
Cc: <regressions@lists.linux.dev>,
Mario Limonciello <mario.limonciello@amd.com>,
<linux-kernel@vger.kernel.org>
Subject: [PATCH 0/2] Fix a spurious wakeup regression
Date: Mon, 16 Jan 2023 13:37:00 -0600 [thread overview]
Message-ID: <20230116193702.31356-1-mario.limonciello@amd.com> (raw)
commit 1796f808e4bb ("HID: i2c-hid: acpi: Stop setting wakeup_capable")
changed the policy such that I2C touchpads may be able to wake up the
system by default if the system is configured as such.
This had an unintended consequence on a Clevo NL50RU where the system
would wakeup immediately after suspending the system.
Reviewing the schematics and ACPI tables this appears to be a bug in
the ACPI tables, but it was exposed by that change.
To avoid the system waking up immediately after suspend disable wakeups
by default on this system.
Mario Limonciello (2):
gpiolib: acpi: Allow ignoring wake capability on pins that aren't in
_AEI
gpiolib: acpi: Add a ignore wakeup quirk for Clevo NL5xRU
drivers/gpio/gpiolib-acpi.c | 17 +++++++++++++++--
1 file changed, 15 insertions(+), 2 deletions(-)
--
2.34.1
next reply other threads:[~2023-01-16 19:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-16 19:37 Mario Limonciello [this message]
2023-01-16 19:37 ` [PATCH 1/2] gpiolib: acpi: Allow ignoring wake capability on pins that aren't in _AEI Mario Limonciello
2023-01-17 8:33 ` Andy Shevchenko
2023-01-16 19:37 ` [PATCH 2/2] gpiolib: acpi: Add a ignore wakeup quirk for Clevo NL5xRU Mario Limonciello
2023-01-17 8:33 ` Andy Shevchenko
2023-01-18 14:26 ` Bartosz Golaszewski
2023-01-18 20:44 ` Linus Walleij
2023-01-18 20:50 ` Limonciello, Mario
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=20230116193702.31356-1-mario.limonciello@amd.com \
--to=mario.limonciello@amd.com \
--cc=benjamin.tissoires@redhat.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=regressions@lists.linux.dev \
--cc=rrangel@chromium.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