From: Thierry Reding <thierry.reding@gmail.com>
To: arm@kernel.org
Cc: linux-tegra@vger.kernel.org,
Thierry Reding <thierry.reding@gmail.com>,
linux-arm-kernel@lists.infradead.org,
Jon Hunter <jonathanh@nvidia.com>
Subject: [GIT PULL 1/8] dt-bindings: Changes for v5.5-rc1
Date: Sat, 2 Nov 2019 15:45:14 +0100 [thread overview]
Message-ID: <20191102144521.3863321-1-thierry.reding@gmail.com> (raw)
Hi ARM SoC maintainers,
The following changes since commit 54ecb8f7028c5eb3d740bb82b0f1d90f2df63c5c:
Linux 5.4-rc1 (2019-09-30 10:35:40 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git tags/tegra-for-5.5-dt-bindings
for you to fetch changes up to 641262f5e1ed5c96799e17595893fa1a703616ac:
dt-bindings: memory: Add binding for NVIDIA Tegra30 External Memory Controller (2019-10-29 20:22:34 +0100)
Thanks,
Thierry
----------------------------------------------------------------
dt-bindings: Changes for v5.5-rc1
This contains various updates to device tree bindings and includes that
are related to driver changes in other Tegra branches.
----------------------------------------------------------------
Dmitry Osipenko (4):
dt-bindings: regulator: Document regulators coupling of NVIDIA Tegra20/30 SoCs
dt-bindings: memory: tegra30: Convert to Tegra124 YAML
dt-bindings: memory: Add binding for NVIDIA Tegra30 Memory Controller
dt-bindings: memory: Add binding for NVIDIA Tegra30 External Memory Controller
Thierry Reding (1):
dt-bindings: clock: tegra: Rename SOR0_LVDS to SOR0_OUT
.../memory-controllers/nvidia,tegra124-mc.yaml | 152 ++++++++++
.../memory-controllers/nvidia,tegra30-emc.yaml | 336 +++++++++++++++++++++
.../memory-controllers/nvidia,tegra30-mc.txt | 123 --------
.../memory-controllers/nvidia,tegra30-mc.yaml | 167 ++++++++++
.../regulator/nvidia,tegra-regulators-coupling.txt | 65 ++++
include/dt-bindings/clock/tegra124-car-common.h | 3 +-
include/dt-bindings/clock/tegra210-car.h | 3 +-
7 files changed, 724 insertions(+), 125 deletions(-)
create mode 100644 Documentation/devicetree/bindings/memory-controllers/nvidia,tegra124-mc.yaml
create mode 100644 Documentation/devicetree/bindings/memory-controllers/nvidia,tegra30-emc.yaml
delete mode 100644 Documentation/devicetree/bindings/memory-controllers/nvidia,tegra30-mc.txt
create mode 100644 Documentation/devicetree/bindings/memory-controllers/nvidia,tegra30-mc.yaml
create mode 100644 Documentation/devicetree/bindings/regulator/nvidia,tegra-regulators-coupling.txt
next reply other threads:[~2019-11-02 14:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-02 14:45 Thierry Reding [this message]
2019-11-02 14:45 ` [GIT PULL 2/8] firmware: tegra: Changes for v5.5-rc1 Thierry Reding
2019-11-02 14:45 ` [GIT PULL 3/8] memory: " Thierry Reding
2019-11-04 1:33 ` Olof Johansson
2019-11-04 15:34 ` Dmitry Osipenko
2019-11-07 15:32 ` Thierry Reding
2019-11-11 14:38 ` [GIT PULL v2 " Thierry Reding
2019-11-02 14:45 ` [GIT PULL 4/8] soc/tegra: " Thierry Reding
2019-11-02 14:45 ` [GIT PULL 5/8] ARM: tegra: Core changes " Thierry Reding
2019-11-02 14:45 ` [GIT PULL 6/8] ARM: tegra: Device tree " Thierry Reding
2019-11-02 14:45 ` [GIT PULL 7/8] ARM: tegra: Default configuration " Thierry Reding
2019-11-02 14:45 ` [GIT PULL 8/8] arm64: tegra: Device tree " Thierry Reding
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=20191102144521.3863321-1-thierry.reding@gmail.com \
--to=thierry.reding@gmail.com \
--cc=arm@kernel.org \
--cc=jonathanh@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-tegra@vger.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).