From: Krzysztof Kozlowski <krzk@kernel.org>
To: Olof Johansson <olof@lixom.net>, Arnd Bergmann <arnd@arndb.de>,
arm@kernel.org, soc@kernel.org
Cc: linux-samsung-soc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Krzysztof Kozlowski <krzk@kernel.org>,
linux-kernel@vger.kernel.org
Subject: [GIT PULL 3/4] arm64: dts: exynos: Pull for v5.11
Date: Tue, 1 Dec 2020 22:44:03 +0200 [thread overview]
Message-ID: <20201201204404.22675-3-krzk@kernel.org> (raw)
In-Reply-To: <20201201204404.22675-1-krzk@kernel.org>
The following changes since commit 3650b228f83adda7e5ee532e2b90429c03f7b9ec:
Linux 5.10-rc1 (2020-10-25 15:14:11 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/krzk/linux.git tags/samsung-dt64-5.11
for you to fetch changes up to f74e93032df229a8358617e586ba89f744d5dbcd:
arm64: dts: exynos: Drop incorrect use of io-channel-ranges property (2020-11-17 20:47:55 +0100)
----------------------------------------------------------------
Samsung DTS ARM64 changes for v5.11
1. Several cleanups, including aligning node names with dtschema.
2. Add WiFi/PCIe to TM2 boards (Exynos5433).
3. Correct restart and shutdown of Exynos7 boards, as part of Paweł
Chmiel Exynos7420 mainlining effort.
----------------------------------------------------------------
Jaehoon Chung (1):
arm64: dts: exynos: add the WiFi/PCIe support to TM2(e) boards
Jonathan Cameron (1):
arm64: dts: exynos: Drop incorrect use of io-channel-ranges property
Krzysztof Kozlowski (4):
arm64: dts: exynos: adjust node names to DT spec in Exynos5433 TM2
arm64: dts: exynos: adjust node names to DT spec in Exynos7 Espresso
arm64: dts: exynos: remove redundant status=okay in Exynos5433 TM2
arm64: dts: exynos: use hyphens in Exynos5433 node names
Paweł Chmiel (2):
arm64: dts: exynos: Include common syscon restart/poweroff for Exynos7
arm64: dts: exynos: Correct psci compatible used on Exynos7
Serge Semin (1):
arm64: dts: exynos: Harmonize DWC USB3 DT nodes name
arch/arm64/boot/dts/exynos/exynos5433-bus.dtsi | 10 ++---
arch/arm64/boot/dts/exynos/exynos5433-pinctrl.dtsi | 2 +-
.../boot/dts/exynos/exynos5433-tm2-common.dtsi | 39 +++++++++++++----
arch/arm64/boot/dts/exynos/exynos5433.dtsi | 49 ++++++++++++++++++----
arch/arm64/boot/dts/exynos/exynos7-espresso.dts | 2 +-
arch/arm64/boot/dts/exynos/exynos7.dtsi | 15 +++----
6 files changed, 84 insertions(+), 33 deletions(-)
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-12-01 20:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-01 20:44 [GIT PULL 1/4] ARM: defconfig: samsung for v5.11 Krzysztof Kozlowski
2020-12-01 20:44 ` [GIT PULL 2/4] ARM: dts: " Krzysztof Kozlowski
2020-12-08 23:09 ` Arnd Bergmann
2020-12-01 20:44 ` Krzysztof Kozlowski [this message]
2020-12-08 23:09 ` [GIT PULL 3/4] arm64: dts: exynos: Pull " Arnd Bergmann
2020-12-01 20:44 ` [GIT PULL 4/4] ARM: samsung: " Krzysztof Kozlowski
2020-12-09 16:41 ` Arnd Bergmann
2020-12-08 16:34 ` [GIT PULL 1/4] ARM: defconfig: samsung " Arnd Bergmann
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=20201201204404.22675-3-krzk@kernel.org \
--to=krzk@kernel.org \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=olof@lixom.net \
--cc=soc@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).