From: Han Gao <gaohan@iscas.ac.cn>
To: "Bjorn Helgaas" <bhelgaas@google.com>,
"Uwe Kleine-König" <u.kleine-koenig@baylibre.com>,
"Jonathan Cameron" <jonathan.cameron@huawei.com>,
"Lukas Wunner" <lukas@wunner.de>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Kees Cook" <kees@kernel.org>, "Han Gao" <gaohan@iscas.ac.cn>,
"Chen Wang" <unicorn_wang@outlook.com>,
"Manivannan Sadhasivam" <mani@kernel.org>
Cc: linux-pci@vger.kernel.org, sophgo@lists.linux.dev,
linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
Han Gao <rabenda.cn@gmail.com>,
Icenowy Zheng <zhengxingda@iscas.ac.cn>,
Inochi Amaoto <inochiama@gmail.com>,
Vivian Wang <wangruikang@iscas.ac.cn>, Yao Zi <me@ziyao.cc>
Subject: [PATCH 0/2] PCI: Allow disabling port services on broken root ports
Date: Wed, 1 Apr 2026 01:56:56 +0800 [thread overview]
Message-ID: <20260331175658.1015829-1-gaohan@iscas.ac.cn> (raw)
Some PCIe root ports break MSI delivery to downstream devices when
native port services (AER, PME, bwctrl, etc.) are active. The existing
pcie_ports=compat kernel parameter works around this globally, but
affects all ports on the system.
This series adds a per-device mechanism to skip port service probing:
1. Introduce PCI_DEV_FLAGS_NO_PORT_SERVICES flag and wire it into
the PCIe port driver
2. Apply it via quirk to Sophgo SG2042 root ports [1f1c:2042], which
fail to deliver MSI interrupts when port services are enabled
SG2042's PCIe root ports only support MSI, not MSI-X. The MSI
controller provides only 32 vectors shared across all devices behind
each root port. When native port services claim vectors from this
limited pool, downstream devices are starved of interrupts, resulting
in zero interrupts delivered and driver timeouts (e.g. amdgpu fence
fallback timer expired on all rings).
Han Gao (2):
PCI: Add per-device flag to disable native PCIe port services
PCI: Add quirk to disable PCIe port services on Sophgo SG2042
drivers/pci/pcie/portdrv.c | 3 +++
drivers/pci/quirks.c | 12 ++++++++++++
include/linux/pci.h | 2 ++
include/linux/pci_ids.h | 2 ++
4 files changed, 19 insertions(+)
--
2.47.3
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next reply other threads:[~2026-03-31 17:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-31 17:56 Han Gao [this message]
2026-03-31 17:56 ` [PATCH 1/2] PCI: Add per-device flag to disable native PCIe port services Han Gao
2026-03-31 17:56 ` [PATCH 2/2] PCI: Add quirk to disable PCIe port services on Sophgo SG2042 Han Gao
2026-05-01 16:53 ` Manivannan Sadhasivam
2026-05-02 13:58 ` Icenowy Zheng
2026-05-02 19:47 ` Lukas Wunner
2026-05-03 7:10 ` Icenowy Zheng
2026-05-03 8:52 ` Lukas Wunner
2026-05-06 13:39 ` Manivannan Sadhasivam
2026-05-06 14:22 ` Icenowy Zheng
2026-05-07 0:41 ` Inochi Amaoto
2026-05-07 8:52 ` Manivannan Sadhasivam
2026-03-31 18:58 ` [PATCH 0/2] PCI: Allow disabling port services on broken root ports Lukas Wunner
2026-03-31 19:07 ` Han Gao
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=20260331175658.1015829-1-gaohan@iscas.ac.cn \
--to=gaohan@iscas.ac.cn \
--cc=bhelgaas@google.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=inochiama@gmail.com \
--cc=jonathan.cameron@huawei.com \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=lukas@wunner.de \
--cc=mani@kernel.org \
--cc=me@ziyao.cc \
--cc=rabenda.cn@gmail.com \
--cc=sophgo@lists.linux.dev \
--cc=u.kleine-koenig@baylibre.com \
--cc=unicorn_wang@outlook.com \
--cc=wangruikang@iscas.ac.cn \
--cc=zhengxingda@iscas.ac.cn \
/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