All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Zhang Heng <zhangheng@kylinos.cn>
Cc: tiwai@suse.com, perex@perex.cz, kailang@realtek.com,
	linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org,
	Roman Maidanovych via B4 Relay
	<devnull+devuarpd.gmail.com@kernel.org>
Subject: Re: [PATCH 1/3] ALSA: hda/realtek: Fix DAC binding for Lenovo Legion Pro 7 16ARX8H
Date: Wed, 04 Nov 2026 15:41:53 +0100	[thread overview]
Message-ID: <87zevou09a.wl-tiwai@suse.de> (raw)
In-Reply-To: <20261104100427.474270-1-zhangheng@kylinos.cn>

On Wed, 04 Nov 2026 11:04:25 +0100,
Zhang Heng wrote:
> 
> The Lenovo Legion Pro 7 16ARX8H (SSID 17aa:38a7) uses the TAS2781
> I2C DAC. The generic ALC287_FIXUP_TAS2781_I2C quirk assumes two
> speakers (0x14 and 0x17). It forcibly binds 0x14 to DAC 0x02, and
> binds 0x17 and 0x21 to DAC 0x03.
> 
> However, this machine only has 0x17 as the speaker and lacks 0x14,
> which leads to incorrect DAC binding. To fix this, chain the
> alc295_fixup_asus_dacs() fixup before the generic quirk to ensure
> the correct DAC routing for this hardware layout.
> 
> Tested-by: Roman Maidanovych via B4 Relay <devnull+devuarpd.gmail.com@kernel.org>
> Link: https://bugzilla.kernel.org/show_bug.cgi?id=221735
> Signed-off-by: Zhang Heng <zhangheng@kylinos.cn>

Applied all three patches now.  Thanks.


Takashi

      parent reply	other threads:[~2026-11-04 14:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-04 10:04 [PATCH 1/3] ALSA: hda/realtek: Fix DAC binding for Lenovo Legion Pro 7 16ARX8H Zhang Heng
2026-11-04 10:04 ` [PATCH 2/3] ALSA: hda/realtek: Fix DAC binding for Legion Pro 7 16ARX8H variant Zhang Heng
2026-11-04 10:04 ` [PATCH 3/3] ALSA: hda/realtek: Fix pop noise on ASUS PRIME B650M-K Zhang Heng
2026-11-04 14:41 ` 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=87zevou09a.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=devnull+devuarpd.gmail.com@kernel.org \
    --cc=kailang@realtek.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=perex@perex.cz \
    --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 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.