From: Gregory CLEMENT <gregory.clement@bootlin.com>
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>,
Vadym Kochan <vadym.kochan@plvision.eu>,
Chris Packham <chris.packham@alliedtelesis.co.nz>,
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
Cc: Elad Nachman <enachman@marvell.com>
Subject: Re: [PATCH v10 0/3] arm64: mvebu: Support for Marvell 98DX2530 (and variants)
Date: Mon, 18 Jul 2022 12:48:20 +0200 [thread overview]
Message-ID: <87tu7er91n.fsf@BL-laptop> (raw)
In-Reply-To: <20220705190934.6168-1-vadym.kochan@plvision.eu>
Vadym Kochan <vadym.kochan@plvision.eu> writes:
> This series adds support for the Marvell 98DX2530 SoC which is the Control and
> Management CPU integrated into the AlleyCat5/AlleyCat5X series of Marvell
> switches.
>
> The CPU core is an ARM Cortex-A55 with neon, simd and crypto extensions.
>
> This is fairly similar to the Armada-3700 SoC so most of the required
> peripherals are already supported. This series adds a devicetree and pinctrl
> driver for the SoC and the RD-AC5X-32G16HVG6HLG reference board.
>
> The pinctrl changes from v4 have been picked up and are in linux-next so I
> haven't included them in this round. That leaves just the dts files and a minor
> Kconfig update for arm64.
>
> Changes:
>
> v10:
> 1) Use different cnm clock for AC5 and AC5X DTSIs
>
> 2) Rename device-tree yaml binding to match the $id
>
> v9 (proposed by Marvell):
> It was discussed with Chris that Marvell will add some changes:
> 1) Rename "armada-" prefix in dts(i) file names to ac5, because
> Armada has not much common with AC5 SoC.
>
> 2) Add clock fixes:
> a) rename core_clock to cnm_clock
>
> b) remove axi_clock
>
> c) change cnm_clock to 325MHZ
>
> d) use cnm_clock for the UART
>
> Chris Packham (3):
> dt-bindings: marvell: Document the AC5/AC5X compatibles
> arm64: dts: marvell: Add Armada 98DX2530 SoC and RD-AC5X board
> arm64: marvell: enable the 98DX2530 pinctrl driver
>
> .../bindings/arm/marvell/marvell,ac5.yaml | 32 ++
> arch/arm64/Kconfig.platforms | 2 +
> arch/arm64/boot/dts/marvell/Makefile | 1 +
> arch/arm64/boot/dts/marvell/ac5-98dx25xx.dtsi | 291 ++++++++++++++++++
> .../boot/dts/marvell/ac5-98dx35xx-rd.dts | 101 ++++++
> arch/arm64/boot/dts/marvell/ac5-98dx35xx.dtsi | 17 +
> 6 files changed, 444 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/arm/marvell/marvell,ac5.yaml
> create mode 100644 arch/arm64/boot/dts/marvell/ac5-98dx25xx.dtsi
> create mode 100644 arch/arm64/boot/dts/marvell/ac5-98dx35xx-rd.dts
> create mode 100644 arch/arm64/boot/dts/marvell/ac5-98dx35xx.dtsi
>
Series applied on mvebu/dt64
Thanks,
Gregory
> --
> 2.17.1
>
--
Gregory Clement, Bootlin
Embedded Linux and Kernel engineering
http://bootlin.com
prev parent reply other threads:[~2022-07-18 10:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-05 19:09 [PATCH v10 0/3] arm64: mvebu: Support for Marvell 98DX2530 (and variants) Vadym Kochan
2022-07-05 19:09 ` [PATCH v10 1/3] dt-bindings: marvell: Document the AC5/AC5X compatibles Vadym Kochan
2022-07-06 7:50 ` Krzysztof Kozlowski
2022-07-05 19:09 ` [PATCH v10 2/3] arm64: dts: marvell: Add Armada 98DX2530 SoC and RD-AC5X board Vadym Kochan
2022-07-05 19:09 ` [PATCH v10 3/3] arm64: marvell: enable the 98DX2530 pinctrl driver Vadym Kochan
2022-07-05 21:02 ` [PATCH v10 0/3] arm64: mvebu: Support for Marvell 98DX2530 (and variants) Chris Packham
2022-07-18 10:48 ` Gregory CLEMENT [this message]
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=87tu7er91n.fsf@BL-laptop \
--to=gregory.clement@bootlin.com \
--cc=andrew@lunn.ch \
--cc=catalin.marinas@arm.com \
--cc=chris.packham@alliedtelesis.co.nz \
--cc=devicetree@vger.kernel.org \
--cc=enachman@marvell.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).