From: Takashi Iwai <tiwai@suse.de>
To: Oliver Sieber <ollisieber@gmail.com>
Cc: Bagas Sanjaya <bagasdotme@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Sound System <linux-sound@vger.kernel.org>,
Linux ALSA Development <alsa-devel@alsa-project.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>, Jaroslav Kysela <perex@perex.cz>,
Takashi Iwai <tiwai@suse.com>
Subject: Re: Fwd: acp3x: Missing product ID for Thinkpad T14s Gen2 AMD Ryzen 7 PRO 5850U
Date: Fri, 17 Nov 2023 14:32:14 +0100 [thread overview]
Message-ID: <87sf54jyjl.wl-tiwai@suse.de> (raw)
In-Reply-To: <78149e00-12b5-459b-8754-a17dd974916d@gmail.com>
On Fri, 17 Nov 2023 08:17:48 +0100,
Oliver Sieber wrote:
>
>
> Hi,
>
> in the following I provide my proposed patch for the bug report on Bugzilla
> [1]. Let me quote from it:
>
> Hey,sound/soc/amd/renoir/rn-pci-acp3x.c has a hard-coded list of quirks. It seems like some product IDs may be missing. In my case, I am using a Lenovo Thinkpad t14s gen2 with an AMD Ryzen 7 PRO 5850U.
> My audio output is fine but my internal microphone cannot be found.
>
> Running `dmidecode` yields:
>
> Handle 0x000F, DMI type 1, 27 bytes
> System Information
> Manufacturer: LENOVO
> Product Name: 20XGS1KT02
> Version: ThinkPad T14s Gen 2a
>
> Could it be that one may have to add the product ID "20XGS1KT02" to the hard-coded list of quirks in rn-pci-acp3x.c?
>
> It seems as there have been similar problems in the past, e.g. https://bugzilla.kernel.org/show_bug.cgi?id=216270.
>
> My proposed diff looks as follows:
>
> diff --git a/sound/soc/amd/renoir/rn-pci-acp3x.c b/sound/soc/amd/renoir/
> rn-pci-acp3x.c
> index b3812b70f5f9..754e24d55e6f 100644
> --- a/sound/soc/amd/renoir/rn-pci-acp3x.c
> +++ b/sound/soc/amd/renoir/rn-pci-acp3x.c
> @@ -199,6 +199,13 @@ static const struct dmi_system_id rn_acp_quirk_table[] =
> {
> DMI_EXACT_MATCH(DMI_BOARD_NAME, "20NLCTO1WW"),
> }
> },
> + {
> + /* Lenovo ThinkPad T14s Gen 2 */
> + .matches = {
> + DMI_EXACT_MATCH(DMI_BOARD_VENDOR, "LENOVO"),
> + DMI_EXACT_MATCH(DMI_BOARD_NAME, "20XGS1KT02"),
> + }
> + },
> {}
> };
>
> Please have in mind that this is my first patch for the kernel.
The kernel patch should be in a proper format, so that it can be
merged to the upstream. e.g. The Subject line should have a brief
description with the proper prefix for the corresponding subsystem (in
your case, something like "ASoC: amd:"). It'll follow the patch
description, as well as your proper Signed-off-by tag.
The details are found in
https://docs.kernel.org/process/submitting-patches.html
Could you resubmit the patch in a proper format?
thanks,
Takashi
next prev parent reply other threads:[~2023-11-17 13:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-16 11:10 Fwd: acp3x: Missing product ID for Thinkpad T14s Gen2 AMD Ryzen 7 PRO 5850U Bagas Sanjaya
2023-11-16 18:36 ` Oliver Sieber
2023-11-16 23:34 ` Bagas Sanjaya
[not found] ` <78149e00-12b5-459b-8754-a17dd974916d@gmail.com>
2023-11-17 13:32 ` Takashi Iwai [this message]
[not found] ` <826bb4f4-c6ea-4c45-a0e0-5ca826f0cfe0@gmail.com>
2023-11-19 13:51 ` Bagas Sanjaya
2023-11-20 8:18 ` [PATCH] Subject: ASoC: AMD Renoir - add DMI entry for Lenovo ThinkPad T14s Gen 2 Oliver Sieber
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=87sf54jyjl.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=bagasdotme@gmail.com \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=ollisieber@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox