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 4/7] ARM: tegra: Device tree changes for v7.1-rc1
Date: Sun, 29 Mar 2026 17:10:41 +0200 [thread overview]
Message-ID: <20260329151045.1443133-4-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-arm-dt
for you to fetch changes up to ce74a6c6d88ba9ee29a6b99ac97ffcded577c85d:
ARM: tegra: paz00: Configure WiFi rfkill switch through device tree (2026-03-28 00:56:36 +0100)
Thanks,
Thierry
----------------------------------------------------------------
ARM: tegra: Device tree changes for v7.1-rc1
Various improvements for Tegra114 boards, as well as some legacy cleanup
for PAZ00 and Transformers devices.
----------------------------------------------------------------
Dmitry Torokhov (1):
ARM: tegra: paz00: Configure WiFi rfkill switch through device tree
Svyatoslav Ryhel (8):
ARM: tegra: Add SOCTHERM support on Tegra114
ARM: tn7: Adjust panel node
ARM: tegra: lg-x3: Add panel and bridge nodes
ARM: tegra: lg-x3: Add USB and power related nodes
ARM: tegra: lg-x3: Add node for capacitive buttons
ARM: tegra: Add ACTMON node to Tegra114 device tree
ARM: tegra: Add External Memory Controller node on Tegra114
ARM: tegra: transformers: Add connector node
arch/arm/boot/dts/nvidia/tegra114-tn7.dts | 13 +-
arch/arm/boot/dts/nvidia/tegra114.dtsi | 221 +++++++++++++++++++++++
arch/arm/boot/dts/nvidia/tegra20-paz00.dts | 8 +
arch/arm/boot/dts/nvidia/tegra30-asus-tf600t.dts | 21 ++-
arch/arm/boot/dts/nvidia/tegra30-lg-p880.dts | 23 +++
arch/arm/boot/dts/nvidia/tegra30-lg-p895.dts | 33 ++++
arch/arm/boot/dts/nvidia/tegra30-lg-x3.dtsi | 174 +++++++++++++++++-
arch/arm/mach-tegra/Makefile | 2 -
arch/arm/mach-tegra/board-paz00.c | 56 ------
arch/arm/mach-tegra/board.h | 2 -
arch/arm/mach-tegra/tegra.c | 4 -
11 files changed, 482 insertions(+), 75 deletions(-)
delete mode 100644 arch/arm/mach-tegra/board-paz00.c
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 ` Thierry Reding [this message]
2026-03-29 15:10 ` [GIT PULL 5/7] ARM: tegra: Default configuration changes " Thierry Reding
2026-03-29 15:10 ` [GIT PULL 6/7] arm64: tegra: Device tree " Thierry Reding
2026-03-29 15:10 ` [GIT PULL 7/7] arm64: tegra: Default configuration " 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-4-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