From: Greg KH <gregkh@linuxfoundation.org>
To: Markuss Broks <markuss.broks@gmail.com>
Cc: Mark Brown <broonie@kernel.org>,
linux-sound@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] ASoC: amd: yc: Add a quirk for MSI Bravo 17 (D7VEK)
Date: Thu, 29 Aug 2024 15:49:24 +0200 [thread overview]
Message-ID: <2024082917-jockstrap-armored-6a14@gregkh> (raw)
In-Reply-To: <20240829130313.338508-1-markuss.broks@gmail.com>
On Thu, Aug 29, 2024 at 04:03:05PM +0300, Markuss Broks wrote:
> MSI Bravo 17 (D7VEK), like other laptops from the family,
> has broken ACPI tables and needs a quirk for internal mic
> to work.
>
> Signed-off-by: Markuss Broks <markuss.broks@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 0523c16305db..843abc378b28 100644
> --- a/sound/soc/amd/yc/acp6x-mach.c
> +++ b/sound/soc/amd/yc/acp6x-mach.c
> @@ -353,6 +353,13 @@ static const struct dmi_system_id yc_acp_quirk_table[] = {
> DMI_MATCH(DMI_PRODUCT_NAME, "Bravo 15 C7VF"),
> }
> },
> + {
> + .driver_data = &acp6x_card,
> + .matches = {
> + DMI_MATCH(DMI_BOARD_VENDOR, "Micro-Star International Co., Ltd."),
> + DMI_MATCH(DMI_PRODUCT_NAME, "Bravo 17 D7VEK"),
> + }
> + },
> {
> .driver_data = &acp6x_card,
> .matches = {
> --
> 2.46.0
>
>
<formletter>
This is not the correct way to submit patches for inclusion in the
stable kernel tree. Please read:
https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
for how to do this properly.
</formletter>
next prev parent reply other threads:[~2024-08-29 13:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-29 13:03 [PATCH] ASoC: amd: yc: Add a quirk for MSI Bravo 17 (D7VEK) Markuss Broks
2024-08-29 13:49 ` Greg KH [this message]
2024-08-29 14:36 ` Markuss Broks
2024-08-29 14:40 ` Mark Brown
2024-08-29 14:56 ` Mark Brown
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=2024082917-jockstrap-armored-6a14@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=broonie@kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=markuss.broks@gmail.com \
--cc=stable@vger.kernel.org \
/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