All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Alexander Savenko <alex.sav4387@gmail.com>
Cc: alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ALSA: hda/realtek: Add quirk for Lenovo Yoga Pro 7 14IMH9
Date: Tue, 31 Mar 2026 16:21:50 +0200	[thread overview]
Message-ID: <87bjg4rse9.wl-tiwai@suse.de> (raw)
In-Reply-To: <20260331082929.44890-1-alex.sav4387@gmail.com>

On Tue, 31 Mar 2026 10:29:28 +0200,
Alexander Savenko wrote:
> 
> The Lenovo Yoga Pro 7 14IMH9 (DMI: 83E2) shares PCI SSID 17aa:3847
> with the Legion 7 16ACHG6, but has a different codec subsystem ID
> (17aa:38cf). The existing SND_PCI_QUIRK for 17aa:3847 applies
> ALC287_FIXUP_LEGION_16ACHG6, which attempts to initialize an external
> I2C amplifier (CLSA0100) that is not present on the Yoga Pro 7 14IMH9.
> 
> As a result, pin 0x17 (bass speakers) is connected to DAC 0x06 which
> has no volume control, making hardware volume adjustment completely
> non-functional. Audio is either silent or at maximum volume regardless
> of the slider position.
> 
> Add a HDA_CODEC_QUIRK entry using the codec subsystem ID (17aa:38cf)
> to correctly identify the Yoga Pro 7 14IMH9 and apply
> ALC287_FIXUP_YOGA9_14IMH9_BASS_SPK_PIN, which redirects pin 0x17 to
> DAC 0x02 and restores proper volume control. The existing Legion entry
> is preserved unchanged.
> 
> This follows the same pattern used for 17aa:386e, where Legion Y9000X
> and Yoga Pro 7 14ARP8 share a PCI SSID but are distinguished via
> HDA_CODEC_QUIRK.
> 
> Link: https://github.com/nomad4tech/lenovo-yoga-pro-7-linux
> Tested-by: Alexander Savenko <alex.sav4387@gmail.com>
> Signed-off-by: Alexander Savenko <alex.sav4387@gmail.com>

Applied now.  Thanks.


Takashi

      reply	other threads:[~2026-03-31 14:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-31  8:29 [PATCH] ALSA: hda/realtek: Add quirk for Lenovo Yoga Pro 7 14IMH9 Alexander Savenko
2026-03-31 14:21 ` 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=87bjg4rse9.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alex.sav4387@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=linux-kernel@vger.kernel.org \
    /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.