Re: [PATCH] gpiolib: acpi: Ignore GPIO 11 interrupt on Acer Nitro V 16S AI

[Andy Shevchenko]

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.

-- 
With Best Regards,
Andy Shevchenko