From: Thierry Reding <thierry.reding@kernel.org>
To: arm@kernel.org, soc@kernel.org
Cc: Thierry Reding <thierry.reding@kernel.org>,
Jon Hunter <jonathanh@nvidia.com>,
linux-tegra@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 1/7] Device tree bindings changes for v7.4-rc1
Date: Sat, 3 Oct 2026 11:59:16 +0200 [thread overview]
Message-ID: <20261003095924.1370238-1-thierry.reding@kernel.org> (raw)
From: Thierry Reding <thierry.reding@gmail.com>
Hi ARM SoC maintainers,
The following changes since commit cee9395acd8043be0644b25c34bfa86623f2b935:
Linux 7.3-rc1 (2026-08-30 13:34:40 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git tags/tegra-for-7.4-dt-bindings
for you to fetch changes up to 8370532640fa15b9480ba19af9314d3266c92aef:
dt-bindings: soc: tegra: pmc: Document Tegra210B01 (2026-10-03 00:39:13 +0200)
Thanks,
Thierry
----------------------------------------------------------------
Device tree bindings changes for v7.4-rc1
This contains a minor fix for the Tegra132 external memory controller
bindings as well as additions of compatible strings for Tegra264 and
Tegra210-B01 to existing bindings. Also, the new Motorola Artix 4G and
Droid X2 devices are documented.
----------------------------------------------------------------
Aaron Kling (1):
dt-bindings: soc: tegra: pmc: Document Tegra210B01
Svyatoslav Ryhel (1):
dt-bindings: arm: tegra: Add Motorola Artix 4G and Droid X2
Thierry Reding (2):
dt-bindings: memory: tegra: Fix Tegra132 compatible string
dt-bindings: fuse: Document compatible string for Tegra264 FUSE
Documentation/devicetree/bindings/arm/tegra.yaml | 6 ++++++
.../devicetree/bindings/fuse/nvidia,tegra20-fuse.yaml | 1 +
.../bindings/memory-controllers/nvidia,tegra124-emc.yaml | 10 +++++++---
.../bindings/memory-controllers/nvidia,tegra124-mc.yaml | 1 +
.../devicetree/bindings/soc/tegra/nvidia,tegra20-pmc.yaml | 5 ++++-
5 files changed, 19 insertions(+), 4 deletions(-)
next reply other threads:[~2026-10-03 9:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-03 9:59 Thierry Reding [this message]
2026-10-03 9:59 ` [GIT PULL 2/7] ARM: Core changes for v7.4-rc1 Thierry Reding
2026-10-03 9:59 ` [GIT PULL 3/7] soc/tegra: Changes " Thierry Reding
2026-10-03 9:59 ` [GIT PULL 4/7] firmware/tegra: " Thierry Reding
2026-10-03 9:59 ` [GIT PULL 5/7] ARM: tegra: " Thierry Reding
2026-10-03 9:59 ` [GIT PULL 6/7] arm64: " Thierry Reding
2026-10-03 9:59 ` [GIT PULL 7/7] arm64: tegra: Default configuration changes " 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=20261003095924.1370238-1-thierry.reding@kernel.org \
--to=thierry.reding@kernel.org \
--cc=arm@kernel.org \
--cc=jonathanh@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-tegra@vger.kernel.org \
--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