[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <35f98bc2-dc26-4441-8ed3-1ecce582d0d2@lunn.ch>
Date: Mon, 27 Nov 2023 23:33:42 +0100
From: Andrew Lunn <andrew@...n.ch>
To: Elad Nachman <enachman@...vell.com>
Cc: robh+dt@...nel.org, krzysztof.kozlowski+dt@...aro.org,
conor+dt@...nel.org, gregory.clement@...tlin.com,
sebastian.hesselbarth@...il.com, pali@...nel.org,
mrkiko.rs@...il.com, chris.packham@...iedtelesis.co.nz,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, cyuval@...vell.com
Subject: Re: [PATCH v6 3/3] arm64: dts: cn913x: add device trees for COM
Express boards
> +++ b/arch/arm64/boot/dts/marvell/ac5x-rd-carrier-cn9131.dts
> @@ -0,0 +1,25 @@
> +// SPDX-License-Identifier: (GPL-2.0+ OR MIT)
> +/*
> + * Copyright (C) 2023 Marvell International Ltd.
> + *
> + * Device tree for the AC5X RD Type 7 Com Express carrier board,
> + * Utilizing the CN913x COM Express CPU module board.
> + * This specific board only maintains a PCIe link with the CPU CPU module
> + * module, which does not require any special DTS definitions.
> + */
> +
> +#include "cn9131-db-comexpress.dtsi"
> +#include "ac5x-rd-carrier.dtsi"
> +
> +/ {
> + model = "Marvell Armada AC5X RD COM EXPRESS type 7 carrier board with CN9131 CPU module";
> + compatible = "marvell,cn9131-ac5x-carrier", "marvell,rd-ac5x-carrier",
> + "marvell,cn9131-cpu-module", "marvell,cn9131",
> + "marvell,armada-ap807-quad", "marvell,armada-ap807";
> diff --git a/arch/arm64/boot/dts/marvell/ac5x-rd-carrier.dtsi b/arch/arm64/boot/dts/marvell/ac5x-rd-carrier.dtsi
> new file mode 100644
> index 000000000000..fd45d5582233
> +/ {
> + model = "Marvell Armada AC5X RD COM EXPRESS type 7 carrier board";
> + compatible = "marvell,rd-ac5x-carrier";
Now i'm confused. What does rd mean?
I would expect RD mean Reference Design, and that is the complete
device in its box.
Yet, here you have RD for the carrier?
The box itself is called cn9131-ac5x-carrier?
This makes no sense to me.
Maybe i'm understanding this all wrong, and its the carrier which you
are producing a reference design for? The CPU module does not really
matter? I could use any off the shelf ComExpress 7 SOM. The bits you
are trying to sell are on the carrier? But since you are Marvell, you
don't want to recommend using an AMD ComExpress board when you happen
to also have CPU module which would work? But the CPU is not really
the point of this, its the carrier?
Andrew
Powered by blists - more mailing lists