From: Yannic Moog <y.moog@phytec.de>
To: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Shawn Guo <shawnguo@kernel.org>, Li Yang <leoyang.li@nxp.com>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
NXP Linux Team <linux-imx@nxp.com>
Cc: <devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<upstream@lists.phytec.de>, Yannic Moog <y.moog@phytec.de>
Subject: [PATCH 0/2] Add support for the phyGATE-Tauri-L IoT Gateway
Date: Fri, 1 Sep 2023 11:26:15 +0200 [thread overview]
Message-ID: <20230901-tauri_upstream_support-v1-0-ed30c6df789b@phytec.de> (raw)
The phyGATE-Tauri-L is a SBC that uses the phyCORE-i.MX8MM SoM, but has
a different carrier board.
This series adds support for the board and most of its interfaces.
Notably, RS485 support is missing.
Signed-off-by: Yannic Moog <y.moog@phytec.de>
---
Yannic Moog (2):
dt-bindings: arm: fsl: add phyGATE-Tauri-L board
arm64: dts: freescale: add phyGATE-Tauri i.MX 8M Mini Support
Documentation/devicetree/bindings/arm/fsl.yaml | 4 +-
arch/arm64/boot/dts/freescale/Makefile | 1 +
.../boot/dts/freescale/imx8mm-phygate-tauri-l.dts | 488 +++++++++++++++++++++
3 files changed, 492 insertions(+), 1 deletion(-)
---
base-commit: 2dde18cd1d8fac735875f2e4987f11817cc0bc2c
change-id: 20230828-tauri_upstream_support-08fac2175150
Best regards,
--
Yannic Moog <y.moog@phytec.de>
next reply other threads:[~2023-09-01 9:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-01 9:26 Yannic Moog [this message]
2023-09-01 9:26 ` [PATCH 1/2] dt-bindings: arm: fsl: add phyGATE-Tauri-L board Yannic Moog
2023-09-01 15:39 ` Conor Dooley
2023-09-01 9:26 ` [PATCH 2/2] arm64: dts: freescale: add phyGATE-Tauri i.MX 8M Mini Support Yannic Moog
2023-09-25 1:26 ` Shawn Guo
2023-09-25 6:57 ` Yannic Moog
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=20230901-tauri_upstream_support-v1-0-ed30c6df789b@phytec.de \
--to=y.moog@phytec.de \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@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 \
--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;
as well as URLs for NNTP newsgroup(s).