Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Kris Kater <kris@kater.nu>
Cc: Takashi Iwai <tiwai@suse.com>, alsa-devel@alsa-project.org
Subject: Re: [PATCH] ALSA: hda/realtek: Add HDA_CODEC_QUIRK for Lenovo Yoga Slim 7 14AGP11
Date: Mon, 25 May 2026 09:21:41 +0200	[thread overview]
Message-ID: <87fr3ggdiy.wl-tiwai@suse.de> (raw)
In-Reply-To: <20260522060902.9423-1-kris@kater.nu>

On Fri, 22 May 2026 08:09:02 +0200,
Kris Kater wrote:
> 
> The BIOS on the Lenovo Yoga Slim 7 14AGP11 (AMD Ryzen AI / Kraken
> Point chassis; board LNVNB161216, product 83QS) programs the PCI
> subsystem ID of the HDA function as 17aa:0000. As a result no entry
> in alc269_fixup_tbl[] matches via SND_PCI_QUIRK, the fixup falls back
> to the generic auto-routing path, and the bass speaker pin is left
> mis-routed. Laptop speakers sound noticeably thin.
> 
> The codec's own internal subsystem ID register reports 0x17aa394c
> correctly, so an HDA_CODEC_QUIRK entry (which matches on the codec
> SSID rather than on the PCI SSID) binds the chassis to the existing
> ALC287_FIXUP_YOGA9_14IAP7_BASS_SPK_PIN fixup. This mirrors the same
> workaround already in place for the closely-related Yoga 7 2-in-1
> 14AKP10 and 16AKP10 entries earlier in the table.
> 
> With this change the kernel log goes from
> 
>   ALC287: picked fixup  for PCI SSID 17aa:0000
> 
> to
> 
>   ALC287: picked fixup alc287-yoga9-bass-spk-pin
> 
> and speaker routing matches what the firmware intended. Verified by
> the reporter against the equivalent modprobe override
> (model=,alc287-yoga9-bass-spk-pin).
> 
> Link: https://bugzilla.kernel.org/show_bug.cgi?id=221438
> Signed-off-by: Kris Kater <kris@kater.nu>

Applied now.  Thanks.


Takashi

           reply	other threads:[~2026-05-25  7:45 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20260522060902.9423-1-kris@kater.nu>]

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=87fr3ggdiy.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=kris@kater.nu \
    --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