From: Takashi Iwai <tiwai@suse.de>
To: Guobing Yin <yinguobing@gmail.com>
Cc: alsa-devel@alsa-project.org, linux-sound@vger.kernel.org, perex@perex.cz
Subject: Re: [PATCH] ALSA: hda/realtek: Add quirk for Huawei WRT-WX9 (ALC256, 19e5:320d)
Date: Sat, 31 Oct 2026 16:52:29 +0100 [thread overview]
Message-ID: <8733tlsw8y.wl-tiwai@suse.de> (raw)
In-Reply-To: <CA+2LKoO7He4DciWnx7qcwndwpZNxA4R1FMTpXGSTVK_k9J6Svg@mail.gmail.com>
On Thu, 29 Oct 2026 09:13:31 +0100,
Guobing Yin wrote:
>
> Hi,
>
> this is a one-line quirk addition for a Huawei MateBook WRT-WX9 whose
> Realtek ALC256 codec reports subsystem ID 19e5:320d. The patch is
> attached.
>
> Problem: headphone insertion is never detected. The "Headphone Jack"
> control stays off, PipeWire keeps the speaker route selected, and audio
> comes out of the internal speakers and the headphones at the same time.
> Unplugging the headphones leaves the speakers working, so only insertion
> detection is broken.
>
> Cause: the existing quirk for this machine family is registered for
> 19e5:320f only, so this variant receives no fixup at all. Applying
> ALC269_FIXUP_HEADSET_MODE makes jack detection work.
>
> Evidence from the affected machine (kernel 7.0.0-38-generic):
>
> lspci -nn:
> 00:1f.3 Audio device [0403]: Intel Corporation Cannon Point-LP
> High Definition Audio Controller [8086:9dc8] (rev 30)
>
> codec: Realtek ALC256, vendor 0x10ec0256, subsystem 0x19e5320d
> DMI: HUAWEI WRT-WX9 / WRT-WX9-PCB, BIOS 1.39
>
> Without the fixup:
> $ amixer -c0 cget numid=12 | tail -1
> : values=off # headphones are plugged in
> $ hda-verb /dev/snd/hwC0D0 0x21 0x0f09 0x0
> value = 0x0 # pin sense never reports presence
> PipeWire: analog-output-headphones -> "not available"
>
> Booting with snd-hda-intel.model=headset-mode (the same
> ALC269_FIXUP_HEADSET_MODE fixup):
> $ amixer -c0 cget numid=12 | tail -1
> : values=on
> $ hda-verb /dev/snd/hwC0D0 0x21 0x0f09 0x0
> value = 0x80000000
> PipeWire: analog-output-headphones -> "available"; the speaker is
> muted automatically on insertion and unplugging restores speaker
> output.
>
> HDMI audio profiles and the internal microphone keep working with the
> fixup applied.
>
> The attached patch just maps 19e5:320d to that fixup.
>
> I am not subscribed to the list, please keep me in Cc.
>
> Thanks,
> yinguobing <yinguobing@gmail.com>
> From: yinguobing <yinguobing@gmail.com>
> Date: Thu, 29 Oct 2026 16:08:00 +0800
> Subject: [PATCH] ALSA: hda/realtek: Add quirk for Huawei WRT-WX9 (ALC256, 19e5:320d)
>
> On the Huawei MateBook WRT-WX9 whose ALC256 codec reports subsystem ID
> 19e5:320d, headphone jack presence detection never works: the
> "Headphone Jack" control stays off, PipeWire keeps the speaker route
> active, and audio plays from the internal speakers and the headphones at
> the same time. Unplugging the headphones leaves the speakers working, so
> only insertion detection is broken.
>
> The existing quirk for this machine family is registered for 19e5:320f
> only, so this variant receives no fixup at all. ALC256 on this board
> needs ALC269_FIXUP_HEADSET_MODE; without it the codec's jack detection is
> never enabled and GET_PIN_SENSE on the headphone pin (0x21) always reads 0.
>
> Verified on the affected machine by booting with
> snd-hda-intel.model=headset-mode, which applies the same fixup: the
> "Headphone Jack" control then reports "on" when a plug is inserted,
> GET_PIN_SENSE on pin 0x21 returns 0x80000000, the "Headphones" port
> becomes available in PipeWire, and the speaker is muted automatically on
> insertion. HDMI audio profiles and the internal microphone keep working.
>
> Add a SND_PCI_QUIRK entry for 19e5:320d using ALC269_FIXUP_HEADSET_MODE.
>
> Signed-off-by: yinguobing <yinguobing@gmail.com>
Applied now. Thanks.
Takashi
prev parent reply other threads:[~2026-10-31 15:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-29 8:13 [PATCH] ALSA: hda/realtek: Add quirk for Huawei WRT-WX9 (ALC256, 19e5:320d) Guobing Yin
2026-10-31 15:52 ` 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=8733tlsw8y.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=yinguobing@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.