Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Claudiu Manoil" <claudiu.manoil@nxp.com>
Cc: conor+dt@kernel.org, imx@lists.linux.dev, robh@kernel.org,
	devicetree@vger.kernel.org, Frank.Li@kernel.org
Subject: Re: [PATCH net-next v1 3/5] arm64: dts: s32n79: add NETC IEP18 ECAM node for ENETC PPM ports
Date: Sat, 10 Oct 2026 12:49:53 +0000	[thread overview]
Message-ID: <sashiko-outbox-166545@kernel.org> (raw)
In-Reply-To: <49a0450c6d906f0ba1a886d86e89f35746a7a6fc.1791548316.git.claudiu.manoil@nxp.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] dt-bindings: PCI node netc_iep18 uses msi-parent instead of msi-map breaking MSI routing
--

commit 31419622a4729bd8008cf190e3a0993387a80408
Author: Claudiu Manoil <claudiu.manoil@nxp.com>

arm64: dts: s32n79: add NETC IEP18 ECAM node for ENETC PPM ports

Add the netc_iep18 PCIe ECAM host node describing the NETC integrated
endpoint bus allocated to the first Linux cohort on S32N79.

> diff --git a/arch/arm64/boot/dts/freescale/s32n79.dtsi b/arch/arm64/boot/dts/freescale/s32n79.dtsi
> index 94ab58783fdc8..671b807f1c540 100644
> --- a/arch/arm64/boot/dts/freescale/s32n79.dtsi
> +++ b/arch/arm64/boot/dts/freescale/s32n79.dtsi
> @@ -122,6 +122,30 @@ irqsteer_coss: interrupt-controller@4ed00000 {
[ ... ]
> +		netc_iep18: pcie@241200000 {
> +			compatible = "pci-host-ecam-generic";
> +			reg = <0x2 0x41200000 0x0 0x100000>;
> +			#address-cells = <3>;
> +			#size-cells = <2>;
> +			device_type = "pci";
> +			bus-range = <0x0 0x0>;
> +			msi-parent = <&its 0x0>;

[Severity: High]
Does this break MSI routing for the PCIe devices on this bus?

The GICv3 ITS requires an MSI specifier (#msi-cells = <1>), and Linux's
of_check_msi_parent() explicitly rejects msi-parent on bus nodes if the
target MSI controller has #msi-cells > 0. This causes of_msi_xlate() to
fail to locate an MSI controller, leaving the PCIe devices entirely without
an MSI domain.

Furthermore, PCI buses typically use the msi-map property to map Requester
IDs (RIDs) to MSI sideband Device IDs. Using msi-parent with an argument
maps all 256 RIDs to the exact same ITS sideband ID (0x0). This breaks MSI
isolation and contradicts the iommu-map property which maps them to distinct
Stream IDs (0xc0000 to 0xc00FF).

Should this use msi-map instead, for example:
msi-map = <0x0 &its 0xc0000 0x100>?

> +			iommu-map = <0x0 &smmu 0xc0000 0x100>;
> +			dma-coherent;
> +			status = "disabled";
> +
> +			/* All NETC PCIe functions */
> +			ranges = <0x82000000 0x0 0x48800000 0x0 0x48800000 0x0 0x4b0000>;
> +		};
> +	};

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/cover.1791548316.git.claudiu.manoil@nxp.com?part=3

  reply	other threads:[~2026-10-10 12:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-09 12:40 [PATCH net-next v1 0/5] net: enetc: S32N79 pseudo-MAC (PPM) networking support Claudiu Manoil
2026-10-09 12:40 ` [PATCH net-next v1 1/5] net: enetc: Add pseudo-MAC support for ENETCv4 Ports via a DT overlay Claudiu Manoil
2026-10-10  2:26   ` Frank Li
2026-10-10 12:49   ` sashiko-bot
2026-10-09 12:40 ` [PATCH net-next v1 3/5] arm64: dts: s32n79: add NETC IEP18 ECAM node for ENETC PPM ports Claudiu Manoil
2026-10-10 12:49   ` sashiko-bot [this message]
2026-10-09 12:40 ` [PATCH net-next v1 4/5] arm64: dts: s32n79-rdb: enable NETC IEP18 Claudiu Manoil

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=sashiko-outbox-166545@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=Frank.Li@kernel.org \
    --cc=claudiu.manoil@nxp.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=imx@lists.linux.dev \
    --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