Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Kamlesh Chhetty <kamleshkc2002@gmail.com>
Cc: Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
	David Rhodes <david.rhodes@cirrus.com>,
	Richard Fitzgerald <rf@opensource.cirrus.com>,
	linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org,
	patches@opensource.cirrus.com
Subject: Re: [PATCH] ALSA: hda: Add Lenovo Legion 7i 16IAX7 17AA3874 quirk
Date: Thu, 25 Jun 2026 13:54:02 +0200	[thread overview]
Message-ID: <87a4sivns5.wl-tiwai@suse.de> (raw)
In-Reply-To: <20260622172247.19301-1-kamleshkc2002@gmail.com>

On Mon, 22 Jun 2026 19:22:47 +0200,
Kamlesh Chhetty wrote:
> 
> Lenovo Legion 7i 16IAX7 systems with Realtek ALC287 codec SSID
> 17aa:3874 and CSC3551/CS35L41 speaker amps do not provide the
> required CS35L41 _DSD properties in ACPI.
> 
> Without a quirk, cs35l41-hda fails probing the amps with missing
> cirrus,dev-index / Platform not supported errors, leaving the built-in
> speakers silent.
> 
> This model is similar to the already-supported 17AA386F Legion 7i
> 16IAX7 variant. Add the Realtek ALC287 quirk to select
> ALC287_FIXUP_CS35L41_I2C_2 and add 17AA3874 to the CS35L41 property
> table using the same two-amp external-boost configuration.
> 
> Tested on a Lenovo Legion 7 16IAX7 with Ubuntu 7.0.0-22-generic. Both
> CSC3551 CS35L41 amps probe and bind, firmware loads, calibration
> applies, built-in speaker playback works, and the cirrus,dev-index
> failure is gone.
> 
> Closes: https://bugzilla.kernel.org/show_bug.cgi?id=221663
> Link: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2157060
> Signed-off-by: Kamlesh Chhetty <kamleshkc2002@gmail.com>

Applied now.  Thanks.


Takashi

      reply	other threads:[~2026-06-25 11:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-22 17:22 [PATCH] ALSA: hda: Add Lenovo Legion 7i 16IAX7 17AA3874 quirk Kamlesh Chhetty
2026-06-25 11:54 ` 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=87a4sivns5.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=david.rhodes@cirrus.com \
    --cc=kamleshkc2002@gmail.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=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