The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Zhang Heng <zhangheng@kylinos.cn>
Cc: tiwai@suse.com, linux-sound@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] ALSA: hda/realtek: Fix bass speaker DAC routing for Lenovo Yoga Pro 9 16IAH10
Date: Thu, 20 Aug 2026 15:44:16 +0200	[thread overview]
Message-ID: <87v794lxe7.wl-tiwai@suse.de> (raw)
In-Reply-To: <20260820130644.76093-1-zhangheng@kylinos.cn>

On Thu, 20 Aug 2026 15:06:43 +0200,
Zhang Heng wrote:
> 
> The Lenovo Yoga Pro 9 16IAH10 (PCI SSID 17aa:3846, codec SSID 17aa:3920)
> uses a TAS2781 smart amplifier driven via the ALC287 codec.  On this
> machine the bass speaker pin (NID 0x17) is by default routed to DAC 0x03,
> which has no volume amplifier capability, resulting in the right-side
> woofer being barely audible while only the tweeter plays.  The Windows
> driver configures NID 0x17 to DAC 0x02, which is shared with the main
> speaker and carries proper amp control.
> 
> Currently this machine has no PCI SSID quirk, so it falls through to the
> codec SSID fallback and matches the existing 0x17aa:0x3920 entry intended
> for the Yoga S990-16, applying only the TAS2781 I2C init without the DAC
> routing fix.
> 
> Add a dedicated quirk for PCI SSID 17aa:3846 that forces NID 0x17 to DAC
> 0x02 via alc285_fixup_speaker2_to_dac1() and chains to
> ALC287_FIXUP_TXNW2781_I2C so the TAS2781 amplifier initialization is
> preserved.
> 
> Link: https://bugzilla.kernel.org/show_bug.cgi?id=220540
> Signed-off-by: Zhang Heng <zhangheng@kylinos.cn>

Applied both patches now.  Thanks.


Takashi

      parent reply	other threads:[~2026-08-20 13:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-20 13:06 [PATCH 1/2] ALSA: hda/realtek: Fix bass speaker DAC routing for Lenovo Yoga Pro 9 16IAH10 Zhang Heng
2026-08-20 13:06 ` [PATCH 2/2] ALSA: hda/realtek: Reorder quirk entries for Lenovo Legion Pro 7 16ARX8H Zhang Heng
2026-08-20 13:44 ` 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=87v794lxe7.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=tiwai@suse.com \
    --cc=zhangheng@kylinos.cn \
    /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