From: Elad Nachman <enachman@marvell.com>
To: <robh+dt@kernel.org>, <krzysztof.kozlowski+dt@linaro.org>,
<conor+dt@kernel.org>, <andrew@lunn.ch>,
<gregory.clement@bootlin.com>, <sebastian.hesselbarth@gmail.com>,
<pali@kernel.org>, <mrkiko.rs@gmail.com>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Cc: <enachman@marvell.com>, <cyuval@marvell.com>
Subject: [PATCH v3 0/3] arm64: dts: cn913x: add device trees for COM Express boards
Date: Thu, 26 Oct 2023 11:47:32 +0300 [thread overview]
Message-ID: <20231026084735.3595944-1-enachman@marvell.com> (raw)
From: Elad Nachman <enachman@marvell.com>
Add support for CN9130 and CN9131 COM Express Type 7 CPU
module boards by Marvell.
Define these COM Express CPU modules as dtsi, and
provide a dts file for a carrier board (Marvell AC5X RD
COM Express type 7 carrier board).
This Carrier board only utilizes the PCIe link, hence no
special device / driver support is provided by this dts file.
v3:
1) Remove acronym which creates warnings for checkpatch.pl
2) Correct compatibility string for ac5x rd board
3) Add above compatibility string to dt bindings
4) update MAINTAINERS file with ac5 series dts files
5) remove memory property from carrier dts
6) add comment explaining that OOB RGMII ethernet port
connector and PHY are both on CPU module
v2:
1) add compatibility string for the board
2) remove unneeded hard-coded PHY LED blinking mode initialization
3) Split the CPU portion of the carrier board to
dtsi files, and define a dts file for the AC5X RD
carrier board.
Elad Nachman (3):
arm64: dts: cn913x: add device trees for COM Express boards
dt-bindings: arm64: dts: add dt-bindings for ac5x rd carrier
MAINTAINERS: add ac5 to list of maintained Marvell dts files
.../bindings/arm/marvell/armada-7k-8k.yaml | 8 ++
MAINTAINERS | 1 +
arch/arm64/boot/dts/marvell/Makefile | 1 +
.../boot/dts/marvell/ac5x_rd_carrier.dts | 23 ++++
.../dts/marvell/cn9130-db-comexpress.dtsi | 101 ++++++++++++++++
.../dts/marvell/cn9131-db-comexpress.dtsi | 113 ++++++++++++++++++
6 files changed, 247 insertions(+)
create mode 100644 arch/arm64/boot/dts/marvell/ac5x_rd_carrier.dts
create mode 100644 arch/arm64/boot/dts/marvell/cn9130-db-comexpress.dtsi
create mode 100644 arch/arm64/boot/dts/marvell/cn9131-db-comexpress.dtsi
--
2.25.1
next reply other threads:[~2023-10-26 8:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-26 8:47 Elad Nachman [this message]
2023-10-26 8:47 ` [PATCH v3 1/3] arm64: dts: cn913x: add device trees for COM Express boards Elad Nachman
2023-10-26 17:32 ` Andrew Lunn
2023-10-27 11:12 ` Krzysztof Kozlowski
2023-10-26 8:47 ` [PATCH v3 2/3] dt-bindings: arm64: dts: add dt-bindings for ac5x rd carrier Elad Nachman
2023-10-26 14:08 ` Conor Dooley
2023-10-26 17:44 ` Andrew Lunn
2023-10-27 11:09 ` Krzysztof Kozlowski
2023-10-27 11:15 ` Krzysztof Kozlowski
2023-10-26 8:47 ` [PATCH v3 3/3] MAINTAINERS: add ac5 to list of maintained Marvell dts files Elad Nachman
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=20231026084735.3595944-1-enachman@marvell.com \
--to=enachman@marvell.com \
--cc=andrew@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=cyuval@marvell.com \
--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=mrkiko.rs@gmail.com \
--cc=pali@kernel.org \
--cc=robh+dt@kernel.org \
--cc=sebastian.hesselbarth@gmail.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;
as well as URLs for NNTP newsgroup(s).