From: Mario Limonciello <mario.limonciello@amd.com>
To: louison fourmoy <louison.fourmoy@orange.fr>,
lgirdwood@gmail.com, broonie@kernel.org, perex@perex.cz,
tiwai@suse.com, venkataprasad.potturu@amd.com
Cc: linux-sound@vger.kernel.org
Subject: Re: [PATCH] Linux Laptop ACP6x microphone "quirk list" addition
Date: Sun, 5 Jan 2025 22:06:09 -0600 [thread overview]
Message-ID: <e5b4c96c-5a5f-46b2-b627-cbb3672afadc@amd.com> (raw)
In-Reply-To: <2146099437.3319556.1736118857176.JavaMail.open-xchange@opme11oxm24nd1.op.nd1.pom.fr.intraorange>
On 1/5/2025 17:14, louison fourmoy wrote:
> Hi,
>
> The following patch aims to enable the use of the built in microphone
> for the Lenovo Ideapad Slim 5 Gen 10 (AMD). Currently the inbuilt
> microphone of the laptop is not usable with a “stock” kernel and kernel
> manipulation is necessary to use it. This patch adds the correct model
> in the list of models under sound/soc/amd/yc/acp6x-mach.c
In a patch there is no need to say "this patch" or the "following patch".
When a patch is accepted it becomes a commit, and the commit message
won't read right.
I'd suggest taking a gander at
https://www.kernel.org/doc/html/v6.13-rc4/process/submitting-patches.html.
>
> Signed-off-by: Louison Fourmoy <louison.fourmoy@orange.fr>
>
> Patch :
Specifically over here you don't need to use "Patch: ".
You also need to correct the subject, and don't write the patch like an
email.
Here is another one of these that you can reference for submitting a
better patch.
https://github.com/torvalds/linux/commit/b682aa788e5f9f1ddacdfbb453e49fd3f4e83721
>
> --- linux/sound/soc/amd/yc/acp6x-mach.c.orig 2025-01-05
> 23:37:36.927778168 +0100
> +++ linux/sound/soc/amd/yc/acp6x-mach.c 2025-01-05 23:38:28.066418534 +0100
> @@ -304,6 +304,13 @@ static const struct dmi_system_id yc_acp
>
> DMI_MATCH(DMI_PRODUCT_NAME, “83AS”),
> }
> },
> + {
> + .driver_data = &acp6x_card,
> + .matches = {
> + DMI_MATCH(DMI_BOARD_VENDOR, “LENOVO”),
> + DMI_MATCH(DMI_PRODUCT_NAME, “83J3”),
> + }
> + },
> {
> .driver_data = &acp6x_card,
> .matches = {
>
next parent reply other threads:[~2025-01-06 4:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2146099437.3319556.1736118857176.JavaMail.open-xchange@opme11oxm24nd1.op.nd1.pom.fr.intraorange>
2025-01-06 4:06 ` Mario Limonciello [this message]
2025-01-05 23:27 [PATCH] Linux Laptop ACP6x microphone "quirk list" addition Louison Fourmoy
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=e5b4c96c-5a5f-46b2-b627-cbb3672afadc@amd.com \
--to=mario.limonciello@amd.com \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-sound@vger.kernel.org \
--cc=louison.fourmoy@orange.fr \
--cc=perex@perex.cz \
--cc=tiwai@suse.com \
--cc=venkataprasad.potturu@amd.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox