From: Peng Fan <peng.fan@oss.nxp.com>
To: Primoz Fiser <primoz.fiser@norik.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,
upstream@lists.phytec.de
Subject: Re: [PATCH 2/2] arm64: dts: freescale: Add PHYTEC phyBOARD-Nash-i.MX93 support
Date: Tue, 29 Apr 2025 20:06:49 +0800 [thread overview]
Message-ID: <20250429120649.GC28789@nxa18884-linux> (raw)
In-Reply-To: <20250425064107.174548-2-primoz.fiser@norik.com>
On Fri, Apr 25, 2025 at 08:41:07AM +0200, Primoz Fiser wrote:
>Add initial support for PHYTEC phyBOARD-Nash-i.MX93 board [1] based on
>the PHYTEC phyCORE-i.MX93 SoM (System-on-Module) [2].
>
>Supported board features:
> * ADC
> * CAN
> * Ethernet 2x
> * EEPROM
> * eMMC
> * Heartbeat LED
> * RTC
> * RS-232/RS-485
> * SD-card
> * TPM 2.0
> * USB
>
>For more details see the product pages for the development kit and the
>SoM:
>
>[1] https://www.phytec.eu/en/produkte/development-kits/phyboard-nash/
>[2] https://www.phytec.eu/en/produkte/system-on-modules/phycore-imx-91-93/
>
>Signed-off-by: Primoz Fiser <primoz.fiser@norik.com>
Reviewed-by: Peng Fan <peng.fan@nxp.com>
next prev parent reply other threads:[~2025-04-29 11:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-25 6:41 [PATCH 1/2] bindings: arm: fsl: Add PHYTEC phyBOARD-Nash-i.MX93 board Primoz Fiser
2025-04-25 6:41 ` [PATCH 2/2] arm64: dts: freescale: Add PHYTEC phyBOARD-Nash-i.MX93 support Primoz Fiser
2025-04-28 14:31 ` [Upstream] " Wadim Egorov
2025-05-05 7:04 ` Primoz Fiser
2025-04-29 12:06 ` Peng Fan [this message]
2025-04-28 8:29 ` [PATCH 1/2] bindings: arm: fsl: Add PHYTEC phyBOARD-Nash-i.MX93 board Krzysztof Kozlowski
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=20250429120649.GC28789@nxa18884-linux \
--to=peng.fan@oss.nxp.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=primoz.fiser@norik.com \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=upstream@lists.phytec.de \
/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