From: Francesco Dolcini <francesco@dolcini.it>
To: Lei Xu <lei.xu@nxp.com>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
imx@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
justin.jiang@nxp.com, qijian.guo@nxp.com
Subject: Re: [PATCH 2/2] arm64: dts: freescale: imx95: Add support for i.MX95 15x15 FRDM board
Date: Mon, 8 Dec 2025 07:57:07 +0100 [thread overview]
Message-ID: <20251208065707.GA15128@francesco-nb> (raw)
In-Reply-To: <20251207-127-v1-2-5a2eeb69f150@nxp.com>
Hello Lei,
On Sun, Dec 07, 2025 at 05:26:06AM -0800, Lei Xu wrote:
> The i.MX95 15x15 FRDM board is a compact and cost-effective development
> platform based on the i.MX95 applications processor.
...
> diff --git a/arch/arm64/boot/dts/freescale/imx95-15x15-frdm.dts b/arch/arm64/boot/dts/freescale/imx95-15x15-frdm.dts
> new file mode 100644
> index 000000000000..61e815c858b8
> --- /dev/null
> +++ b/arch/arm64/boot/dts/freescale/imx95-15x15-frdm.dts
...
> +
> +/* Default settings in i.mx95.dtsi are for i.MX95 19x19 package.
> + * Override here for the i.MX95 15x15 package.
> + */
> +&netc_bus0 {
> + msi-map = <0x0 &its 0x60 0x1>, //ENETC0 PF
> + <0x10 &its 0x61 0x1>, //ENETC0 VF0
> + <0x20 &its 0x62 0x1>, //ENETC0 VF1
> + <0x40 &its 0x63 0x1>, //ENETC1 PF
> + <0x50 &its 0x65 0x1>, //ENETC1 VF0
> + <0x60 &its 0x66 0x1>, //ENETC1 VF1
> + <0x80 &its 0x64 0x1>, //ENETC2 PF
> + <0xc0 &its 0x67 0x1>; //NETC Timer
> + iommu-map = <0x0 &smmu 0x20 0x1>,
> + <0x10 &smmu 0x21 0x1>,
> + <0x20 &smmu 0x22 0x1>,
> + <0x40 &smmu 0x23 0x1>,
> + <0x50 &smmu 0x25 0x1>,
> + <0x60 &smmu 0x26 0x1>,
> + <0x80 &smmu 0x24 0x1>,
> + <0xc0 &smmu 0x27 0x1>;
> +};
If the 19x19 and 15x15 i.MX95 requires something different you should
have a different soc dtsi. Probably creating a new imx95-$something
dtsi, that includes the existing imx95.dtsi and override this property.
This solution does not scale, please fix it.
Francesco
next prev parent reply other threads:[~2025-12-08 6:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-07 13:26 [PATCH 0/2] Add device tree support for NXP i.MX95 15x15 FRDM board Lei Xu
2025-12-07 13:26 ` [PATCH 1/2] dt-bindings: arm: fsl: Add compatible for " Lei Xu
2025-12-08 7:13 ` Krzysztof Kozlowski
2025-12-07 13:26 ` [PATCH 2/2] arm64: dts: freescale: imx95: Add support " Lei Xu
2025-12-08 6:57 ` Francesco Dolcini [this message]
2025-12-10 7:05 ` Lei Xu
2025-12-10 7:59 ` Francesco Dolcini
2025-12-10 9:07 ` Lei Xu
2025-12-08 9:15 ` Marc Kleine-Budde
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=20251208065707.GA15128@francesco-nb \
--to=francesco@dolcini.it \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=justin.jiang@nxp.com \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=lei.xu@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=qijian.guo@nxp.com \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@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;
as well as URLs for NNTP newsgroup(s).