[PATCH] ASoC: amd: yc: Add quirk for ASUS Vivobook S15 M3502RA

[PATCH] ASoC: amd: yc: Add quirk for ASUS Vivobook S15 M3502RA

[Christian Heusel]

As reported the builtin microphone doesn't work on the ASUS Vivobook
model S15 OLED M3502RA. Therefore add a quirk for it to make it work.

Link: https://bugzilla.kernel.org/show_bug.cgi?id=219345
Signed-off-by: Christian Heusel <christian@heusel.eu>
---
Note that I do not have the relevant hardware since I'm sending in this
quirk at the request of someone else.

Also does this change need a "Fixes: ..." tag?
---
 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 06349bf0b65874321e1c54afcff50417cdc9248c..e353542dcf636b5e38db89af532a73c55e29de51 100644
--- a/sound/soc/amd/yc/acp6x-mach.c
+++ b/sound/soc/amd/yc/acp6x-mach.c
@@ -339,6 +339,13 @@ static const struct dmi_system_id yc_acp_quirk_table[] = {
 			DMI_MATCH(DMI_PRODUCT_NAME, "M7600RE"),
 		}
 	},
+	{
+		.driver_data = &acp6x_card,
+		.matches = {
+			DMI_MATCH(DMI_BOARD_VENDOR, "ASUSTeK COMPUTER INC."),
+			DMI_MATCH(DMI_PRODUCT_NAME, "M3502RA"),
+		}
+	},
 	{
 		.driver_data = &acp6x_card,
 		.matches = {

---
base-commit: 9852d85ec9d492ebef56dc5f229416c925758edc
change-id: 20241010-bugzilla-219345-asus-vivobook-5d5e371e7b45

Best regards,
--
Christian Heusel <christian@heusel.eu>

Re: [PATCH] ASoC: amd: yc: Add quirk for ASUS Vivobook S15 M3502RA

[Mark Brown]

On Thu, 10 Oct 2024 15:32:11 +0200, Christian Heusel wrote:
> As reported the builtin microphone doesn't work on the ASUS Vivobook
> model S15 OLED M3502RA. Therefore add a quirk for it to make it work.
> 
> 

Applied to

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

Thanks!

[1/1] ASoC: amd: yc: Add quirk for ASUS Vivobook S15 M3502RA
      commit: 182fff3a2aafe4e7f3717a0be9df2fe2ed1a77de

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