From: Peng Fan <peng.fan@oss.nxp.com>
To: Marek Vasut <marex@nabladev.com>
Cc: linux-arm-kernel@lists.infradead.org,
Fedor Ross <fedor.ross@ifm.com>,
Christian Eggers <ceggers@arri.de>,
Conor Dooley <conor+dt@kernel.org>,
Fabio Estevam <festevam@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Markus Heidelberg <m.heidelberg@cab.de>,
Rob Herring <robh@kernel.org>, Shawn Guo <shawnguo@kernel.org>,
devicetree@vger.kernel.org, imx@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 4/4] arm64: dts: imx8mn: Add ifm VHIP4 EvalBoard v1 and v2
Date: Wed, 7 Jan 2026 09:29:06 +0800 [thread overview]
Message-ID: <aV224uyLvqX8J+x3@shlinux89> (raw)
In-Reply-To: <20260106190147.31924-4-marex@nabladev.com>
On Tue, Jan 06, 2026 at 08:00:40PM +0100, Marek Vasut wrote:
>From: Fedor Ross <fedor.ross@ifm.com>
>
>Add support for ifm i.MX8MN VHIP4 EvalBoard v1 and v2 reference design.
>This system exists in two generations, v1 and v2, which share a lot of
>commonality. The boards come with either single gigabit ethernet or an
>KSZ8794 fast-ethernet switch, boot from eMMC, and offer CAN interfaces
>via Microchip MCP25xx SPI CAN controllers, UART, and USB host. The GPU
>is not available in the SoC populated on these devices.
>
>Signed-off-by: Fedor Ross <fedor.ross@ifm.com>
>Signed-off-by: Marek Vasut <marex@nabladev.com>
Reviewed-by: Peng Fan <peng.fan@nxp.com>
next prev parent reply other threads:[~2026-01-07 1:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-06 19:00 [PATCH v5 1/4] dt-bindings: vendor-prefixes: Document ifm electronic gmbh Marek Vasut
2026-01-06 19:00 ` [PATCH v5 2/4] dt-bindings: arm: fsl: Document ifm VHIP4 EvalBoard v1 and v2 Marek Vasut
2026-01-06 19:00 ` [PATCH v5 3/4] arm64: dts: imx8mn: Add SNVS LPGPR Marek Vasut
2026-01-06 19:00 ` [PATCH v5 4/4] arm64: dts: imx8mn: Add ifm VHIP4 EvalBoard v1 and v2 Marek Vasut
2026-01-07 1:29 ` Peng Fan [this message]
2026-01-17 7:24 ` [PATCH v5 1/4] dt-bindings: vendor-prefixes: Document ifm electronic gmbh Shawn Guo
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=aV224uyLvqX8J+x3@shlinux89 \
--to=peng.fan@oss.nxp.com \
--cc=ceggers@arri.de \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=fedor.ross@ifm.com \
--cc=festevam@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=imx@lists.linux.dev \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.heidelberg@cab.de \
--cc=marex@nabladev.com \
--cc=robh@kernel.org \
--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