From: Mario Limonciello <mario.limonciello@amd.com>
To: Ihor Uzlov <igor.uzlov@gmail.com>,
Vijendar.Mukunda@amd.com, lgirdwood@gmail.com,
broonie@kernel.org
Cc: venkataprasad.potturu@amd.com, perex@perex.cz, tiwai@suse.com,
linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ASoC: amd: yc: Add MSI Vector A16 HX A8WHG to quirk table
Date: Fri, 10 Apr 2026 08:14:19 -0500 [thread overview]
Message-ID: <f95444d2-44dd-4a25-93e3-85c11276d876@amd.com> (raw)
In-Reply-To: <20260410094553.24654-1-igor.uzlov@gmail.com>
On 4/10/26 04:45, Ihor Uzlov wrote:
> [You don't often get email from igor.uzlov@gmail.com. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ]
>
> Add the MSI Vector A16 HX A8WHG (board MS-15MM) to the DMI quirk table
> to enable DMIC support. This laptop uses an AMD Ryzen 9 7945HX (Dragon
> Range) with the ACP6x audio coprocessor (rev 0x62) and a Realtek ALC274
> codec. The built-in digital microphone is connected via the ACP PDM
> interface and requires this DMI entry to be activated.
>
> Tested on MSI Vector A16 HX A8WHG with kernel 6.8.0-107 (Ubuntu 24.04).
> DMIC capture device appears as 'acp6x' and records audio correctly.
>
If this system is dragon range, I'm not sure that is the completely
right location.
Shouldn't it be using the IOD from Raphael (IE rpl-pci-acp6x)?
> Signed-off-by: Ihor Uzlov <igor.uzlov@gmail.com>
> ---
> sound/soc/amd/yc/acp6x-mach.c | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/sound/soc/amd/yc/acp6x-mach.c b/sound/soc/amd/yc/acp6x-mach.c
> index 85579c81378f..c5cf45881416 100644
> --- a/sound/soc/amd/yc/acp6x-mach.c
> +++ b/sound/soc/amd/yc/acp6x-mach.c
> @@ -500,6 +500,13 @@ static const struct dmi_system_id yc_acp_quirk_table[] = {
> DMI_MATCH(DMI_PRODUCT_NAME, "Bravo 17 D7VF"),
> }
> },
> + {
> + .driver_data = &acp6x_card,
> + .matches = {
> + DMI_MATCH(DMI_BOARD_VENDOR, "Micro-Star International Co., Ltd."),
> + DMI_MATCH(DMI_PRODUCT_NAME, "Vector A16 HX A8WHG"),
> + }
> + },
> {
> .driver_data = &acp6x_card,
> .matches = {
> --
> 2.43.0
>
prev parent reply other threads:[~2026-04-10 13:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-10 9:45 Ihor Uzlov
2026-04-10 10:31 ` Mark Brown
2026-04-10 13:14 ` Mario Limonciello [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=f95444d2-44dd-4a25-93e3-85c11276d876@amd.com \
--to=mario.limonciello@amd.com \
--cc=Vijendar.Mukunda@amd.com \
--cc=broonie@kernel.org \
--cc=igor.uzlov@gmail.com \
--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®