All of lore.kernel.org
 help / color / mirror / Atom feed
From: M Cooley <m.cooley.198@gmail.com>
To: Mark Brown <broonie@kernel.org>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
	linux-sound@vger.kernel.org,  Jaroslav Kysela <perex@perex.cz>,
	Takashi Iwai <tiwai@suse.com>
Subject: [PATCH v2] ASoC: amd: yc: Fix non-functional mic on ASUS M7600RE
Date: Fri, 8 Mar 2024 17:35:40 -0500	[thread overview]
Message-ID: <CALijGznExWW4fujNWwMzmn_K=wo96sGzV_2VkT7NjvEUdkg7Gw@mail.gmail.com> (raw)
In-Reply-To: <5eb9f2b5-62ef-442d-b93f-ea6b0d85eac3@sirena.org.uk>

On Fri, Mar 8, 2024 at 4:37 PM Mark Brown <broonie@kernel.org> wrote:
>
> It's a patch whatever the reason for it - basically your email looks
> like it got almost everything right (assuming git am likes it), you just
> need to delete the process question above from the changelog and add a
> Signed-off-by as covered in submitting-patches.rst.  As that covers
> there's legal stuff with the signoff which means I shouldn't take a
> patch without it.

The ASUS M7600RE (Vivobook Pro 16X OLED) needs a quirks-table entry for the
internal microphone to function properly.

Signed-off-by: Mitch Cooley <m.cooley.198@gmail.com>
---
diff --git a/sound/soc/amd/yc/acp6x-mach.c b/sound/soc/amd/yc/acp6x-mach.c
index abb9589b8477..af90da8646ba 100644
--- a/sound/soc/amd/yc/acp6x-mach.c
+++ b/sound/soc/amd/yc/acp6x-mach.c
@@ -311,6 +311,13 @@ static const struct dmi_system_id yc_acp_quirk_table[] = {
                        DMI_MATCH(DMI_PRODUCT_NAME, "M6500RC"),
                }
        },
+ {
+         .driver_data = &acp6x_card,
+         .matches = {
+                 DMI_MATCH(DMI_BOARD_VENDOR, "ASUSTeK COMPUTER INC."),
+                 DMI_MATCH(DMI_PRODUCT_NAME, "M7600RE"),
+         }
+ },
        {
                .driver_data = &acp6x_card,
                .matches = {
--

  reply	other threads:[~2024-03-08 22:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-08 20:50 ASoC: amd: yc: Fix non-functional mic on ASUS M7600RE M Cooley
2024-03-08 21:37 ` Mark Brown
2024-03-08 22:35   ` M Cooley [this message]
2024-03-11 15:40     ` [PATCH v2] " Mark Brown
2024-03-11 16:50     ` 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='CALijGznExWW4fujNWwMzmn_K=wo96sGzV_2VkT7NjvEUdkg7Gw@mail.gmail.com' \
    --to=m.cooley.198@gmail.com \
    --cc=broonie@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-sound@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=tiwai@suse.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.