From: Mark Brown <broonie@kernel.org>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>,
Kivan <vaknins33@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Mateo Borda <mateob226@gmail.com>
Subject: linux-next: manual merge of the gpio-brgl tree with the gpio-intel-fixes tree
Date: Fri, 25 Sep 2026 17:10:05 +0100 [thread overview]
Message-ID: <arac3fNw4DFKnguy@sirena.org.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 1879 bytes --]
Hi all,
Today's linux-next merge of the gpio-brgl tree got a conflict in:
drivers/gpio/gpiolib-acpi-quirks.c
between commit:
8d37f20173a27 ("gpiolib: acpi: Add quirk for Lenovo IdeaPad Slim 3 15ABR8")
from the gpio-intel-fixes tree and commit:
1900b5a41493e ("gpiolib: acpi: Add ignore_wake quirk for ASUS ZenBook UX425UA_UM425UA")
from the gpio-brgl tree.
I fixed it up (see below) and can carry the fix as necessary. This
is now fixed as far as linux-next is concerned, but any non trivial
conflicts should be mentioned to your upstream maintainer when your tree
is submitted for merging. You may also want to consider cooperating
with the maintainer of the conflicting tree to minimise any particularly
complex conflicts.
diff --cc drivers/gpio/gpiolib-acpi-quirks.c
index 22c5fb1493778,dd4db58d36ad0..0000000000000
--- a/drivers/gpio/gpiolib-acpi-quirks.c
+++ b/drivers/gpio/gpiolib-acpi-quirks.c
@@@ -392,19 -392,19 +392,32 @@@ static const struct dmi_system_id gpiol
.ignore_wake = "VEN_0488:00@355",
},
},
+ {
+ /*
+ * Lenovo IdeaPad Slim 3 15ABR8: the touchscreen wake IRQ fires as soon
+ * as the system enters suspend, causing an immediate spurious resume.
+ */
+ .matches = {
+ DMI_MATCH(DMI_SYS_VENDOR, "LENOVO"),
+ DMI_MATCH(DMI_PRODUCT_NAME, "82XM"),
+ },
+ .driver_data = &(struct acpi_gpiolib_dmi_quirk) {
+ .ignore_wake = "GTCH7503:00@10",
+ },
+ },
+ {
+ /*
+ * Spurious wakeups from GPP3 PCIe bridge interrupt
+ * Found in BIOS UX425UA.301
+ */
+ .matches = {
+ DMI_MATCH(DMI_SYS_VENDOR, "ASUSTeK COMPUTER INC."),
+ DMI_MATCH(DMI_PRODUCT_NAME, "ZenBook UX425UA_UM425UA"),
+ },
+ .driver_data = &(struct acpi_gpiolib_dmi_quirk) {
+ .ignore_wake = "AMDI0030:00@24",
+ },
+ },
{} /* Terminating entry */
};
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
reply other threads:[~2026-09-25 16:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=arac3fNw4DFKnguy@sirena.org.uk \
--to=broonie@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bartosz.golaszewski@oss.qualcomm.com \
--cc=brgl@bgdev.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mateob226@gmail.com \
--cc=vaknins33@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
all inboxes | Powered by JetHome®