From: Takashi Iwai <tiwai@suse.de>
To: Damien Laine <damien.laine@gmail.com>
Cc: Takashi Iwai <tiwai@suse.com>, Jaroslav Kysela <perex@perex.cz>,
linux-sound@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] ALSA: hda/realtek: Fix speakers on Legion Pro 7 16ARX8H with codec SSID 17aa:38a7
Date: Mon, 13 Jul 2026 12:05:40 +0200 [thread overview]
Message-ID: <87se5nyzkb.wl-tiwai@suse.de> (raw)
In-Reply-To: <20260712213708.1835469-1-damien.laine@gmail.com>
On Sun, 12 Jul 2026 23:37:08 +0200,
Damien Laine wrote:
>
> Some units of the Lenovo Legion Pro 7 16ARX8H (82WS) report codec
> subsystem ID 17aa:38a7 instead of 17aa:38a8. Since only 38a8 has a
> codec SSID quirk, these machines fall through to the PCI SSID match
> 17aa:386f (Legion Pro 7i 16IAX7) and get ALC287_FIXUP_CS35L41_I2C_2,
> which probes the Cirrus amplifiers of the Intel variant. The TI
> TAS2781 amplifier (ACPI TIAS2781:00) present on this AMD variant is
> never bound and the internal speakers remain silent.
>
> Add a codec SSID quirk for 17aa:38a7 pointing to
> ALC287_FIXUP_TAS2781_I2C, mirroring the existing 38a8 entry.
>
> Tested on a Legion Pro 7 16ARX8H (82WS, BIOS LPCN62WW): with the codec
> SSID overridden to 17aa:38a8 via the HDA patch loader, the TAS2781
> amplifier binds and the internal speakers work.
>
> Cc: <stable@vger.kernel.org>
> Signed-off-by: Damien Laine <damien.laine@gmail.com>
Applied now. Thanks.
Takashi
prev parent reply other threads:[~2026-07-13 10:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-12 21:37 [PATCH] ALSA: hda/realtek: Fix speakers on Legion Pro 7 16ARX8H with codec SSID 17aa:38a7 Damien Laine
2026-07-13 10: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=87se5nyzkb.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=damien.laine@gmail.com \
--cc=linux-sound@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox