From: Gregory CLEMENT <gregory.clement@bootlin.com>
To: Arnd Bergmann <arnd@arndb.de>, Olof Johansson <olof@lixom.net>,
arm@kernel.org, soc@kernel.org
Cc: Andrew Lunn <andrew@lunn.ch>,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
linux-arm-kernel@lists.infradead.org,
Chris Packham <chris.packham@alliedtelesis.co.nz>,
Vadym Kochan <vadym.kochan@plvision.eu>
Subject: Re: [GIT PULL] ARM: mvebu: dt64 for v5.20 (#1)
Date: Tue, 19 Jul 2022 15:25:27 +0200 [thread overview]
Message-ID: <87fsixqlo8.fsf@BL-laptop> (raw)
In-Reply-To: <87o7xlqn6x.fsf@BL-laptop>
Hello,
> Hi,
>
> Here is the first pull request for dt64 for mvebu for v5.20.
>
> Sorry to be late, actually I've just realized this week we were already
> at -rc7.
>
> Gregory
>
> The following changes since commit f2906aa863381afb0015a9eb7fefad885d4e5a56:
>
> Linux 5.19-rc1 (2022-06-05 17:18:54 -0700)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/gclement/mvebu.git tags/mvebu-dt64-5.20-1
>
> for you to fetch changes up to df9c42a99a89f3e8c613ec669fa9a10637c96231:
>
> arm64: marvell: enable the 98DX2530 pinctrl driver (2022-07-18 12:47:18 +0200)
>
> ----------------------------------------------------------------
> mvebu dt64 for 5.20 (part 1)
>
> Add support for Marvell 98DX2530 (and variants)
>
> ----------------------------------------------------------------
> Chris Packham (3):
> dt-bindings: marvell: Document the AC5/AC5X compatibles
> arm64: dts: marvell: Add Armada 98DX2530 SoC and RD-AC5X board
As seen with Arnd on IRC, I fixed the cpu node for this patch by using
the specific cpu type: cortex-a55 instead of the generic one amrv8.
So I am replacing this tag by an updated one, and a new pull request is
coming soon.
Gregory
> 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 +++++++++++++++++++++
> arch/arm64/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
>
> --
> Gregory Clement, Bootlin
> Embedded Linux and Kernel engineering
> http://bootlin.com
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
--
Gregory Clement, Bootlin
Embedded Linux and Kernel engineering
http://bootlin.com
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2022-07-19 13:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-19 12:52 [GIT PULL] ARM: mvebu: dt64 for v5.20 (#1) Gregory CLEMENT
2022-07-19 13:25 ` 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=87fsixqlo8.fsf@BL-laptop \
--to=gregory.clement@bootlin.com \
--cc=andrew@lunn.ch \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=chris.packham@alliedtelesis.co.nz \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=olof@lixom.net \
--cc=sebastian.hesselbarth@gmail.com \
--cc=soc@kernel.org \
--cc=vadym.kochan@plvision.eu \
/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