From: "Mukunda,Vijendar" <vijendar.mukunda@amd.com>
To: Zhang Heng <zhangheng@kylinos.cn>,
venkataprasad.potturu@amd.com, lgirdwood@gmail.com,
broonie@kernel.org, perex@perex.cz, tiwai@suse.com
Cc: linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org,
Syed Saba Kareem <Syed.SabaKareem@amd.com>,
"Dommati, Sunil-kumar" <Sunil-kumar.Dommati@amd.com>
Subject: Re: [PATCH] ASoC: amd: yc: Add DMI quirk for ASUS TUF Gaming A16 FA607NUQ
Date: Thu, 5 Nov 2026 11:28:23 +0530 [thread overview]
Message-ID: <8bf1a5de-0f7d-4db9-b607-d44979fdbb4f@amd.com> (raw)
In-Reply-To: <20261105015428.54091-1-zhangheng@kylinos.cn>
On 05/11/26 07:24, Zhang Heng wrote:
> [Some people who received this message don't often get email from zhangheng@kylinos.cn. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ]
>
> The ASUS TUF Gaming A16 FA607NUQ has an internal DMIC array connected
> to the AMD ACP 6.x PDM interface, but its BIOS does not configure the
> _WOV ACPI method correctly — it returns 0, causing the driver to
> return -ENODEV before the DMI quirk table is consulted.
>
> Not all BIOS implementations report _WOV correctly. The DMI quirk
> table already serves as a fallback for machines with broken ACPI
> values (the _WOV read-failure path already falls through to it).
> Extend the same fallback to the _WOV=0 case so that DMI overrides
> can take effect for machines whose BIOS reports _WOV incorrectly.
>
> Add a DMI entry for the ASUS TUF Gaming A16 FA607NUQ. After applying
> this fix, the internal DMIC is detected and captured from correctly
> on the affected machine.
This patch should be split into two patches:
1. Allow the _WOV=0 case to fall back to the DMI quirk table.
2. Add the DMI quirk for the ASUS TUF Gaming A16 FA607NUQ.
>
> Closes: https://bugzilla.kernel.org/show_bug.cgi?id=222214
> Signed-off-by: Zhang Heng <zhangheng@kylinos.cn>
> ---
> sound/soc/amd/yc/acp6x-mach.c | 9 ++++++++-
> 1 file changed, 8 insertions(+), 1 deletion(-)
>
> diff --git a/sound/soc/amd/yc/acp6x-mach.c b/sound/soc/amd/yc/acp6x-mach.c
> index 4908f4cc147a..fdeaedcfb178 100644
> --- a/sound/soc/amd/yc/acp6x-mach.c
> +++ b/sound/soc/amd/yc/acp6x-mach.c
> @@ -969,6 +969,13 @@ static const struct dmi_system_id yc_acp_quirk_table[] = {
> DMI_MATCH(DMI_PRODUCT_NAME, "HP 255R 15.6 inch G10 Notebook PC"),
> }
> },
> + {
> + .driver_data = &acp6x_card,
> + .matches = {
> + DMI_MATCH(DMI_BOARD_VENDOR, "ASUSTeK COMPUTER INC."),
> + DMI_MATCH(DMI_PRODUCT_NAME, "TUF Gaming A16 FA607NUQ"),
> + }
> + },
> {}
> };
>
> @@ -1000,7 +1007,7 @@ static int acp6x_probe(struct platform_device *pdev)
> if (!ACPI_FAILURE(ret)) {
> wov_en = dmic_status;
> if (!wov_en)
> - return -ENODEV;
> + goto check_dmi_entry;
> } else {
> /* Incase of ACPI method read failure then jump to check_dmi_entry */
> goto check_dmi_entry;
> --
> 2.25.1
prev parent reply other threads:[~2026-11-05 5:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-05 1:54 Zhang Heng
2026-11-05 5:58 ` Mukunda,Vijendar [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=8bf1a5de-0f7d-4db9-b607-d44979fdbb4f@amd.com \
--to=vijendar.mukunda@amd.com \
--cc=Sunil-kumar.Dommati@amd.com \
--cc=Syed.SabaKareem@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 \
--cc=zhangheng@kylinos.cn \
/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®