From: Francesco Dolcini <francesco@dolcini.it>
To: "Yanan.Yang" <yanan.yang@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,
qijian.guo@nxp.com, justin.jiang@nxp.com, Lei Xu <lei.xu@nxp.com>,
Xiaofeng Wei <xiaofeng.wei@nxp.com>
Subject: Re: [PATCH 2/2] arm64: dts: freescale: add NXP FRDM-IMX91S board support
Date: Fri, 5 Dec 2025 10:04:08 +0100 [thread overview]
Message-ID: <20251205090408.GA48399@francesco-nb> (raw)
In-Reply-To: <20251205-imx91s-frdm-v1-2-afd6cd01c299@nxp.com>
On Fri, Dec 05, 2025 at 05:03:59PM +0900, Yanan.Yang wrote:
> Add DeviceTree support for the NXP FRDM-IMX91S development board based
> on the i.MX91 SoC. FRDM-IMX91S is a cost-optimized variant of FRDM-IMX91
> and differs in memory, storage, Ethernet, and PMIC configuration:
>
> - 512MB LPDDR4 (FRDM-IMX91 uses 1GB)
> - 256MB FlexSPI-NAND (FRDM-IMX91 uses 8GB eMMC)
> - Single GbE port (FRDM-IMX91 has dual GbE)
...
> +
> + aliases {
> + ethernet0 = &fec;
> + ethernet1 = &eqos;
Single ethernet port, and 2 ethernet aliases. Please fix
Francesco
next prev parent reply other threads:[~2025-12-05 9:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-05 8:03 [PATCH 0/2] Add NXP FRDM-IMX91S board support Yanan.Yang
2025-12-05 8:03 ` [PATCH 1/2] dt-bindings: arm: fsl: Add FRDM-IMX91S board Yanan.Yang
2025-12-05 8:21 ` Krzysztof Kozlowski
2025-12-10 6:31 ` Yanan Yang
2025-12-11 1:16 ` Krzysztof Kozlowski
2025-12-11 1:55 ` Yanan Yang
2025-12-05 8:03 ` [PATCH 2/2] arm64: dts: freescale: add NXP FRDM-IMX91S board support Yanan.Yang
2025-12-05 8:23 ` Krzysztof Kozlowski
2025-12-05 9:04 ` Francesco Dolcini [this message]
2025-12-08 2:17 ` Joseph Guo
2025-12-08 9:13 ` 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=20251205090408.GA48399@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 \
--cc=xiaofeng.wei@nxp.com \
--cc=yanan.yang@nxp.com \
/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