From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Abduvaliy Abdulazizov <abduvaliy.hbai@gmail.com>,
Mika Westerberg <westeri@kernel.org>,
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
Subject: Re: [PATCH] gpiolib: acpi: Ignore GPIO 11 interrupt on Acer Nitro V 16S AI
Date: Fri, 2 Oct 2026 15:04:24 +0200 [thread overview]
Message-ID: <20261002130424.GG176164@black.igk.intel.com> (raw)
In-Reply-To: <ar-qbsmktRJbFoF-@ashevche-desk.local>
On Fri, Oct 02, 2026 at 03:58:22PM +0300, Andy Shevchenko wrote:
> On Fri, Oct 02, 2026 at 05:17:02PM +0500, Abduvaliy Abdulazizov wrote:
> > On Fri, Oct 02, 2026, Andy Shevchenko wrote:
> > > On Fri, Oct 02, 2026 at 03:18:00PM +0500, Abduvaliy Abdulazizov wrote:
> > > > On the Acer Nitro V 16S AI (ANV16S-41) the internal USB camera
> > > > (0408:4035) works on Windows but never shows up on Linux.
> > >
> > > While this all sounds legit, I'm worrying that the pin can be used for
> > > something more. For the record, can you share the DSDT table (or entire
> > > `acpidump -o NitroV16S.dat` file) via some file exchanger so we may see
> > > that?
> >
> > Sure, here is the full acpidump (BIOS V1.14):
> > https://github.com/abduvaliy-engineer/acer-nitro-anv16s-camera-fix/releases/download/acpidump-v1.14/NitroV16S.dat
> >
> > What I found when going through it:
> >
> > - Pin 0x0B shows up only once, in \_SB.GPIO._AEI, as
> > GpioInt (Edge, ActiveLow, ExclusiveAndWake, PullNone). Its _EVT case
> > only does M000 (0x390B), with no Notify.
> >
> > - There is no GpioIo for it, and none of the M009/M010/M011 GPIO helpers
> > are called with 0x0B. The only static mapping of the GPIO bank in the
> > DSDT (OperationRegion GSMG at 0xFED81500) has fields for pins 23 and
> > 40 only.
> >
> > - The PCIe reset pins in the NVMe SSDTs (RSTM) are computed at runtime
> > from a platform table. Pin 11 is not one of them on this machine: it
> > reads low after Linux takes it, and both NVMe drives keep working.
> >
> > So as far as I can see, the firmware drives the pin as an output for the
> > camera and lists it in _AEI without a real handler.
>
> Thanks for sharing. I will wait for Mika's tag and apply if he has no
> objections.
No objections,
Acked-by: Mika Westerberg <westeri@kernel.org>
next prev parent reply other threads:[~2026-10-02 13:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-02 10:18 Abduvaliy Abdulazizov
2026-10-02 10:37 ` Andy Shevchenko
[not found] ` <CAPGafd=-SfJoVMXtjwpahEkZ8nB9gTjGm+C5WvP+F-AdjsGPjg@mail.gmail.com>
2026-10-02 12:58 ` Andy Shevchenko
2026-10-02 13:04 ` Mika Westerberg [this message]
2026-10-02 13:22 ` 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=20261002130424.GG176164@black.igk.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=abduvaliy.hbai@gmail.com \
--cc=andriy.shevchenko@linux.intel.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=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®