From: Soeren Moch <smoch@web.de>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Richard Zhu <hongxing.zhu@nxp.com>,
stable@vger.kernel.org, Manivannan Sadhasivam <mani@kernel.org>,
Lucas Stach <l.stach@pengutronix.de>,
Bjorn Helgaas <bhelgaas@google.com>, Frank Li <Frank.Li@nxp.com>,
Fabio Estevam <festevam@gmail.com>,
linux-pci@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
imx@lists.linux.dev, linux-kernel@vger.kernel.org,
Thorsten Leemhuis <regressions@leemhuis.info>
Subject: Re: [PATCH] PCI: imx6: Keep Root Port MSI capability also for i.MX6Q
Date: Tue, 29 Sep 2026 14:27:45 +0200 [thread overview]
Message-ID: <2025e3e9-3aa5-4ea6-a68f-42f0d148e3f4@web.de> (raw)
In-Reply-To: <20260918230015.GA1205610@bhelgaas>
On 19.09.26 01:00, Bjorn Helgaas wrote:
> [+cc Thorsten, possible regzbot confusion?]
>
> On Mon, Apr 27, 2026 at 01:58:04PM +0200, Soeren Moch wrote:
>> Also on the NXP i.MX6Q chipset MSIs from the endpoints won't be received by
>> the iMSI-RX MSI controller if the Root Port MSI capability is disabled.
>>
>> Even though the Root Port MSIs won't be received by the iMSI-RX controller
>> due to design, this chipset has some weird hardware bug that prevents
>> the endpoint MSIs from reaching when the Root Port MSI capability is
>> disabled.
>>
>> Hence, always keep the Root Port MSI capability for this chipset.
>>
>> Note that by keeping Root Port MSI capability, Root Port MSIs such as AER,
>> PME and others won't be received by default. So users need to use
>> workarounds such as passing 'pcie_pme=nomsi' cmdline param.
>>
>> Fixes: 3a4e8302e72f ("PCI: imx6: Keep Root Port MSI capability with iMSI-RX to work around hardware bug")
>> Cc: <stable@vger.kernel.org> # 7.0.x
>> Signed-off-by: Soeren Moch <smoch@web.de>
> This thread is still listed as a regression:
> https://linux-regtracking.leemhuis.info/regzbot/regression/lore/20260427115804.134231-1-smoch@web.de/
>
> But I *think* it's been resolved by:
>
> b4bee12ebecc ("PCI: imx6: Keep i.MX6 Root Port MSI/MSI-X Capabilities with iMSI-RX to work around hardware bug")
>
> Can you confirm?
It was fixed for 7.2.0, in 7.2.5 I saw a similar (?) problem again, in
7.2.8 this is (finally?) fixed. I did not test the stable versions in
between.
So I can confirm this is fixed, yes.
Thanks,
Soeren
>
> Maybe regzbot is confused by the fact that the regression was first
> attributed to 3a4e8302e72f, and then later attributed to
> f5cd8a929c825?
>
>> ---
>> Cc: Manivannan Sadhasivam <mani@kernel.org>
>> Cc: Richard Zhu <hongxing.zhu@nxp.com>
>> Cc: Lucas Stach <l.stach@pengutronix.de>
>> Cc: Bjorn Helgaas <bhelgaas@google.com>
>> Cc: Frank Li <Frank.Li@nxp.com>
>> Cc: Fabio Estevam <festevam@gmail.com>
>> Cc: linux-pci@vger.kernel.org
>> Cc: linux-arm-kernel@lists.infradead.org
>> Cc: imx@lists.linux.dev
>> Cc: linux-kernel@vger.kernel.org
>>
>> Tested on a tbs2910 board [1]
>> [1] arch/arm/boot/dts/nxp/imx/imx6q-tbs2910.dts
>> ---
>> drivers/pci/controller/dwc/pci-imx6.c | 3 ++-
>> 1 file changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/pci/controller/dwc/pci-imx6.c b/drivers/pci/controller/dwc/pci-imx6.c
>> index 6d6a1688e7eb..3d461bdef967 100644
>> --- a/drivers/pci/controller/dwc/pci-imx6.c
>> +++ b/drivers/pci/controller/dwc/pci-imx6.c
>> @@ -1865,7 +1865,8 @@ static const struct imx_pcie_drvdata drvdata[] = {
>> .flags = IMX_PCIE_FLAG_IMX_PHY |
>> IMX_PCIE_FLAG_SPEED_CHANGE_WORKAROUND |
>> IMX_PCIE_FLAG_BROKEN_SUSPEND |
>> - IMX_PCIE_FLAG_SUPPORTS_SUSPEND,
>> + IMX_PCIE_FLAG_SUPPORTS_SUSPEND |
>> + IMX_PCIE_FLAG_KEEP_MSI_CAP,
>> .dbi_length = 0x200,
>> .gpr = "fsl,imx6q-iomuxc-gpr",
>> .ltssm_off = IOMUXC_GPR12,
>> --
>> 2.43.0
>>
prev parent reply other threads:[~2026-09-29 12:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-27 11:58 Soeren Moch
2026-04-28 2:19 ` Hongxing Zhu
2026-07-05 9:10 ` Soeren Moch
2026-07-06 3:06 ` Hongxing Zhu
2026-04-30 18:53 ` Frank Li
2026-07-06 10:29 ` Manivannan Sadhasivam
2026-07-08 8:52 ` Soeren Moch
2026-07-15 5:40 ` Manivannan Sadhasivam
2026-07-16 21:44 ` Soeren Moch
2026-09-18 23:00 ` Bjorn Helgaas
2026-09-19 6:57 ` Thorsten Leemhuis
2026-09-29 12:27 ` Soeren Moch [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=2025e3e9-3aa5-4ea6-a68f-42f0d148e3f4@web.de \
--to=smoch@web.de \
--cc=Frank.Li@nxp.com \
--cc=bhelgaas@google.com \
--cc=festevam@gmail.com \
--cc=helgaas@kernel.org \
--cc=hongxing.zhu@nxp.com \
--cc=imx@lists.linux.dev \
--cc=l.stach@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mani@kernel.org \
--cc=regressions@leemhuis.info \
--cc=stable@vger.kernel.org \
/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®