From: Krzysztof Kozlowski <krzk@kernel.org>
To: Yanan Yang <yanan.yang@nxp.com>, 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>
Cc: 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
Subject: Re: [PATCH v2 1/2] dt-bindings: arm: fsl: Add FRDM-IMX91S board
Date: Mon, 15 Dec 2025 12:59:49 +0100 [thread overview]
Message-ID: <31617f79-4cdb-4c8f-89f5-8ca1a3b3d054@kernel.org> (raw)
In-Reply-To: <20251215-imx91s-frdm-v2-1-87996bdaa59c@nxp.com>
On 15/12/2025 09:42, Yanan Yang wrote:
> Add DT compatible string for NXP FRDM-IMX91S board
>
> The FRDM-IMX91S is a low-cost, compact development board based on the
> i.MX91 applications processor. It is a cost-optimized variant of the
> FRDM-IMX91 board, with notable hardware differences requiring a separate
> DTS:
> - 512MB LPDDR4 (FRDM-IMX91 uses 1GB)
> - 256MB FlexSPI-NAND (FRDM-IMX91 uses 8GB eMMC)
> - Single GbE port (FRDM-IMX91 has dual GbE)
> - PMIC PF9453 (FRDM-IMX91 uses PCA9451A)
>
> Signed-off-by: Yanan Yang <yanan.yang@nxp.com>
>
Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-12-15 11:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-15 8:42 [PATCH v2 0/2] Add NXP FRDM-IMX91S board support Yanan Yang
2025-12-15 8:42 ` [PATCH v2 1/2] dt-bindings: arm: fsl: Add FRDM-IMX91S board Yanan Yang
2025-12-15 11:59 ` Krzysztof Kozlowski [this message]
2025-12-15 8:42 ` [PATCH v2 2/2] arm64: dts: freescale: add NXP FRDM-IMX91S board support Yanan Yang
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=31617f79-4cdb-4c8f-89f5-8ca1a3b3d054@kernel.org \
--to=krzk@kernel.org \
--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=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=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;
as well as URLs for NNTP newsgroup(s).