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 1/3] dt-bindings: arm64: add Marvell 7k COMe boards
Date: Mon, 02 Mar 2026 16:43:58 +0100 [thread overview]
Message-ID: <87ms0qfd8h.fsf@BLaptop.bootlin.com> (raw)
In-Reply-To: <20260122165923.2316510-2-enachman@marvell.com>
Elad Nachman <enachman@marvell.com> writes:
> From: Elad Nachman <enachman@marvell.com>
>
> Add dt bindings for:
> Armada 7020 COM Express CPU module
> Falcon DB-98CX85x0 COM Express type 7 Carrier board
> Falcon DB-98CX85x0 COM Express type 7 Carrier board
> with an Armada 7020 COM Express CPU module
>
> Signed-off-by: Elad Nachman <enachman@marvell.com>
Applied on mvebu/dt64
Thanks,
Gregory
> ---
> .../devicetree/bindings/arm/marvell/armada-7k-8k.yaml | 11 +++++++++++
> 1 file changed, 11 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/arm/marvell/armada-7k-8k.yaml b/Documentation/devicetree/bindings/arm/marvell/armada-7k-8k.yaml
> index 4bc7454a5d3a..7e77310da626 100644
> --- a/Documentation/devicetree/bindings/arm/marvell/armada-7k-8k.yaml
> +++ b/Documentation/devicetree/bindings/arm/marvell/armada-7k-8k.yaml
> @@ -21,6 +21,17 @@ properties:
> - const: marvell,armada-ap806-dual
> - const: marvell,armada-ap806
>
> + - description:
> + Falcon (DB-98CX85x0) Development board COM Express Carrier plus
> + Armada 7020 SoC COM Express CPU module
> + items:
> + - const: marvell,armada7020-falcon-carrier
> + - const: marvell,db-falcon-carrier
> + - const: marvell,armada7020-cpu-module
> + - const: marvell,armada7020
> + - const: marvell,armada-ap806-dual
> + - const: marvell,armada-ap806
> +
> - description: Armada 7040 SoC
> items:
> - enum:
> --
> 2.25.1
>
--
Grégory CLEMENT, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2026-03-02 15:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-22 16:59 [PATCH 0/2] arm64: dts: a7k: add COM Express boards Elad Nachman
2026-01-22 16:59 ` [PATCH 1/3] dt-bindings: arm64: add Marvell 7k COMe boards Elad Nachman
2026-01-22 23:21 ` Rob Herring (Arm)
2026-03-02 15:43 ` Gregory CLEMENT [this message]
2026-03-06 23:46 ` Rob Herring
2026-03-13 15:49 ` Gregory CLEMENT
2026-03-13 15:49 ` Gregory CLEMENT
2026-01-22 16:59 ` [PATCH 2/3] arm64: dts: a7k: add COM Express boards Elad Nachman
2026-01-22 16:59 ` [PATCH 3/3] MAINTAINERS: Add Falcon DB Elad Nachman
2026-01-22 18:07 ` [PATCH 0/2] arm64: dts: a7k: add COM Express boards Rob Herring
2026-01-23 9:10 ` Gregory CLEMENT
2026-01-23 9:20 ` Maxime Chevallier
2026-01-23 9:27 ` Gregory CLEMENT
2026-01-27 16:23 ` Rob Herring
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=87ms0qfd8h.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