From: Samuel Leyva <samuelslg03idk@gmail.com>
To: broonie@kernel.org
Cc: Vijendar.Mukunda@amd.com, venkataprasad.potturu@amd.com,
lgirdwood@gmail.com, perex@perex.cz, tiwai@suse.com,
linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org,
Samuel Leyva <samuelslg03idk@gmail.com>
Subject: [PATCH v2 0/2] ASoC: amd: acp: Support Huawei MateBook D 14 (NBM-WXX9)
Date: Sat, 7 Nov 2026 17:22:23 -0600 [thread overview]
Message-ID: <20261107232225.3838-1-samuelslg03idk@gmail.com> (raw)
The Huawei MateBook D 14 AMD (NBM-WXX9) has the same ES8336 + ACP3x
audio layout as the already supported BOM-WXX9, but is missing from
the DMI tables, so only the DMIC-only driver binds and the speakers
do not work.
Patch 1 adds the DMI quirk.
Patch 2 greatly reduces a pop heard every time the speaker output powers
up (a faint one is still audible on this machine):
the speaker amplifier GPIO was driven from a SUPPLY widget, which DAPM
enables before the codec output. It is independent of patch 1.
Both were tested as an out-of-tree DKMS module on the NBM-WXX9.
Changes in v2:
- Patch 2: only move the speaker amplifier to the endpoint widget.
The Headphone widget shares its power-up rank with the ES8316 output
drivers, so the reordering did not hold for headphones (Sashiko).
- Patch 2: use braces on both if/else branches (Sashiko).
- Patch 2: add Fixes tag (Sashiko).
- Patch 1: unchanged.
Samuel Leyva (2):
ASoC: amd: acp: Add DMI quirk for Huawei MateBook D 14 (NBM-WXX9)
ASoC: amd: acp: es83xx: Enable speaker amplifier after the codec
output
sound/soc/amd/acp-config.c | 14 +++++++++++
sound/soc/amd/acp/acp3x-es83xx/acp3x-es83xx.c | 24 +++++++++++++------
2 files changed, 31 insertions(+), 7 deletions(-)
--
2.56.0
next reply other threads:[~2026-11-07 23:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-07 23:22 Samuel Leyva [this message]
2026-11-07 23:22 ` [PATCH v2 1/2] ASoC: amd: acp: Add DMI quirk for " Samuel Leyva
2026-11-07 23:22 ` [PATCH v2 2/2] ASoC: amd: acp: es83xx: Enable speaker amplifier after the codec output Samuel Leyva
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=20261107232225.3838-1-samuelslg03idk@gmail.com \
--to=samuelslg03idk@gmail.com \
--cc=Vijendar.Mukunda@amd.com \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.com \
--cc=venkataprasad.potturu@amd.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®