From: Markus Meier <kerneldev@epic-bytes.net>
To: alsa-devel@alsa-project.org
Subject: [PATCH] ASoC: amd: yc: Fix non-functional mic on Lenovo Yoga Slim 7 Pro 14ARH7 82UU
Date: Mon, 02 Oct 2023 23:04:57 +0200 [thread overview]
Message-ID: <10347605.nUPlyArG6x@kali> (raw)
[-- Attachment #1: Type: text/plain, Size: 679 bytes --]
Hi,
I own a Lenovo Yoga Slim 7 Pro 14ARH7 where the microphone is not showing up.
I added the system to the quirk table and the mic is working correctly (but
with very low volume) now.
Here's an except from dmidecode:
System Information
Manufacturer: LENOVO
Product Name: 82UU
Version: Yoga Slim 7 Pro 14ARH7
SKU Number: LENOVO_MT_82UU_BU_idea_FM_Yoga Slim 7 Pro 14ARH7
Family: Yoga Slim 7 Pro 14ARH7
Please add this patch to the kernel and add it to the stable kernels too. I
guess the microphone should have worked before. Seems to be a regression
introduced by c008323fe361bd62a43d9fb29737dacd5c067fb7
Thank you very much
Markus
[-- Attachment #2: yoga-slim-7-pro-82UU-microphone.patch --]
[-- Type: text/x-patch, Size: 451 bytes --]
--- a/sound/soc/amd/yc/acp6x-mach.c 2023-09-29 19:31:03.753786095 +0200
+++ b/sound/soc/amd/yc/acp6x-mach.c 2023-09-29 19:32:06.414276453 +0200
@@ -217,6 +217,13 @@
.driver_data = &acp6x_card,
.matches = {
DMI_MATCH(DMI_BOARD_VENDOR, "LENOVO"),
+ DMI_MATCH(DMI_PRODUCT_NAME, "82UU"),
+ }
+ },
+ {
+ .driver_data = &acp6x_card,
+ .matches = {
+ DMI_MATCH(DMI_BOARD_VENDOR, "LENOVO"),
DMI_MATCH(DMI_PRODUCT_NAME, "82V2"),
}
},
next reply other threads:[~2023-10-02 21:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-02 21:04 Markus Meier [this message]
2023-10-03 9:39 ` [PATCH] ASoC: amd: yc: Fix non-functional mic on Lenovo Yoga Slim 7 Pro 14ARH7 82UU August Wikerfors
2023-10-03 10:24 ` Linux regression tracking (Thorsten Leemhuis)
2023-10-03 15:04 ` Markus Meier
2023-10-06 11:59 ` Linux regression tracking (Thorsten Leemhuis)
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=10347605.nUPlyArG6x@kali \
--to=kerneldev@epic-bytes.net \
--cc=alsa-devel@alsa-project.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;
as well as URLs for NNTP newsgroup(s).