From: "James X. Nelson" <james@wetheinter.net>
To: Vijendar.Mukunda@amd.com, broonie@kernel.org
Cc: venkataprasad.potturu@amd.com, lgirdwood@gmail.com,
perex@perex.cz, tiwai@suse.com, linux-sound@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH] ASoC: amd: yc: Enable DMIC on MSI Crosshair A18 HX A8WGKG
Date: Sat, 21 Nov 2026 21:46:11 -0600 [thread overview]
Message-ID: <20261122034611.26008-1-James@WeTheInter.net> (raw)
On the MSI Crosshair A18 HX A8WGKG (MS-184L), the ACP6x PCI
function binds and the DMIC platform devices are created, but the
machine driver does not register the capture card through the
firmware detection path.
Add an exact DMI match so the existing ACP6x machine driver exposes
the internal microphone on this model, without affecting other MSI
models.
Tested on an A8WGKG, board MS-184L, BIOS E184LAMS.10B with Ubuntu OEM
7.3.0-1004-oem. The patched module logged "Enabling ACP DMIC support
via DMI", and ALSA enumerated the DMIC capture device. After
WirePlumber reprobed the audio card, speech from the built-in
microphone was captured in Google Meet.
ChatGPT/Codex helped diagnose the driver binding failure and draft
the quirk and this changelog. The submitter performed the live
microphone test.
Link: https://bugs.launchpad.net/bugs/2175499
Signed-off-by: James X. Nelson <James@WeTheInter.net>
---
sound/soc/amd/yc/acp6x-mach.c | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/sound/soc/amd/yc/acp6x-mach.c b/sound/soc/amd/yc/acp6x-mach.c
index 1be8504..bfe69ca 100644
--- a/sound/soc/amd/yc/acp6x-mach.c
+++ b/sound/soc/amd/yc/acp6x-mach.c
@@ -556,6 +556,14 @@ static const struct dmi_system_id yc_acp_quirk_table[] = {
DMI_MATCH(DMI_PRODUCT_NAME, "Crosshair A16 HX D7WFKG"),
}
},
+ {
+ .driver_data = &acp6x_card,
+ .matches = {
+ DMI_EXACT_MATCH(DMI_BOARD_VENDOR, "Micro-Star International Co., Ltd."),
+ DMI_EXACT_MATCH(DMI_BOARD_NAME, "MS-184L"),
+ DMI_EXACT_MATCH(DMI_PRODUCT_NAME, "Crosshair A18 HX A8WGKG"),
+ }
+ },
{
.driver_data = &acp6x_card,
.matches = {
--
2.53.0
reply other threads:[~2026-11-22 3:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20261122034611.26008-1-James@WeTheInter.net \
--to=james@wetheinter.net \
--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®