Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: "Rámon van Raaij" <ramon@vanraaij.eu>
Cc: linux-sound@vger.kernel.org, alsa-devel@alsa-project.org
Subject: Re: [PATCH] ALSA: hda/realtek: Add codec SSID quirk for Lenovo Yoga Pro 9 16IMH9
Date: Fri, 01 May 2026 15:01:23 +0200	[thread overview]
Message-ID: <87fr4bl1wc.wl-tiwai@suse.de> (raw)
In-Reply-To: <20260430191224.patch1-ramon@vanraaij.eu>

On Thu, 30 Apr 2026 21:12:24 +0200,
Rámon van Raaij wrote:
> 
> The Yoga Pro 9 16IMH9 (codec SSID 17aa:38d6) shares PCI audio device
> subsystem ID 17aa:3811 with the Legion S7 15IMH05. The existing
> SND_PCI_QUIRK entry for the Legion routes both machines to
> ALC287_FIXUP_LEGION_15IMHG05_SPEAKERS, which does not bind the TAS2781
> smart amplifiers, resulting in near-silent built-in speakers.
> 
> Add an HDA_CODEC_QUIRK entry immediately before the conflicting PCI quirk
> that matches the Yoga Pro 9's unique codec SSID and routes it to
> ALC287_FIXUP_TAS2781_I2C. Codec quirks are evaluated after PCI quirks and
> take precedence, leaving the Legion S7 15IMH05 entry unaffected.
> 
> This follows the same pattern used to disambiguate PCI SSID 17aa:3847
> (shared between Yoga Pro 7 14IMH9 and Legion 7 16ACHG6), where a
> HDA_CODEC_QUIRK for codec SSID 17aa:38cf resolves the conflict.
> 
> Signed-off-by: Rámon van Raaij <ramon@vanraaij.eu>

Applied now.  Thanks.


Takashi

      reply	other threads:[~2026-05-01 13:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-30 19:12 [PATCH] ALSA: hda/realtek: Add codec SSID quirk for Lenovo Yoga Pro 9 16IMH9 Rámon van Raaij
2026-05-01 13:01 ` 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=87fr4bl1wc.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=ramon@vanraaij.eu \
    /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