From: Masahiro Yamada <yamada.masahiro@socionext.com>
To: Arnd Bergmann <arnd@arndb.de>, arm-soc <arm@kernel.org>,
Olof Johansson <olof@lixom.net>
Cc: linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
masahiroy@kernel.org
Subject: [GIT PULL] ARM: dts: uniphier: UniPhier DT updates for v4.20
Date: Wed, 3 Oct 2018 08:47:14 +0900 [thread overview]
Message-ID: <CAK7LNAQnPeNwmmKL_BWSnzEsUCq+MW+5c2TXWnuszOBi32iybg@mail.gmail.com> (raw)
Hi Arnd, Olof,
Please pull UniPhier DT updates for the v4.20 MW.
In this cycle, I queued up all arm/arm64 changes
into a single branch to avoid build errors.
Thanks!
The following changes since commit 5b394b2ddf0347bef56e50c69a58773c94343ff3:
Linux 4.19-rc1 (2018-08-26 14:11:59 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-uniphier.git
tags/uniphier-dt-v4.20
for you to fetch changes up to 84a9c4d55907feece68c6012d3c030cf5c841ceb:
arm64: dts: uniphier: add SD controller nodes (2018-10-03 08:21:27 +0900)
----------------------------------------------------------------
UniPhier ARM SoC DT updates for v4.20
- Add more clocks to NAND controller nodes
- Add SPI controller nodes
- Add SD controller nodes
----------------------------------------------------------------
Kunihiko Hayashi (3):
ARM: dts: uniphier: add SPI pin-mux node
ARM: dts: uniphier: add SPI node for UniPhier 32bit SoCs
arm64: dts: uniphier: add SPI node for LD20, LD11 and PXs3
Masahiro Yamada (4):
ARM: uniphier: dts: add more clocks to Denali NAND controller node
arm64: uniphier: dts: add more clocks to Denali NAND controller node
ARM: dts: uniphier: add SD/eMMC controller nodes
arm64: dts: uniphier: add SD controller nodes
arch/arm/boot/dts/uniphier-ld4-ref.dts | 4 ++
arch/arm/boot/dts/uniphier-ld4.dtsi | 48 ++++++++++++++-
arch/arm/boot/dts/uniphier-ld6b-ref.dts | 4 ++
arch/arm/boot/dts/uniphier-pinctrl.dtsi | 25 ++++++++
arch/arm/boot/dts/uniphier-pro4-ace.dts | 4 ++
arch/arm/boot/dts/uniphier-pro4-ref.dts | 4 ++
arch/arm/boot/dts/uniphier-pro4-sanji.dts | 4 ++
arch/arm/boot/dts/uniphier-pro4.dtsi | 62 +++++++++++++++++++-
arch/arm/boot/dts/uniphier-pro5.dtsi | 59 ++++++++++++++++++-
arch/arm/boot/dts/uniphier-pxs2-gentil.dts | 4 ++
arch/arm/boot/dts/uniphier-pxs2-vodka.dts | 4 ++
arch/arm/boot/dts/uniphier-pxs2.dtsi | 59 ++++++++++++++++++-
arch/arm/boot/dts/uniphier-sld8-ref.dts | 4 ++
arch/arm/boot/dts/uniphier-sld8.dtsi | 48 ++++++++++++++-
arch/arm64/boot/dts/socionext/uniphier-ld11.dtsi | 25 +++++++-
arch/arm64/boot/dts/socionext/uniphier-ld20.dtsi | 61 ++++++++++++++++++-
.../boot/dts/socionext/uniphier-pxs3-ref.dts | 4 ++
arch/arm64/boot/dts/socionext/uniphier-pxs3.dtsi | 43 +++++++++++++-
18 files changed, 458 insertions(+), 8 deletions(-)
--
Best Regards
Masahiro Yamada
next reply other threads:[~2018-10-02 23:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-02 23:47 Masahiro Yamada [this message]
2018-10-03 2:05 ` [GIT PULL] ARM: dts: uniphier: UniPhier DT updates for v4.20 Masahiro Yamada
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=CAK7LNAQnPeNwmmKL_BWSnzEsUCq+MW+5c2TXWnuszOBi32iybg@mail.gmail.com \
--to=yamada.masahiro@socionext.com \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=olof@lixom.net \
/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).