From: Mario Limonciello <mario.limonciello@amd.com>
To: Stuart Hayhurst <stuart.a.hayhurst@gmail.com>,
linux-sound@vger.kernel.org, Takashi Iwai <tiwai@suse.com>
Cc: linux-kernel@vger.kernel.org, Jaroslav Kysela <perex@perex.cz>
Subject: Re: [PATCH] ALSA: hda/intel: Add MSI X870E Tomahawk to denylist by DMI ID
Date: Fri, 27 Mar 2026 11:15:38 -0500 [thread overview]
Message-ID: <05e1cb0a-18f0-412f-87c6-99319b18af52@amd.com> (raw)
In-Reply-To: <20260327155737.21818-2-stuart.a.hayhurst@gmail.com>
On 3/27/26 10:57, Stuart Hayhurst wrote:
> This motherboard uses USB audio instead, causing this driver to complain
> about "no codecs found!".
> Add it to the denylist to silence the warning.
>
> The first attempt only matched on the PCI device, but this caused issues
> for some laptops, so DMI match against the board as well.
>
> Signed-off-by: Stuart Hayhurst <stuart.a.hayhurst@gmail.com>
Thanks!
Takashi,
Probably worth asking - why is the "no codecs found" ERR in the first
place? There are obviously designs out there like this, should the ERR
message be simmered down?
> ---
> sound/hda/controllers/intel.c | 13 +++++++++++++
> 1 file changed, 13 insertions(+)
>
> diff --git a/sound/hda/controllers/intel.c b/sound/hda/controllers/intel.c
> index 2edbcab597c8..8a7bd49e411f 100644
> --- a/sound/hda/controllers/intel.c
> +++ b/sound/hda/controllers/intel.c
> @@ -2085,6 +2085,11 @@ static struct pci_device_id driver_denylist_ideapad_z570[] = {
> {}
> };
>
> +static struct pci_device_id driver_denylist_msi_x870e[] = {
> + { PCI_DEVICE_SUB(0x1022, 0x15e3, 0x1462, 0xee59) }, /* MSI X870E Tomahawk WiFi */
> + {}
> +};
> +
> /* DMI-based denylist, to be used when:
> * - PCI subsystem IDs are zero, impossible to distinguish from valid sound cards.
> * - Different modifications of the same laptop use different GPU models.
> @@ -2098,6 +2103,14 @@ static const struct dmi_system_id driver_denylist_dmi[] = {
> },
> .driver_data = &driver_denylist_ideapad_z570,
> },
> + {
> + /* PCI device matching alone incorrectly matches some laptops */
> + .matches = {
> + DMI_MATCH(DMI_BOARD_VENDOR, "Micro-Star International Co., Ltd."),
> + DMI_MATCH(DMI_BOARD_NAME, "MAG X870E TOMAHAWK WIFI (MS-7E59)"),
> + },
> + .driver_data = &driver_denylist_msi_x870e,
> + },
> {}
> };
>
next prev parent reply other threads:[~2026-03-27 16:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-27 15:57 Stuart Hayhurst
2026-03-27 16:15 ` Mario Limonciello [this message]
2026-03-27 16:39 ` Takashi Iwai
2026-03-27 16:52 ` Mario Limonciello
2026-03-27 17:35 ` Stuart
2026-04-14 13:06 ` Stuart
2026-03-28 9:36 ` Takashi Iwai
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=05e1cb0a-18f0-412f-87c6-99319b18af52@amd.com \
--to=mario.limonciello@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=stuart.a.hayhurst@gmail.com \
--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
all inboxes | Powered by JetHome®