mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Mukunda,Vijendar" <vijendar.mukunda@amd.com>
To: rcilto1@lenovo.com,
	Venkata Prasad Potturu <venkataprasad.potturu@amd.com>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Mark Brown <broonie@kernel.org>, Jaroslav Kysela <perex@perex.cz>,
	Takashi Iwai <tiwai@suse.com>
Cc: linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ASoC: amd: yc: Add DMI quirk for Lenovo V15 AMN G6
Date: Sat, 31 Oct 2026 19:23:57 +0530	[thread overview]
Message-ID: <64d14f89-07a9-40c0-8989-115fa6ea21c9@amd.com> (raw)
In-Reply-To: <20261030-ideapad-mic-support-v1-1-7677371af384@lenovo.com>

On 31/10/26 00:09, Rodnei Cilto via B4 Relay wrote:
> [Some people who received this message don't often get email from devnull+rcilto1.lenovo.com@kernel.org. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ]
>
> From: Rodnei Cilto <rcilto1@lenovo.com>
>
> The Lenovo V15 AMN G6 (product name 83VD and 84CS) uses the ACP6x PDM
> interface for its internal digital microphone array.
>
> Its firmware exposes neither the AcpDmicConnected _DSD property
> nor the _WOV method, causing acp6x_probe() to fall through to
> the DMI check and return -ENODEV. As a result, acp_yc_mach.0
> is not bound and no capture device is registered.
>
> Add a DMI quirk entry for this model. With it, the machine
> driver binds correctly and the DMIC capture device becomes
> available.
>
> Capture was verified working with arecord and PipeWire.
>
> Signed-off-by: Rodnei Cilto <rcilto1@lenovo.com>
Reviewed-by: Vijendar Mukunda <Vijendar.Mukunda@amd.com>
> ---
>  sound/soc/amd/yc/acp6x-mach.c | 14 ++++++++++++++
>  1 file changed, 14 insertions(+)
>
> diff --git a/sound/soc/amd/yc/acp6x-mach.c b/sound/soc/amd/yc/acp6x-mach.c
> index 41f8c0885865..fc648590409a 100644
> --- a/sound/soc/amd/yc/acp6x-mach.c
> +++ b/sound/soc/amd/yc/acp6x-mach.c
> @@ -395,6 +395,20 @@ static const struct dmi_system_id yc_acp_quirk_table[] = {
>                         DMI_MATCH(DMI_PRODUCT_NAME, "83UU"),
>                 }
>         },
> +       {
> +               .driver_data = &acp6x_card,
> +               .matches = {
> +                       DMI_MATCH(DMI_BOARD_VENDOR, "LENOVO"),
> +                       DMI_MATCH(DMI_PRODUCT_NAME, "84CS"),
> +               }
> +       },
> +       {
> +               .driver_data = &acp6x_card,
> +               .matches = {
> +                       DMI_MATCH(DMI_BOARD_VENDOR, "LENOVO"),
> +                       DMI_MATCH(DMI_PRODUCT_NAME, "83VD"),
> +               }
> +       },
>         {
>                 .driver_data = &acp6x_card,
>                 .matches = {
>
> ---
> base-commit: d89e1d186ec9271bf78e62771779e9fc03bf0fc3
> change-id: 20261030-ideapad-mic-support-d658dddb815a
>
> Best regards,
> --
> Rodnei Cilto <rcilto1@lenovo.com>


      reply	other threads:[~2026-10-31 13:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-30 18:39 Rodnei Cilto via B4 Relay
2026-10-31 13:53 ` Mukunda,Vijendar [this message]

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=64d14f89-07a9-40c0-8989-115fa6ea21c9@amd.com \
    --to=vijendar.mukunda@amd.com \
    --cc=broonie@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=rcilto1@lenovo.com \
    --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

all inboxes | Powered by JetHome®