From: Takashi Iwai <tiwai@suse.de>
To: "刘 栋" <liudongxjtu@outlook.com>
Cc: "linux-sound@vger.kernel.org" <linux-sound@vger.kernel.org>,
"tiwai@suse.de" <tiwai@suse.de>,
"perex@perex.cz" <perex@perex.cz>
Subject: Re: ALSA: hda/conexant: Fix silent speaker on Huawei MateBook 14 (SN6140)
Date: Mon, 14 Sep 2026 18:04:40 +0200 [thread overview]
Message-ID: <87a4pjom3r.wl-tiwai@suse.de> (raw)
In-Reply-To: <ME3PR01MB7504E1F31E26F760F73DF639BDBD2@ME3PR01MB7504.ausprd01.prod.outlook.com>
On Sat, 12 Sep 2026 16:03:55 +0200,
刘 栋 wrote:
>
>
> Sir/Madam,
>
> On the Huawei MateBook 14 (PCI SSID 19e5:329e), the SN6140 codec
> silently routes the speaker output through the headphone pin's
> connection select: whatever DAC the headphone pin 0x16 is connected to,
> the speaker pin 0x17 follows. The generic parser attaches the playback
> stream to DAC 0x10 (shared by the headphone path) and mutes that DAC
> when no headphone is plugged, silencing the internal speaker while the
> headphone jack keeps working.
>
> Add a quirk for this machine that suppresses the auto-mute, binds the
> speaker pin to the shared DAC 0x10, removes the mute switch on that DAC
> so userspace cannot mute it, and re-applies the routing after every
> output update; at init it routes both pins to DAC 0x10, enables the
> speaker EAPD (which the driver otherwise leaves off) and unmutes the
> DAC.
>
> Note that this is a different problem than the existing Huawei
> Matebook quirk for SSID 19e5:3289 (commit d152afd1cd7a), which fixes a
> missing headphone jack; that machine has working speakers.
>
> Tested on Ubuntu 26.04 (kernels 7.0.0-30 and 7.0.0-31): the speaker
> plays at boot without any userspace helper, and keeps working across
> suspend/resume.
>
> Signed-off-by: liudongxjtu <liudongxjtu@outlook.com>
The patch can't be applied because your mailer broke the spaces.
Please try to resubmit with a fixed mailer setup; at best use
git-send-email.
About the patch: please drop the heading "Sir/Madam". The patch
description will be taken as the commit log as is, so such a greeting
doesn't fit at all.
Also, spelling your name in a bit more Western style (using
capital/lower letters and putting a space between first name and last
name) would be better.
thanks,
Takashi
next parent reply other threads:[~2026-09-14 16:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ME3PR01MB7504E1F31E26F760F73DF639BDBD2@ME3PR01MB7504.ausprd01.prod.outlook.com>
2026-09-14 16:04 ` Takashi Iwai [this message]
2026-09-19 13:46 ` ALSA: hda/conexant: Fix silent speaker on Huawei MateBook 14 (SN6140) 刘 栋
2026-09-28 13:59 ` Takashi Iwai
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=87a4pjom3r.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=linux-sound@vger.kernel.org \
--cc=liudongxjtu@outlook.com \
--cc=perex@perex.cz \
/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