From: Takashi Iwai <tiwai@suse.de>
To: "Mario Limonciello (AMD)" <superm1@kernel.org>
Cc: mario.limonciello@amd.com, perex@perex.cz, tiwai@suse.com,
Richard Gong <richard.gong@amd.com>,
Juan Martinez <juan.martinez@amd.com>,
linux-sound@vger.kernel.org
Subject: Re: [PATCH] Revert "ALSA: hda: Add ASRock X670E Taichi to denylist"
Date: Wed, 13 Aug 2025 16:15:26 +0200 [thread overview]
Message-ID: <87ms83wbnl.wl-tiwai@suse.de> (raw)
In-Reply-To: <20250813140427.1577172-1-superm1@kernel.org>
On Wed, 13 Aug 2025 16:03:08 +0200,
Mario Limonciello (AMD) wrote:
>
> On a motherboard with an AMD Granite Ridge CPU there is a report
> that 3.5mm microphone and headphones aren't working. In the
> log it's observed:
>
> snd_hda_intel 0000:02:00.6: Skipping the device on the denylist
>
> This was because of commit df42ee7e22f03 ("ALSA: hda: Add ASRock
> X670E Taichi to denylist"). Reverting this commit allows the
> microphone and headphones to work again. As at least some combinations
> of this motherboard do have applicable devices, revert so that they
> can be probed.
>
> Cc: Richard Gong <richard.gong@amd.com>
> Cc: Juan Martinez <juan.martinez@amd.com>
> Signed-off-by: Mario Limonciello (AMD) <superm1@kernel.org>
> ---
> sound/hda/controllers/intel.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/sound/hda/controllers/intel.c b/sound/hda/controllers/intel.c
> index fcf67e97a546a..1bb3ff55b1151 100644
> --- a/sound/hda/controllers/intel.c
> +++ b/sound/hda/controllers/intel.c
> @@ -2077,7 +2077,6 @@ static const struct pci_device_id driver_denylist[] = {
> { PCI_DEVICE_SUB(0x1022, 0x1487, 0x1043, 0x874f) }, /* ASUS ROG Zenith II / Strix */
> { PCI_DEVICE_SUB(0x1022, 0x1487, 0x1462, 0xcb59) }, /* MSI TRX40 Creator */
> { PCI_DEVICE_SUB(0x1022, 0x1487, 0x1462, 0xcb60) }, /* MSI TRX40 */
> - { PCI_DEVICE_SUB(0x1022, 0x15e3, 0x1022, 0xd601) }, /* ASRock X670E Taichi */
Hmm, it's a bit awkward situation. I believe this will make the
problem of the original fix back.
But, the original bug was merely error messages and memory wastes, and
the PCI SSID looks also not specific to the mobo vendor, so we can
start as a revert, but we'd need yet another fix to cover the original
problem.
Maybe some additional DMI check. Oh well. Such mobo vendors should
be cursed if they don't assign the proper PCI SSIDs...
Takashi
next prev parent reply other threads:[~2025-08-13 14:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-13 14:03 [PATCH] Revert "ALSA: hda: Add ASRock X670E Taichi to denylist" Mario Limonciello (AMD)
2025-08-13 14:15 ` Takashi Iwai [this message]
2025-08-13 14:43 ` Mario Limonciello
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=87ms83wbnl.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=juan.martinez@amd.com \
--cc=linux-sound@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=perex@perex.cz \
--cc=richard.gong@amd.com \
--cc=superm1@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.