From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>
Cc: Mika Westerberg <westeri@kernel.org>,
Abduvaliy Abdulazizov <abduvaliy.hbai@gmail.com>,
linux-gpio@vger.kernel.org, linux-acpi@vger.kernel.org,
Linus Walleij <linusw@kernel.org>,
Bartosz Golaszewski <brgl@kernel.org>,
linux-kernel@vger.kernel.org,
Trijan Koju <trijankoju11@gmail.com>
Subject: Re: [PATCH] gpiolib: acpi: Ignore GPIO 11 interrupt on Acer Nitro 16S AI
Date: Mon, 19 Oct 2026 16:29:11 +0300 [thread overview]
Message-ID: <atYbJ4ByzDb1mlOQ@ashevche-desk.local> (raw)
In-Reply-To: <179239686600.5748.7808377662325552771.b4-ty@oss.qualcomm.com>
On Mon, Oct 19, 2026 at 10:01:08AM +0200, Bartosz Golaszewski wrote:
> On Wed, 07 Oct 2026 17:09:44 +0500, Abduvaliy Abdulazizov wrote:
> > The Acer Nitro 16S AI (AN16S-61) has the same problem as the Acer Nitro
> > V 16S AI: the firmware powers the internal USB camera (0408:4059)
> > through GPIO 11 of AMDI0030, but also lists that pin in _AEI. Requesting
> > it as an input cuts the power, so the camera never enumerates. On this
> > model the same rail also powers the internal microphones, so they do
> > not work either.
[...]
> Applied, thanks!
>
> [1/1] gpiolib: acpi: Ignore GPIO 11 interrupt on Acer Nitro 16S AI
> https://git.kernel.org/brgl/c/5a088d1b7266249e7701a94fc90fc829d1ad5ba1
You actually applied my PT to for-next instead of for-current...
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-10-19 13:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-07 12:09 Abduvaliy Abdulazizov
2026-10-16 5:26 ` Mika Westerberg
2026-10-16 9:02 ` Bartosz Golaszewski
2026-10-16 10:32 ` Mika Westerberg
2026-10-19 8:01 ` Bartosz Golaszewski
2026-10-19 13:29 ` Andy Shevchenko [this message]
2026-10-19 15:09 ` Bartosz Golaszewski
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=atYbJ4ByzDb1mlOQ@ashevche-desk.local \
--to=andriy.shevchenko@linux.intel.com \
--cc=abduvaliy.hbai@gmail.com \
--cc=bartosz.golaszewski@oss.qualcomm.com \
--cc=brgl@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=trijankoju11@gmail.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
all inboxes | Powered by JetHome®