From: Chris Packham <chris.packham@alliedtelesis.co.nz>
To: linus.walleij@linaro.org, robh+dt@kernel.org,
catalin.marinas@arm.com, will@kernel.org, andrew@lunn.ch,
gregory.clement@bootlin.com, sebastian.hesselbarth@gmail.com,
kostap@marvell.com, robert.marko@sartura.hr
Cc: linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Chris Packham <chris.packham@alliedtelesis.co.nz>
Subject: [PATCH v3 0/4] arm64: mvebu: Support for Marvell 98DX2530 (and variants)
Date: Wed, 6 Apr 2022 15:21:54 +1200 [thread overview]
Message-ID: <20220406032158.1449049-1-chris.packham@alliedtelesis.co.nz> (raw)
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.
In the v3 series I've dropped out a few patches. The MMC stuff is more
complicated than just adding a compatible string. The mvneta changes have gone
in via net-next.
Chris Packham (4):
dt-bindings: pinctrl: mvebu: Document bindings for AC5
pinctrl: mvebu: pinctrl driver for 98DX2530 SoC
arm64: dts: marvell: Add Armada 98DX2530 SoC and RD-AC5X board
arm64: marvell: enable the 98DX2530 pinctrl driver
.../bindings/pinctrl/marvell,ac5-pinctrl.yaml | 72 +++++
arch/arm64/Kconfig.platforms | 2 +
arch/arm64/boot/dts/marvell/Makefile | 1 +
.../boot/dts/marvell/armada-98dx2530.dtsi | 302 ++++++++++++++++++
arch/arm64/boot/dts/marvell/rd-ac5x.dts | 74 +++++
drivers/pinctrl/mvebu/Kconfig | 4 +
drivers/pinctrl/mvebu/Makefile | 1 +
drivers/pinctrl/mvebu/pinctrl-ac5.c | 261 +++++++++++++++
8 files changed, 717 insertions(+)
create mode 100644 Documentation/devicetree/bindings/pinctrl/marvell,ac5-pinctrl.yaml
create mode 100644 arch/arm64/boot/dts/marvell/armada-98dx2530.dtsi
create mode 100644 arch/arm64/boot/dts/marvell/rd-ac5x.dts
create mode 100644 drivers/pinctrl/mvebu/pinctrl-ac5.c
--
2.35.1
next reply other threads:[~2022-04-06 14:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-06 3:21 Chris Packham [this message]
2022-04-06 3:21 ` [PATCH v3 1/4] dt-bindings: pinctrl: mvebu: Document bindings for AC5 Chris Packham
2022-04-06 23:20 ` Andrew Lunn
2022-04-13 18:29 ` Rob Herring
2022-04-06 3:21 ` [PATCH v3 2/4] pinctrl: mvebu: pinctrl driver for 98DX2530 SoC Chris Packham
2022-04-06 12:36 ` Andrew Lunn
2022-04-06 21:51 ` Chris Packham
2022-04-06 23:17 ` Andrew Lunn
2022-04-06 3:21 ` [PATCH v3 3/4] arm64: dts: marvell: Add Armada 98DX2530 SoC and RD-AC5X board Chris Packham
2022-04-06 23:23 ` Andrew Lunn
2022-04-06 23:29 ` Chris Packham
2022-04-06 3:21 ` [PATCH v3 4/4] arm64: marvell: enable the 98DX2530 pinctrl driver Chris Packham
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=20220406032158.1449049-1-chris.packham@alliedtelesis.co.nz \
--to=chris.packham@alliedtelesis.co.nz \
--cc=andrew@lunn.ch \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=gregory.clement@bootlin.com \
--cc=kostap@marvell.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robert.marko@sartura.hr \
--cc=robh+dt@kernel.org \
--cc=sebastian.hesselbarth@gmail.com \
--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).