From: thierry.reding@gmail.com (Thierry Reding)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 5/5] arm64: tegra: Changes for v4.16-rc1
Date: Wed, 20 Dec 2017 20:19:00 +0100 [thread overview]
Message-ID: <20171220191900.757-5-thierry.reding@gmail.com> (raw)
In-Reply-To: <20171220191900.757-1-thierry.reding@gmail.com>
Hi ARM SoC maintainers,
The following changes since commit 4fbd8d194f06c8a3fd2af1ce560ddb31f7ec8323:
Linux 4.15-rc1 (2017-11-26 16:01:47 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git tags/tegra-for-4.16-arm64-dt
for you to fetch changes up to 50f5b841ba06f4dfb739e7a5ab9b87e8173d5915:
arm64: tegra: Use sor1_out clock (2017-12-15 10:14:17 +0100)
Thanks,
Thierry
----------------------------------------------------------------
arm64: tegra: Changes for v4.16-rc1
This set of patches enables a bunch of new features on Jetson TX2 that
were finally unblocked by the GPIO driver getting merged for v4.15.
----------------------------------------------------------------
Jon Hunter (1):
arm64: tegra: Add CPU and PSCI nodes for NVIDIA Tegra210 platforms
Thierry Reding (12):
dt-bindings: misc: Add Tegra186 MISC registers bindings
dt-bindings: memory: Add Tegra186 support
arm64: tegra: Add MISC registers on Tegra186
arm64: tegra: Add FUSE block on Tegra186
arm64: tegra: Add memory controller on Tegra186
arm64: tegra: Enable memory controller on P3310
arm64: tegra: Add SMMU node for Tegra186
arm64: tegra: Add display nodes on Tegra186
arm64: tegra: Mark I2C4 as DDC on P3310
arm64: tegra: Enable HDMI on Jetson TX2
arm64: tegra: Fix SD write-protect polarity on Jetson TX2
arm64: tegra: Use sor1_out clock
.../memory-controllers/nvidia,tegra30-mc.txt | 2 +
.../bindings/misc/nvidia,tegra186-misc.txt | 12 +
arch/arm64/boot/dts/nvidia/tegra186-p2771-0000.dts | 51 +++
arch/arm64/boot/dts/nvidia/tegra186-p3310.dtsi | 10 +-
arch/arm64/boot/dts/nvidia/tegra186.dtsi | 351 +++++++++++++++++++++
arch/arm64/boot/dts/nvidia/tegra210-p2180.dtsi | 23 ++
arch/arm64/boot/dts/nvidia/tegra210-p2530.dtsi | 23 ++
arch/arm64/boot/dts/nvidia/tegra210.dtsi | 4 +-
include/dt-bindings/memory/tegra186-mc.h | 111 +++++++
9 files changed, 582 insertions(+), 5 deletions(-)
create mode 100644 Documentation/devicetree/bindings/misc/nvidia,tegra186-misc.txt
create mode 100644 include/dt-bindings/memory/tegra186-mc.h
next prev parent reply other threads:[~2017-12-20 19:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-20 19:18 [GIT PULL 1/5] dt-bindings: Updates for v4.16-rc1 Thierry Reding
2017-12-20 19:18 ` [GIT PULL 2/5] soc/tegra: Changes " Thierry Reding
2017-12-20 20:00 ` Dmitry Osipenko
2017-12-21 16:12 ` [GIT PULL v2 " Thierry Reding
2017-12-21 17:04 ` Arnd Bergmann
2017-12-20 19:18 ` [GIT PULL 3/5] memory: tegra: " Thierry Reding
2017-12-21 17:07 ` Arnd Bergmann
2017-12-20 19:18 ` [GIT PULL 4/5] ARM: tegra: Device tree changes " Thierry Reding
2017-12-21 16:55 ` Arnd Bergmann
2017-12-20 19:19 ` Thierry Reding [this message]
2017-12-21 16:56 ` [GIT PULL 5/5] arm64: tegra: Changes " Arnd Bergmann
2017-12-21 16:54 ` [GIT PULL 1/5] dt-bindings: Updates " 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=20171220191900.757-5-thierry.reding@gmail.com \
--to=thierry.reding@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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).