Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Moritz Baron <moritz.baron@stud.uni-hannover.de>
Cc: tiwai@suse.com, perex@perex.cz, linux-sound@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-kernel@i4.cs.fau.de,
	Felix Aljoscha Schnuell
	<felix.aljoscha.schnuell@stud.uni-hannover.de>
Subject: Re: [PATCH v2] ALSA: hda/realtek: Add quirk for Lenovo Yoga Pro 7 14IRH8
Date: Wed, 10 Jun 2026 09:24:13 +0200	[thread overview]
Message-ID: <87wlw66eoy.wl-tiwai@suse.de> (raw)
In-Reply-To: <20260609141648.60608-1-moritz.baron@stud.uni-hannover.de>

On Tue, 09 Jun 2026 16:16:48 +0200,
Moritz Baron wrote:
> 
> The Lenovo Yoga Pro 7 14IRH8 (ALC287 codec, subsystem ID 0x17aa:0x38b1)
> has bass speakers on pin 0x17 that are not routed through a DAC with
> volume control. This causes the bass speakers to play at full volume
> regardless of the volume slider position.
> 
> Apply ALC287_FIXUP_YOGA9_14IAP7_BASS_SPK_PIN which corrects the DAC
> routing for pin 0x17, enabling proper volume control. This is the same
> fix used for other Yoga Pro 7 models with identical audio topology
> (14APH8, 14AHP9, 14ASP10, 14IAH10).
> 
> Link: https://bugzilla.kernel.org/show_bug.cgi?id=217949
> 
> Co-developed-by: Felix Aljoscha Schnuell <felix.aljoscha.schnuell@stud.uni-hannover.de>
> Signed-off-by: Felix Aljoscha Schnuell <felix.aljoscha.schnuell@stud.uni-hannover.de>
> Signed-off-by: Moritz Baron <moritz.baron@stud.uni-hannover.de>
> ---
> v2: Move the quirk entry before 17aa:3852 and add a comment to
>     clarify the PCI SSID conflict, as suggested by Takashi Iwai.

Applied to for-next branch now.  Thanks.


Takashi

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

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-08 20:20 [PATCH] ALSA: hda/realtek: Add quirk for Lenovo Yoga Pro 7 14IRH8 Moritz Baron
2026-06-09 10:54 ` Takashi Iwai
2026-06-09 14:16   ` [PATCH v2] " Moritz Baron
2026-06-10  7:24     ` 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=87wlw66eoy.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=felix.aljoscha.schnuell@stud.uni-hannover.de \
    --cc=linux-kernel@i4.cs.fau.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=moritz.baron@stud.uni-hannover.de \
    --cc=perex@perex.cz \
    --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