From: Takashi Iwai <tiwai@suse.de>
To: rppxj178543@163.com
Cc: alsa-devel@alsa-project.org, tiwai@suse.com, perex@perex.cz,
fuhao@open-hieco.net, linux-kernel@vger.kernel.org,
renpanpan <renpanpan@kylinos.cn>
Subject: Re: [PATCH] ALSA: hda: Force MSI for Hygon H34M51A board
Date: Fri, 23 Oct 2026 15:34:04 +0200 [thread overview]
Message-ID: <87h5ica6cz.wl-tiwai@suse.de> (raw)
In-Reply-To: <20261022085438.1315679-1-rppxj178543@163.com>
On Thu, 22 Oct 2026 10:54:38 +0200,
rppxj178543@163.com wrote:
>
> From: renpanpan <renpanpan@kylinos.cn>
>
> The Hygon HDA controller (PCI 1d94:14a9) has AZX_DCAPS_NO_MSI set in
> the PCI ID table to use legacy INTx, as MSI may lose interrupts under
> heavy load on some Hygon platforms (commit 41212ff3e4ed ("ALSA: hda:
> Add support for Hygon family 18h model 5h HD-Audio")).
>
> However, on the Kunlun H34M51A board (PCI subsystem 1d94:c950) the
> INTx interrupt line is not wired. /proc/interrupts shows zero count
> for the HDA IRQ from boot, so the RIRB interrupt handler is never
> called. Without RIRB processing, azx_rirb_get_response() times out
> after 1 s, switches to polling mode, and the resulting slow codec
> communication delays card registration by ~20 s and breaks
> unsolicited jack-detection event delivery.
>
> Force MSI on for subsystem 1d94:c950 by adding it to msi_deny_list
> with value 1. The list is consulted in check_msi() before the
> AZX_DCAPS_NO_MSI check, so H34M51A gets MSI enabled while other
> Hygon platforms retain INTx.
>
> Signed-off-by: renpanpan <renpanpan@kylinos.cn>
Applied now. Thanks.
Takashi
prev parent reply other threads:[~2026-10-23 13:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-22 8:54 rppxj178543
2026-10-23 13:34 ` Takashi Iwai [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=87h5ica6cz.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=fuhao@open-hieco.net \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=renpanpan@kylinos.cn \
--cc=rppxj178543@163.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®