All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Abduvaliy Abdulazizov <abduvaliy.hbai@gmail.com>
Cc: Mika Westerberg <westeri@kernel.org>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.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: Fri, 16 Oct 2026 07:26:02 +0200	[thread overview]
Message-ID: <20261016052602.GU176164@black.igk.intel.com> (raw)
In-Reply-To: <20261007120944.1705014-1-abduvaliy.hbai@gmail.com>

On Wed, Oct 07, 2026 at 05:09:44PM +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.
> 
> Booting with gpiolib_acpi.ignore_interrupt=AMDI0030:00@11 fixes both
> the camera and the microphones. Add a DMI quirk for this family too.
> 
> Tested-by: Trijan Koju <trijankoju11@gmail.com>
> Assisted-by: LLM
> Signed-off-by: Abduvaliy Abdulazizov <abduvaliy.hbai@gmail.com>

Acked-by: Mika Westerberg <westeri@kernel.org>

  reply	other threads:[~2026-10-16  5:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-07 12:09 [PATCH] gpiolib: acpi: Ignore GPIO 11 interrupt on Acer Nitro 16S AI Abduvaliy Abdulazizov
2026-10-16  5:26 ` Mika Westerberg [this message]
2026-10-16  9:02   ` Bartosz Golaszewski
2026-10-16 10:32     ` Mika Westerberg

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=20261016052602.GU176164@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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.