From: "Limonciello, Mario" <Mario.Limonciello@amd.com>
To: Mika Westerberg <mika.westerberg@linux.intel.com>,
Antheas Kapenekakis <lkml@antheas.dev>
Cc: "linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Mika Westerberg <westeri@kernel.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <brgl@bgdev.pl>
Subject: Re: [PATCH v1] gpiolib: acpi: Ignore touchpad wakeup on GPD G1619-05
Date: Thu, 28 Aug 2025 15:20:51 +0000 [thread overview]
Message-ID: <429fdac8-44dd-4cb1-83b8-f0941dcdd388@amd.com> (raw)
In-Reply-To: <20250828051038.GT476609@black.igk.intel.com>
On 8/28/25 12:10 AM, Mika Westerberg wrote:
> On Wed, Aug 27, 2025 at 07:58:42PM +0200, Antheas Kapenekakis wrote:
>> Same issue as G1619-04 in commit 805c74eac8cb ("gpiolib: acpi: Ignore
>> touchpad wakeup on GPD G1619-04"), Strix Point lineup uses 05.
>>
>> Signed-off-by: Antheas Kapenekakis <lkml@antheas.dev>
>
> Reviewed-by: Mika Westerberg <westeri@kernel.org>
Reviewed-by: Mario Limonciello <mario.limonciello@amd.com>
However as this is the second year in a row with this exact same issue I
would also ask if you can please contact the manufacturer to fix it in
the BIOS for future models so we can hopefully stop accumulating quirks.
next prev parent reply other threads:[~2025-08-28 15:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-27 17:58 [PATCH v1] gpiolib: acpi: Ignore touchpad wakeup on GPD G1619-05 Antheas Kapenekakis
2025-08-28 5:10 ` Mika Westerberg
2025-08-28 15:20 ` Limonciello, Mario [this message]
2025-08-28 15:55 ` Antheas Kapenekakis
2025-08-30 19:51 ` Bartosz Golaszewski
2025-09-01 6:07 ` Andy Shevchenko
2025-09-01 9:04 ` 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=429fdac8-44dd-4cb1-83b8-f0941dcdd388@amd.com \
--to=mario.limonciello@amd.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=brgl@bgdev.pl \
--cc=linus.walleij@linaro.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@antheas.dev \
--cc=mika.westerberg@linux.intel.com \
--cc=westeri@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).