public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: "Joseph Guo (OSS)" <qijian.guo@oss.nxp.com>
To: Fabio Estevam <festevam@gmail.com>, Joseph Guo <qijian.guo@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>, Frank Li <Frank.Li@nxp.com>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	imx@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
	xinyu.chen@nxp.com, justin.jiang@nxp.com
Subject: Re: [PATCH v2 2/2] arm64: dts: freescale: add i.MX95 19x19 FRDM PRO board dts
Date: Wed, 29 Apr 2026 12:17:55 +0800	[thread overview]
Message-ID: <846f10e4-dbe7-4f93-a98d-82cabb086810@oss.nxp.com> (raw)
In-Reply-To: <CAOMZO5DV4Nnc+7DfAZT-VYDqxniz=ROR4-DnH3x9NbU4E8d9mQ@mail.gmail.com>

On 4/29/2026 9:37 AM, Fabio Estevam wrote:
> On Tue, Apr 28, 2026 at 5:03 AM Joseph Guo <qijian.guo@nxp.com> wrote:
>>
>> NXP i.MX95 19x19 FRDM PRO is cost-effective with extensive
>> expansion capabilities based on the i.MX95 19x19 SoC.
> 
> It would be good to explain the difference between the i.MX95 FRDM PRO
> and i.MX95 FRDM.
> 
> Also, does it make sense to share common nodes in a dtsi that can be
> used by the two variants?

Hi Fabio,

Yes, I will explain the difference between these two boards in next version.

But actually these two boards have totally different hardware design. So actually only few nodes which
are not related to the hardware (which means the IPs inside the SoC) can be common. 
Their SoC is also different package. 95 FRDM PRO is 19x19 and 95 15x15 FRDM is 15x15.
I think it is enough to create a individual dts for this board.

Regards,
Joseph


  reply	other threads:[~2026-04-29  4:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-28  8:03 [PATCH v2 0/2] Add NXP FRDM-IMX95-PRO board support Joseph Guo
2026-04-28  8:03 ` [PATCH v2 1/2] dt-bindings: arm: fsl: Add i.MX95 19x19 FRDM PRO board Joseph Guo
2026-04-28  8:03 ` [PATCH v2 2/2] arm64: dts: freescale: add i.MX95 19x19 FRDM PRO board dts Joseph Guo
2026-04-29  1:37   ` Fabio Estevam
2026-04-29  4:17     ` Joseph Guo (OSS) [this message]
2026-04-29  9:26   ` Daniel Baluta
2026-04-29  9:26     ` Joseph Guo (OSS)
2026-04-29  9:31       ` Daniel Baluta
2026-04-29  9:29         ` Joseph Guo (OSS)
2026-04-29 12:46       ` Francesco Dolcini

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=846f10e4-dbe7-4f93-a98d-82cabb086810@oss.nxp.com \
    --to=qijian.guo@oss.nxp.com \
    --cc=Frank.Li@nxp.com \
    --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=xinyu.chen@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