From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Vadym Kochan <vadym.kochan@plvision.eu>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Chris Packham <chris.packham@alliedtelesis.co.nz>,
Gregory CLEMENT <gregory.clement@bootlin.com>,
Konstantin Porotchkin <kostap@marvell.com>,
Andrew Lunn <andrew@lunn.ch>,
Robert Marko <robert.marko@sartura.hr>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v9 1/3] dt-bindings: marvell: Document the AC5/AC5X compatibles
Date: Tue, 14 Jun 2022 13:58:35 -0700 [thread overview]
Message-ID: <57d11a55-beba-c91b-e168-989417e3910d@linaro.org> (raw)
In-Reply-To: <20220613225338.393-2-vadym.kochan@plvision.eu>
On 13/06/2022 15:53, Vadym Kochan wrote:
> From: Chris Packham <chris.packham@alliedtelesis.co.nz>
>
> Describe the compatible properties for the Marvell Alleycat5/5X switches
> with integrated CPUs.
>
> Alleycat5:
> * 98DX2538: 24x1G + 2x10G + 2x10G Stack
> * 98DX2535: 24x1G + 4x1G Stack
> * 98DX2532: 8x1G + 2x10G + 2x1G Stack
> * 98DX2531: 8x1G + 4x1G Stack
> * 98DX2528: 24x1G + 2x10G + 2x10G Stack
> * 98DX2525: 24x1G + 4x1G Stack
> * 98DX2522: 8x1G + 2x10G + 2x1G Stack
> * 98DX2521: 8x1G + 4x1G Stack
> * 98DX2518: 24x1G + 2x10G + 2x10G Stack
> * 98DX2515: 24x1G + 4x1G Stack
> * 98DX2512: 8x1G + 2x10G + 2x1G Stack
> * 98DX2511: 8x1G + 4x1G Stack
>
> Alleycat5X:
> * 98DX3500: 24x1G + 6x25G
> * 98DX3501: 16x1G + 6x10G
> * 98DX3510: 48x1G + 6x25G
> * 98DX3520: 24x2.5G + 6x25G
> * 98DX3530: 48x2.5G + 6x25G
> * 98DX3540: 12x5G/6x10G + 6x25G
> * 98DX3550: 24x5G/12x10G + 6x25G
>
> Signed-off-by: Chris Packham <chris.packham@alliedtelesis.co.nz>
> Signed-off-by: Vadym Kochan <vadym.kochan@plvision.eu>
> ---
>
> Notes:
> Changes in v9:
> - Renamed $id with "ac5" prefix
I guess this was the reason to drop review? Anyway this is unexpected
change considering the name does not appear in compatibles.
> Changes in v8:
> - Add review from Krzysztof
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-06-14 20:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-13 22:53 [PATCH v9 0/3] arm64: mvebu: Support for Marvell 98DX2530 (and variants) Vadym Kochan
2022-06-13 22:53 ` [PATCH v9 1/3] dt-bindings: marvell: Document the AC5/AC5X compatibles Vadym Kochan
2022-06-14 4:03 ` Chris Packham
2022-06-14 20:50 ` Rob Herring
2022-06-14 20:58 ` Krzysztof Kozlowski [this message]
2022-06-13 22:53 ` [PATCH v9 2/3] arm64: dts: marvell: Add Armada 98DX2530 SoC and RD-AC5X board Vadym Kochan
2022-06-14 5:11 ` Chris Packham
2022-06-14 5:26 ` Chris Packham
2022-06-14 8:16 ` Vadym Kochan
2022-06-14 21:25 ` Chris Packham
2022-06-15 0:03 ` Chris Packham
2022-07-05 4:59 ` Chris Packham
2022-06-13 22:53 ` [PATCH v9 3/3] arm64: marvell: enable the 98DX2530 pinctrl driver Vadym Kochan
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=57d11a55-beba-c91b-e168-989417e3910d@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=andrew@lunn.ch \
--cc=catalin.marinas@arm.com \
--cc=chris.packham@alliedtelesis.co.nz \
--cc=devicetree@vger.kernel.org \
--cc=gregory.clement@bootlin.com \
--cc=kostap@marvell.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robert.marko@sartura.hr \
--cc=robh+dt@kernel.org \
--cc=vadym.kochan@plvision.eu \
--cc=will@kernel.org \
/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).