[PATCH] ASoC: amd: acp: add ACP70 DMI override for new ASUS TUF platforms

Syed Saba Kareem posted 1 patch 2 weeks, 1 day ago
sound/soc/amd/acp-config.c | 12 ++++++++++++
1 file changed, 12 insertions(+)
[PATCH] ASoC: amd: acp: add ACP70 DMI override for new ASUS TUF platforms
Posted by Syed Saba Kareem 2 weeks, 1 day ago
From: Syed Saba Kareem <Syed.SabaKareem@amd.com>

Some ASUS TUF ACP70-based systems expose ACP ACPI configuration flags
that select a non-working fallback audio path, similar to previously
affected ASUS platforms.

Add DMI-based overrides in snd_amd_acp_find_config() for the following
systems to skip ACP ACPI flag-based selection:

  - ASUS TUF Gaming Vivobook 18
  - ASUS TUF Gaming A14 FA401EA

This ensures the intended SoundWire-based machine driver is selected on
these platforms.

Signed-off-by: Syed Saba Kareem <Syed.SabaKareem@amd.com>
---
 sound/soc/amd/acp-config.c | 12 ++++++++++++
 1 file changed, 12 insertions(+)

diff --git a/sound/soc/amd/acp-config.c b/sound/soc/amd/acp-config.c
index 93a2182d4e86..f4c1bae878c1 100644
--- a/sound/soc/amd/acp-config.c
+++ b/sound/soc/amd/acp-config.c
@@ -44,6 +44,18 @@ static const struct dmi_system_id acp70_acpi_flag_override_table[] = {
 			DMI_MATCH(DMI_PRODUCT_NAME, "83W5"),
 		},
 	},
+	{
+		.matches = {
+			DMI_MATCH(DMI_BOARD_VENDOR, "ASUSTeK COMPUTER INC"),
+			DMI_MATCH(DMI_PRODUCT_NAME, "TUF Gaming A14 FA401EA"),
+		},
+	},
+	{
+		.matches = {
+			DMI_MATCH(DMI_BOARD_VENDOR, "ASUSTeK COMPUTER INC"),
+			DMI_MATCH(DMI_PRODUCT_NAME, "Vivobook 18 M1807GA"),
+		},
+	},
 	{}
 };
 
-- 
2.43.0
Re: [PATCH] ASoC: amd: acp: add ACP70 DMI override for new ASUS TUF platforms
Posted by Mark Brown 1 week, 5 days ago
On Fri, 10 Jul 2026 15:59:19 +0530, Syed Saba Kareem wrote:
> ASoC: amd: acp: add ACP70 DMI override for new ASUS TUF platforms

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-7.2

Thanks!

[1/1] ASoC: amd: acp: add ACP70 DMI override for new ASUS TUF platforms
      https://git.kernel.org/broonie/sound/c/27d090f3ccd4

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark