From: Josua Mayer <josua@solid-run.com>
To: Andrew Lunn <andrew@lunn.ch>,
Gregory Clement <gregory.clement@bootlin.com>,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: Yazan Shhady <yazan.shhady@solid-run.com>,
linux-arm-kernel@lists.infradead.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Josua Mayer <josua@solid-run.com>
Subject: [PATCH 0/2] arm64: dts: add description for solidrun cn9130 som and clearfog boards
Date: Thu, 21 Mar 2024 22:47:10 +0100 [thread overview]
Message-ID: <20240321-cn9130-som-v1-0-711127a409ae@solid-run.com> (raw)
SolidRun CN9130 SoM is a mostly pin-comptible replacement for Armada 388
SoM used in Clearfog and Clearfog Pro boards.
1. Add new binding for compatible strings closely matching the original.
2. Add device-tree includes for SoM and carrier shared design.
3. Add device-tree for both Clearfog Base and Pro.
NOTICE IN CASE ANYBODY WANTS TO SELF-UPGRADE:
CN9130 SoM has a different footprint from Armada 388 SoM.
Components on the carrier board below the SoM may collide causing
damage, such as on Clearfog Base.
Signed-off-by: Josua Mayer <josua@solid-run.com>
---
Josua Mayer (2):
dt-bindings: arm64: marvell: add solidrun cn9130 clearfog boards
arm64: dts: add description for solidrun cn9130 som and clearfog boards
.../bindings/arm/marvell/armada-7k-8k.yaml | 12 +
arch/arm64/boot/dts/marvell/Makefile | 2 +
arch/arm64/boot/dts/marvell/cn9130-cf-base.dts | 138 ++++++++++++
arch/arm64/boot/dts/marvell/cn9130-cf-pro.dts | 249 +++++++++++++++++++++
arch/arm64/boot/dts/marvell/cn9130-cf.dtsi | 198 ++++++++++++++++
arch/arm64/boot/dts/marvell/cn9130-sr-som.dtsi | 160 +++++++++++++
6 files changed, 759 insertions(+)
---
base-commit: e8f897f4afef0031fe618a8e94127a0934896aba
change-id: 20240318-cn9130-som-848e86acb0ac
Sincerely,
--
Josua Mayer <josua@solid-run.com>
next reply other threads:[~2024-03-21 21:47 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-21 21:47 Josua Mayer [this message]
2024-03-21 21:47 ` [PATCH 1/2] dt-bindings: arm64: marvell: add solidrun cn9130 " Josua Mayer
2024-03-22 2:16 ` Rob Herring
2024-03-22 10:08 ` Josua Mayer
2024-03-25 19:34 ` Krzysztof Kozlowski
2024-03-25 20:12 ` Josua Mayer
2024-03-26 6:41 ` Krzysztof Kozlowski
2024-03-26 19:26 ` Josua Mayer
2024-03-27 10:19 ` Krzysztof Kozlowski
2024-03-27 10:55 ` Josua Mayer
2024-03-28 9:14 ` Krzysztof Kozlowski
2024-03-28 9:33 ` Josua Mayer
2024-03-28 9:41 ` Krzysztof Kozlowski
2024-03-28 9:46 ` Josua Mayer
2024-03-28 16:22 ` Josua Mayer
2024-03-21 21:47 ` [PATCH 2/2] arm64: dts: add description for solidrun cn9130 som and " Josua Mayer
2024-03-21 21:59 ` Andrew Lunn
2024-03-22 9:54 ` Josua Mayer
2024-03-22 13:11 ` Andrew Lunn
2024-03-22 15:38 ` Josua Mayer
2024-03-22 15:49 ` Andrew Lunn
2024-03-22 15:58 ` Josua Mayer
2024-03-22 18:14 ` Josua Mayer
2024-03-22 18:27 ` Andrew Lunn
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=20240321-cn9130-som-v1-0-711127a409ae@solid-run.com \
--to=josua@solid-run.com \
--cc=andrew@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregory.clement@bootlin.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=sebastian.hesselbarth@gmail.com \
--cc=yazan.shhady@solid-run.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
all inboxes | Powered by JetHome®