From: "Arnd Bergmann" <arnd@arndb.de>
To: "Han Gao" <gaohan@iscas.ac.cn>,
"Jaroslav Kysela" <perex@perex.cz>,
"Takashi Iwai" <tiwai@suse.com>,
"Kai Vehmanen" <kai.vehmanen@linux.intel.com>,
"Peter Ujfalusi" <peter.ujfalusi@linux.intel.com>,
"Ranjani Sridharan" <ranjani.sridharan@linux.intel.com>,
"Bard Liao" <yung-chuan.liao@linux.intel.com>,
"Maxim Mikityanskiy" <maxtram95@gmail.com>,
"Pierre-Louis Bossart" <pierre-louis.bossart@linux.dev>,
"Stuart Hayhurst" <stuart.a.hayhurst@gmail.com>,
linux-sound@vger.kernel.org
Cc: "Han Gao" <rabenda.cn@gmail.com>,
linux-riscv@lists.infradead.org, sophgo@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ALSA: hda: intel: Introduce msi64 parameter to override 64-bit MSI restriction
Date: Mon, 22 Dec 2025 17:18:26 +0100 [thread overview]
Message-ID: <ad17d046-158d-4019-b801-423896fcf5fc@app.fastmail.com> (raw)
In-Reply-To: <20251220170501.3972438-1-gaohan@iscas.ac.cn>
On Sat, Dec 20, 2025, at 18:05, Han Gao wrote:
> Sophgo SG2042 MSI driver does not support 32-bit MSI.
> Introduce an 'msi64' kernel parameter to bypass NO_MSI64 for ATI/HDMI.
>
> Signed-off-by: Han Gao <gaohan@iscas.ac.cn>
> ---
> +module_param(msi64, bool, 0444);
> +MODULE_PARM_DESC(msi64, "Force use msi 64bit.");
This does not seem like an appropriate use for a module
parameter. There are very few things we want to use those
for in new code, and working around hardware bugs is
clearly not one.
> @@ -1903,7 +1906,7 @@ static int azx_first_init(struct azx *chip)
> chip->gts_present = true;
> #endif
>
> - if (chip->msi && chip->driver_caps & AZX_DCAPS_NO_MSI64) {
> + if (chip->msi && chip->driver_caps & AZX_DCAPS_NO_MSI64 && !msi64) {
> dev_dbg(card->dev, "Disabling 64bit MSI\n");
> pci->no_64bit_msi = true;
> }
The behavior is also wrong: if the system can use neither 32-bit
MSI nor 64-bit MSI, this would accidentally try to use the
64-bit variant and then cause runtime issues.
I would expect the only possible fallback to be using legacy IntX
interrupts, or returning a probe failure if that doesn't work
either.
Arnd
next prev parent reply other threads:[~2025-12-22 16:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-20 17:05 [PATCH] ALSA: hda: intel: Introduce msi64 parameter to override 64-bit MSI restriction Han Gao
2025-12-22 16:18 ` Arnd Bergmann [this message]
2025-12-23 9:40 ` Han Gao
2025-12-23 10:44 ` Arnd Bergmann
2025-12-23 9:40 ` 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=ad17d046-158d-4019-b801-423896fcf5fc@app.fastmail.com \
--to=arnd@arndb.de \
--cc=gaohan@iscas.ac.cn \
--cc=kai.vehmanen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-sound@vger.kernel.org \
--cc=maxtram95@gmail.com \
--cc=perex@perex.cz \
--cc=peter.ujfalusi@linux.intel.com \
--cc=pierre-louis.bossart@linux.dev \
--cc=rabenda.cn@gmail.com \
--cc=ranjani.sridharan@linux.intel.com \
--cc=sophgo@lists.linux.dev \
--cc=stuart.a.hayhurst@gmail.com \
--cc=tiwai@suse.com \
--cc=yung-chuan.liao@linux.intel.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