mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: evgeny@devduty.com
Cc: Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
	linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org,
	David Rhodes <david.rhodes@cirrus.com>,
	Richard Fitzgerald <rf@opensource.cirrus.com>,
	patches@opensource.cirrus.com, stable@vger.kernel.org
Subject: Re: [PATCH] ALSA: hda/realtek: Enable all four speaker amps on Lenovo ThinkBook X G2 IAH
Date: Sat, 10 Oct 2026 09:59:46 +0200	[thread overview]
Message-ID: <87pkxij899.wl-tiwai@suse.de> (raw)
In-Reply-To: <20261009-thinkbook-x-g2-iah-v1-1-56012188aee0@devduty.com>

On Fri, 09 Oct 2026 18:02:37 +0200,
Evgeny Akhtimirov via B4 Relay wrote:
> 
> From: Evgeny Akhtimirov <evgeny@devduty.com>
> 
> The Lenovo ThinkBook X G2 IAH (MTM 21TU) has an ALC287 codec with four
> CS35L41 amplifiers on I2C (CSC3551). It reports codec SSID 17aa:3929,
> which it shares with the ThinkBook 13x Gen 5, and PCI SSID 17aa:3842.
> 
> Since PCI SSID 17aa:3842 has no quirk entry, the codec SSID matches
> ALC287_FIXUP_MG_RTKC_CSAMP_CS35L41_I2C_THINKPAD. That fixup binds only
> two amps (cs35l41-hda.0 and .1), while the CS35L41 configuration table
> describes four for 17AA3929. Amps .2 and .3 probe and load firmware,
> but they are never bound to the codec, so half of the speakers stay
> silent.
> 
> Add a ThinkPad-style fixup chain that binds four I2C amps, and match the
> laptop by its PCI SSID so the ThinkBook 13x Gen 5 is not affected.
> 
> Tested with hda_model=1028:0c4d (alias to ALC287_FIXUP_CS35L41_I2C_4):
> all four amps bind, apply their calibration and are runtime-active
> during playback.
> 
> Cc: stable@vger.kernel.org
> Signed-off-by: Evgeny Akhtimirov <evgeny@devduty.com>

Thanks, applied now.


Takashi

      reply	other threads:[~2026-10-10  7:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-09 16:02 Evgeny Akhtimirov via B4 Relay
2026-10-10  7:59 ` 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=87pkxij899.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=david.rhodes@cirrus.com \
    --cc=evgeny@devduty.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=patches@opensource.cirrus.com \
    --cc=perex@perex.cz \
    --cc=rf@opensource.cirrus.com \
    --cc=stable@vger.kernel.org \
    --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

all inboxes | Powered by JetHome®