From: Gregory CLEMENT <gregory.clement@bootlin.com>
To: Elad Nachman <enachman@marvell.com>,
robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
conor+dt@kernel.org, andrew@lunn.ch,
sebastian.hesselbarth@gmail.com, pali@kernel.org,
mrkiko.rs@gmail.com, chris.packham@alliedtelesis.co.nz,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Cc: enachman@marvell.com
Subject: Re: [PATCH v2 0/3] arm64: dts: a7k: add COM Express boards
Date: Mon, 26 Jan 2026 11:30:07 +0100 [thread overview]
Message-ID: <87sebsk6og.fsf@BLaptop.bootlin.com> (raw)
In-Reply-To: <20260125152347.2518538-1-enachman@marvell.com>
Hello Elad,
> From: Elad Nachman <enachman@marvell.com>
>
> Add support for Armada 7020 Express Type 7 CPU module board by Marvell.
> Add device tree bindings for this board.
> Define this COM Express CPU module as dtsi and provide a dtsi file for
> the carrier board (Marvell DB-98CX85x0 COM Express type 7 carrier board).
>
> Since memory is soldered on CPU module, memory node is on CPU module
> dtsi file.
>
> This Carrier board only utilizes the PCIe link, hence no special device
> or driver support is provided by this dtsi file.
> Devise a dts file for the combined com express carrier and CPU module.
>
> The Aramda 7020 CPU COM Express board offers the following features:
>
> 1. Armada 7020 CPU, with dual ARM A72 cores
> 2. DDR4 memory, 8GB, on board soldered
> 3. 1Gbit Out of Band Ethernet via RGMII to PHY and RJ45 connector,
> all are present on A7K CPU module (none on the carrier)
> 4. Optional 10G KR Ethernet going via the COM Express type 7 connector
> 5. On-board 8 Gbit, 8-bit bus width NAND flash
> 6. On-board 512 Mbit SPI flash
> 7. PCIe Root Complex, 4 lanes PCIe gen3 connectivity, going via the
> COM Express type 7 connector
> 8. m.2 SATA connector
> 9. Micro-SD card connector
> 10. USB 2.0 via COM Express type 7 connector
> 11. Two i2c interfaces - one to the CPU module, and one to the
> carrier board via the COM Express type 7 connector
> 12. UART (mini USB connector by virtue of FT2232D UART to USB
> converter, connected to the Armada 7020 UART0)
>
> v2:
> 1) update 10gbase-kr to 10gbase-r in dtsi
>
I’ve already merged your previous version with this fix and even
included it in the PR for the next release.
However, I noticed a comment from Andrew. Could you provide a fix for
it, and I’ll try to include it i
Thanks,
Gregory
> Elad Nachman (3):
> dt-bindings: arm64: add Marvell 7k COMe boards
> arm64: dts: a7k: add COM Express boards
> MAINTAINERS: Add Falcon DB
>
> .../bindings/arm/marvell/armada-7k-8k.yaml | 11 ++
> MAINTAINERS | 1 +
> arch/arm64/boot/dts/marvell/Makefile | 1 +
> .../dts/marvell/armada-7020-comexpress.dtsi | 161 ++++++++++++++++++
> arch/arm64/boot/dts/marvell/armada-70x0.dtsi | 7 +
> .../boot/dts/marvell/armada-ap806-dual.dtsi | 4 +-
> .../dts/marvell/db-falcon-carrier-a7k.dts | 27 +++
> .../boot/dts/marvell/db-falcon-carrier.dtsi | 22 +++
> 8 files changed, 232 insertions(+), 2 deletions(-)
> create mode 100644 arch/arm64/boot/dts/marvell/armada-7020-comexpress.dtsi
> create mode 100644 arch/arm64/boot/dts/marvell/db-falcon-carrier-a7k.dts
> create mode 100644 arch/arm64/boot/dts/marvell/db-falcon-carrier.dtsi
>
> --
> 2.25.1
>
--
Grégory CLEMENT, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2026-01-26 10:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-25 15:23 [PATCH v2 0/3] arm64: dts: a7k: add COM Express boards Elad Nachman
2026-01-25 15:23 ` [PATCH v2 1/3] dt-bindings: arm64: add Marvell 7k COMe boards Elad Nachman
2026-01-25 15:23 ` [PATCH v2 2/3] arm64: dts: a7k: add COM Express boards Elad Nachman
2026-01-25 16:28 ` Andrew Lunn
2026-01-25 15:23 ` [PATCH v2 3/3] MAINTAINERS: Add Falcon DB Elad Nachman
2026-01-26 10:30 ` Gregory CLEMENT [this message]
2026-01-26 14:01 ` [PATCH v2 0/3] arm64: dts: a7k: add COM Express boards 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=87sebsk6og.fsf@BLaptop.bootlin.com \
--to=gregory.clement@bootlin.com \
--cc=andrew@lunn.ch \
--cc=chris.packham@alliedtelesis.co.nz \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=enachman@marvell.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