From: Thierry Reding <thierry.reding@kernel.org>
To: arm@kernel.org, soc@kernel.org
Cc: Thierry Reding <thierry.reding@gmail.com>,
Jon Hunter <jonathanh@nvidia.com>,
linux-tegra@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 6/7] arm64: tegra: Device tree changes for v7.1-rc1
Date: Sun, 29 Mar 2026 17:10:43 +0200 [thread overview]
Message-ID: <20260329151045.1443133-6-thierry.reding@kernel.org> (raw)
In-Reply-To: <20260329151045.1443133-1-thierry.reding@kernel.org>
From: Thierry Reding <thierry.reding@gmail.com>
Hi ARM SoC maintainers,
The following changes since commit 6de23f81a5e08be8fbf5e8d7e9febc72a5b5f27f:
Linux 7.0-rc1 (2026-02-22 13:18:59 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git tags/tegra-for-7.1-arm64-dt
for you to fetch changes up to c70e6bc11d2008fbb19695394b69fd941ab39030:
arm64: tegra: Add Tegra264 GPIO controllers (2026-03-28 01:36:46 +0100)
Thanks,
Thierry
----------------------------------------------------------------
arm64: tegra: Device tree changes for v7.1-rc1
Various fixes and new additions across a number of devices. GPIO and PCI
are enabled on Tegra264 and the Jetson AGX Thor Developer Kit, allowing
it to boot via network and mass storage.
----------------------------------------------------------------
Diogo Ivo (1):
arm64: tegra: smaug: Enable SPI-NOR flash
Jon Hunter (1):
arm64: tegra: Fix RTC aliases
Prathamesh Shete (1):
arm64: tegra: Add Tegra264 GPIO controllers
Thierry Reding (6):
dt-bindings: pci: Document the NVIDIA Tegra264 PCIe controller
Merge branch for-7.1/dt-bindings into for-7.1/pci
arm64: tegra: Fix snps,blen properties
arm64: tegra: Drop redundant clock and reset names for TSEC
arm64: tegra: Add PCI controllers on Tegra264
arm64: tegra: Add Jetson AGX Thor Developer Kit support
.../bindings/pci/nvidia,tegra264-pcie.yaml | 149 +++++++++
arch/arm64/boot/dts/nvidia/Makefile | 2 +
arch/arm64/boot/dts/nvidia/tegra210-smaug.dts | 12 +
arch/arm64/boot/dts/nvidia/tegra210.dtsi | 2 -
arch/arm64/boot/dts/nvidia/tegra234-p3701.dtsi | 1 +
arch/arm64/boot/dts/nvidia/tegra234-p3767.dtsi | 1 +
arch/arm64/boot/dts/nvidia/tegra234.dtsi | 6 +-
.../dts/nvidia/tegra264-p4071-0000+p3834-0008.dts | 11 +
.../boot/dts/nvidia/tegra264-p4071-0000+p3834.dtsi | 12 +
arch/arm64/boot/dts/nvidia/tegra264.dtsi | 336 +++++++++++++++++++--
10 files changed, 500 insertions(+), 32 deletions(-)
create mode 100644 Documentation/devicetree/bindings/pci/nvidia,tegra264-pcie.yaml
create mode 100644 arch/arm64/boot/dts/nvidia/tegra264-p4071-0000+p3834-0008.dts
create mode 100644 arch/arm64/boot/dts/nvidia/tegra264-p4071-0000+p3834.dtsi
next prev parent reply other threads:[~2026-03-29 15:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-29 15:10 [GIT PULL 1/7] dt-bindings: Changes for v7.1-rc1 Thierry Reding
2026-03-29 15:10 ` [GIT PULL 2/7] soc/tegra: " Thierry Reding
2026-03-29 15:10 ` [GIT PULL 3/7] firmware: tegra: " Thierry Reding
2026-03-29 15:10 ` [GIT PULL 4/7] ARM: tegra: Device tree changes " Thierry Reding
2026-03-29 15:10 ` [GIT PULL 5/7] ARM: tegra: Default configuration " Thierry Reding
2026-03-29 15:10 ` Thierry Reding [this message]
2026-03-29 15:10 ` [GIT PULL 7/7] arm64: " 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=20260329151045.1443133-6-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 \
--cc=thierry.reding@gmail.com \
/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