[PATCH] ASoC: amd: yc: Add DMI quirk for MSI Bravo 15 C7VF

[PATCH] ASoC: amd: yc: Add DMI quirk for MSI Bravo 15 C7VF

[Bagas Sanjaya]

From: Techno Mooney <techno.mooney@gmail.com>

The laptop requires a quirk ID to enable its internal microphone. Add
it to the DMI quirk table.

Reported-by: Techno Mooney <techno.mooney@gmail.com>
Closes: https://bugzilla.kernel.org/show_bug.cgi?id=218402
Cc: stable@vger.kernel.org
Signed-off-by: Techno Mooney <techno.mooney@gmail.com>
Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
---
 I'm not sure about reporter's identity (which also authored the quirk
 patch), hence I derived his name instead.

 Techno Mooney: is it OK to use above Reported-by: identity as-is?
 Developers: In this case, is it better to just use
 `Reported-by: <reporter's email>`?

 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 d83cb6e4c62aec..23d44a50d81572 100644
--- a/sound/soc/amd/yc/acp6x-mach.c
+++ b/sound/soc/amd/yc/acp6x-mach.c
@@ -297,6 +297,13 @@ static const struct dmi_system_id yc_acp_quirk_table[] = {
 			DMI_MATCH(DMI_PRODUCT_NAME, "Bravo 15 B7ED"),
 		}
 	},
+	{
+		.driver_data = &acp6x_card,
+		.matches = {
+			DMI_MATCH(DMI_BOARD_VENDOR, "Micro-Star International Co., Ltd."),
+			DMI_MATCH(DMI_PRODUCT_NAME, "Bravo 15 C7VF"),
+		}
+	},
 	{
 		.driver_data = &acp6x_card,
 		.matches = {

base-commit: aa8e3ef4fe5332c2ce33507e874b20d9c0077c21
-- 
An old man doll... just what I always wanted! - Clara

Re: [PATCH] ASoC: amd: yc: Add DMI quirk for MSI Bravo 15 C7VF

[Mark Brown]

On Mon, 29 Jan 2024 15:11:47 +0700, Bagas Sanjaya wrote:
> The laptop requires a quirk ID to enable its internal microphone. Add
> it to the DMI quirk table.
> 
> 

Applied to

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

Thanks!

[1/1] ASoC: amd: yc: Add DMI quirk for MSI Bravo 15 C7VF
      commit: c6dce23ec993f7da7790a9eadb36864ceb60e942

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