All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: "Iván Ezequiel Rodriguez" <ivanrwcm25@gmail.com>
Cc: Takashi Iwai <tiwai@suse.com>, Jaroslav Kysela <perex@perex.cz>,
	linux-sound@vger.kernel.org, Kailang Yang <kailang@realtek.com>,
	Naser Al-Asbahi <nasserqahtan0@gmail.com>,
	stable@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ALSA: hda/realtek: keep headset mic on Acer SSID 0x1640
Date: Wed, 14 Oct 2026 08:05:20 +0200	[thread overview]
Message-ID: <87h5iog6lb.wl-tiwai@suse.de> (raw)
In-Reply-To: <20261013204219.9649-1-ivanrwcm25@gmail.com>

On Tue, 13 Oct 2026 22:42:19 +0200,
Iván Ezequiel Rodriguez wrote:
> 
> The micmute-LED quirk for the Aspire A315-44P matches PCI SSID
> 1025:1640 before the Acer ALC256 pin fallback. The Aspire Go 15
> AG15-42P shares that SSID and leaves nid 0x19 as 0x411111f0, so
> selecting the LED-only fixup drops the headset-mic pin remap that
> the fallback would have applied.
> 
> Chain ALC2XX_FIXUP_HEADSET_MIC before the GPIO3 micmute LED on that
> SSID. Leave the Swift SFG16 entry (0x169a) unchanged.
> 
> Tested on Acer Aspire AG15-42P (Callisto_BCU): PCI pick 1025:1640,
> Headset Mic=0x19, GPIO3 enabled with no physical micmute LED, speaker
> and capture paths functional.
> 
> Fixes: d830631a128b ("ALSA: hda/realtek: Add micmute LED quirk for Acer Aspire A315-44P")
> Cc: stable@vger.kernel.org
> Signed-off-by: Iván Ezequiel Rodriguez <ivanrwcm25@gmail.com>

Applied now to for-next branch (with a correction of
ALC256_FIXUP_ACER_HEADSET_MICMUTE_LED enum position, so that it can be
cleanly applied to stable trees).


thanks,

Takashi

      reply	other threads:[~2026-10-14  6:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-13 20:42 [PATCH] ALSA: hda/realtek: keep headset mic on Acer SSID 0x1640 Iván Ezequiel Rodriguez
2026-10-14  6:05 ` Takashi Iwai [this message]

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=87h5iog6lb.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=ivanrwcm25@gmail.com \
    --cc=kailang@realtek.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=nasserqahtan0@gmail.com \
    --cc=perex@perex.cz \
    --cc=stable@vger.kernel.org \
    --cc=tiwai@suse.com \
    /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.