Re: [BUG] 36-second boot delay due to by acpi_gpio_handle_deferred_request_irqs on ASUS ROG Strix G16 (2025)

[Mika Westerberg <mika.westerberg@linux.intel.com>]

On Sat, Apr 25, 2026 at 10:41:46PM +0200, Armin Wolf wrote:
> > > according to the Microsoft documentation
> > > (https://learn.microsoft.com/
> > > en-us/windows-hardware/drivers/bringup/general-purpose-i-o--gpio-,
> > > section "GPIO controllers and ActiveBoth interrupts"), triggering
> > > GPIO interrupts marked as ActiveBoth during initialization is
> > > correct as long as the associated GPIO line is already "asserted"
> > > (aka logic level low). I think the problem is that we also trigger
> > > edge-based GPIO interrupts _not_ marked as ActiveBoth.
> > > 
> > > Based on this i agree with Hans, except that we should continue you
> > > trigger ActiveBoth GPIO interrupts as long as the above
> > > condition applies.
> > > 
> > > Thanks,
> > > Armin Wolf
> > > 
> > 
> > So maybe something like this (attached)?
> 
> Yes, exactly.

This is good information and definitely scales better than the quirk list.
The linked document also mentions that there is _DSM under GPIO device that
could be used to override the asserted state:

https://learn.microsoft.com/en-us/windows-hardware/drivers/bringup/gpio-controller-device-specific-method---dsm-

I wonder if we should implement that as well?