Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Richard Zhu" <hongxing.zhu@nxp.com>
Cc: devicetree@vger.kernel.org, linux-pci@vger.kernel.org,
	imx@lists.linux.dev, conor+dt@kernel.org, robh@kernel.org,
	Frank.Li@kernel.org
Subject: Re: [PATCH v5 2/3] arm64: dts: imx95: Add dma, intr, aer and pme interrupts for PCIe
Date: Thu, 21 May 2026 10:27:42 +0000	[thread overview]
Message-ID: <20260521102743.3D0981F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260521093255.61585-3-hongxing.zhu@nxp.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:

Pre-existing issues:
- [High] The pcie0 node is missing the msi-map-mask property, which can cause MSI mapping failures for downstream devices on higher bus numbers.
--

commit 0e2b46336a5b22c94438abb01ead59266994b86b
Author: Richard Zhu <hongxing.zhu@nxp.com>

arm64: dts: imx95: Add dma, intr, aer and pme interrupts for PCIe

This commit updates the device tree configurations for pcie0 and pcie1
on imx95 to include additional interrupts for dma, intr, aer, and pme.
These new interrupt definitions enable advanced PCIe functionality beyond
basic MSI support.

> diff --git a/arch/arm64/boot/dts/freescale/imx95.dtsi b/arch/arm64/boot/dts/freescale/imx95.dtsi
> index 71394871d8dd0..6896d9c15bf53 100644
> --- a/arch/arm64/boot/dts/freescale/imx95.dtsi
> +++ b/arch/arm64/boot/dts/freescale/imx95.dtsi
> @@ -1861,8 +1861,12 @@ pcie0: pcie@4c300000 {
>  			bus-range = <0x00 0xff>;
>  			num-lanes = <1>;
>  			num-viewport = <8>;
> -			interrupts = <GIC_SPI 310 IRQ_TYPE_LEVEL_HIGH>;
> -			interrupt-names = "msi";
> +			interrupts = <GIC_SPI 310 IRQ_TYPE_LEVEL_HIGH>,
> +				     <GIC_SPI 311 IRQ_TYPE_LEVEL_HIGH>,
> +				     <GIC_SPI 310 IRQ_TYPE_LEVEL_HIGH>,
> +				     <GIC_SPI 310 IRQ_TYPE_LEVEL_HIGH>,
> +				     <GIC_SPI 310 IRQ_TYPE_LEVEL_HIGH>;
> +			interrupt-names = "msi", "dma", "intr", "aer", "pme";

[Severity: High]
This is a pre-existing issue, but I noticed the pcie0 node is missing an
msi-map-mask property. The node defines an iommu-map-mask but lacks a
corresponding msi-map-mask.

Without msi-map-mask, of_map_id() applies a default mask of 0xffffffff to
the PCI requestor ID during MSI allocation. If a PCIe switch is connected
and downstream devices are enumerated on a bus number >= 2, their requestor
IDs (e.g., 0x200, 0x300) might fail to match the defined msi-map entries
which only cover 0x0 and 0x100 ranges.

Could this cause of_map_id to bypass translation, leaving the msi domain
unassigned and breaking MSI functionality for downstream topologies beyond
the first bus?

[ ... ]

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260521093255.61585-1-hongxing.zhu@nxp.com?part=2

  reply	other threads:[~2026-05-21 10:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-21  9:32 [PATCH v5 0/3] Add root port reset to support link recovery Richard Zhu
2026-05-21  9:32 ` [PATCH v5 1/3] dt-bindings: imx6q-pcie: Add optional interrupt entries for intr, aer and pme Richard Zhu
2026-05-21  9:54   ` sashiko-bot
2026-05-21  9:32 ` [PATCH v5 2/3] arm64: dts: imx95: Add dma, intr, aer and pme interrupts for PCIe Richard Zhu
2026-05-21 10:27   ` sashiko-bot [this message]
2026-05-21  9:32 ` [PATCH v5 3/3] PCI: imx6: Add root port reset to support link recovery Richard Zhu
2026-05-21 11:21   ` sashiko-bot
2026-05-22  2:41     ` Hongxing Zhu

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=20260521102743.3D0981F000E9@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=Frank.Li@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=hongxing.zhu@nxp.com \
    --cc=imx@lists.linux.dev \
    --cc=linux-pci@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /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