devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Walle <michael@walle.cc>
To: Shawn Guo <shawnguo@kernel.org>, Sascha Hauer <s.hauer@pengutronix.de>
Cc: Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	Fabio Estevam <festevam@gmail.com>,
	NXP Linux Team <linux-imx@nxp.com>,
	Heiko Thiery <heiko.thiery@gmail.com>,
	Li Yang <leoyang.li@nxp.com>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	Michael Walle <michael@walle.cc>
Subject: [PATCH v3 0/2] arm64: dts: imx8mn: add 8MNANOD3L-EVK device tree
Date: Tue, 12 Apr 2022 16:32:36 +0200	[thread overview]
Message-ID: <20220412143238.1925059-1-michael@walle.cc> (raw)

Add support for the 8MNANOD3L-EVK which features a NXP IMX8MN SoC.

Patch 1 was formerly postet separately, but never picked up. So I've bumped
its version and added the actual device tree. Please note, there wasn't a
v1 nor a v2 of patch 2.

Michael Walle (2):
  dt-bindings: arm: fsl: add IMX8MN DDR3L eval board
  arm64: dts: imx8mn: add 8MNANOD3L-EVK device tree

 .../devicetree/bindings/arm/fsl.yaml          |   1 +
 arch/arm64/boot/dts/freescale/Makefile        |   1 +
 .../boot/dts/freescale/imx8mn-ddr3l-evk.dts   | 114 ++++++++++++++++++
 3 files changed, 116 insertions(+)
 create mode 100644 arch/arm64/boot/dts/freescale/imx8mn-ddr3l-evk.dts

-- 
2.30.2


             reply	other threads:[~2022-04-12 14:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-12 14:32 Michael Walle [this message]
2022-04-12 14:32 ` [PATCH v3 1/2] dt-bindings: arm: fsl: add IMX8MN DDR3L eval board Michael Walle
2022-04-12 14:32 ` [PATCH v3 2/2] arm64: dts: imx8mn: add 8MNANOD3L-EVK device tree Michael Walle
2022-04-18 12:06 ` [PATCH v3 0/2] " 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=20220412143238.1925059-1-michael@walle.cc \
    --to=michael@walle.cc \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=heiko.thiery@gmail.com \
    --cc=kernel@pengutronix.de \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=leoyang.li@nxp.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --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;
as well as URLs for NNTP newsgroup(s).