From: Vadym Kochan <vadym.kochan@plvision.eu>
To: robh+dt@kernel.org,
Chris Packham <chris.packham@alliedtelesis.co.nz>,
krzysztof.kozlowski+dt@linaro.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, vadym.kochan@plvision.eu
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Chris Packham <chris.packham@alliedtelesis.co.nz>
Subject: Re: [PATCH v8 2/3] arm64: dts: marvell: Add Armada 98DX2530 SoC and RD-AC5X board
Date: Tue, 7 Jun 2022 14:49:36 +0300 [thread overview]
Message-ID: <20220607114936.GA18404@plvision.eu> (raw)
In-Reply-To: <20220515233047.531979-3-chris.packham@alliedtelesis.co.nz>
Hi All,
> arch/arm64/boot/dts/marvell/Makefile | 1 +
> .../boot/dts/marvell/armada-98dx25xx.dtsi | 297 ++++++++++++++++++
> .../boot/dts/marvell/armada-98dx35xx-rd.dts | 101 ++++++
> .../boot/dts/marvell/armada-98dx35xx.dtsi | 13 +
There is a proposal from the Marvell to replace "armada-" prefix to "ac5-" in DTS naming as there
is no much common with Armada SoC's.
Regards,
Vadym Kochan
next prev parent reply other threads:[~2022-06-07 11:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-15 23:30 [PATCH v8 0/3] arm64: mvebu: Support for Marvell 98DX2530 (and variants) Chris Packham
2022-05-15 23:30 ` [PATCH v8 1/3] dt-bindings: marvell: Document the AC5/AC5X compatibles Chris Packham
2022-05-15 23:30 ` [PATCH v8 2/3] arm64: dts: marvell: Add Armada 98DX2530 SoC and RD-AC5X board Chris Packham
2022-05-17 23:14 ` Chris Packham
2022-05-26 22:46 ` Chris Packham
2022-06-07 11:49 ` Vadym Kochan [this message]
2022-06-07 12:07 ` Andrew Lunn
2022-06-07 21:40 ` Chris Packham
2022-05-15 23:30 ` [PATCH v8 3/3] 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=20220607114936.GA18404@plvision.eu \
--to=vadym.kochan@plvision.eu \
--cc=20220515233047.531979-3-chris.packham@alliedtelesis.co.nz \
--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=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).