From: Takashi Iwai <tiwai@suse.de>
To: chris@nilk.net
Cc: Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] ALSA: hda/realtek: Enable bass speakers on Alienware m17 R3
Date: Sat, 31 Oct 2026 17:05:03 +0100 [thread overview]
Message-ID: <87se1lrh3k.wl-tiwai@suse.de> (raw)
In-Reply-To: <20261029-alc289-m17r3-v1-1-5d3eac605e7a@nilk.net>
On Thu, 29 Oct 2026 23:49:10 +0100,
Chris Simpson via B4 Relay wrote:
>
> From: Chris Simpson <chris@nilk.net>
>
> The Alienware m17 R3 (ALC289, PCI SSID 1028:09d1) has a second speaker
> pair, the bass speakers, on pin 0x17, which the BIOS leaves unconnected
> (0x411111f0). No PCI SSID quirk matches the machine, so it gets
> ALC269_FIXUP_DELL4_MIC_NO_PRESENCE from the fallback pin quirk table,
> and only the speakers on pin 0x14 play.
>
> Use ALC289_FIXUP_DUAL_SPK, as on the Alienware x16 R2 and Dell XPS 15
> 9510/9520: it sets pin 0x17 up as a speaker on DAC 0x02, so one volume
> control covers both pairs, and chains to
> ALC269_FIXUP_DELL4_MIC_NO_PRESENCE, so the headset mic setup is
> unchanged.
>
> Tested on an Alienware m17 R3 (BIOS 1.38.0), Linux 7.3 with this change
> applied: the bass speakers play, and volume and mute cover both pairs,
> also after suspend and resume. Headphones and a headset mic were not
> tested.
>
> I used Claude Code (Claude Opus 5.5) to find the unused pin, pick the
> existing fixup and write this patch and changelog; I did the listening
> tests myself.
>
> Cc: stable@vger.kernel.org
> Assisted-by: LLM
> Signed-off-by: Chris Simpson <chris@nilk.net>
Applied now. Thanks.
Takashi
prev parent reply other threads:[~2026-10-31 16:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-29 22:49 Chris Simpson via B4 Relay
2026-10-31 16:05 ` 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=87se1lrh3k.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=chris@nilk.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--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®