From: Krzysztof Kozlowski <krzk@kernel.org>
To: Thierry Reding <thierry.reding@kernel.org>,
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: Re: [GIT PULL 4/7] ARM: tegra: Device tree changes for v7.1-rc1
Date: Mon, 30 Mar 2026 13:46:32 +0200 [thread overview]
Message-ID: <058d79b7-3d4c-4f0a-a95f-b2e3582a4fa7@kernel.org> (raw)
In-Reply-To: <20260329151045.1443133-4-thierry.reding@kernel.org>
On 29/03/2026 17:10, Thierry Reding wrote:
> ----------------------------------------------------------------
> 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 -
Why does the DTS branch has mach code? Tag message mentions legacy
cleanup only and such cleanup should not cause mixing independent
hardware description (DTS) with drivers.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-03-30 11:46 UTC|newest]
Thread overview: 11+ 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-30 11:46 ` Krzysztof Kozlowski [this message]
2026-03-29 15:10 ` [GIT PULL 5/7] ARM: tegra: Default configuration " Thierry Reding
2026-03-29 15:10 ` [GIT PULL 6/7] arm64: tegra: Device tree " Thierry Reding
2026-03-30 11:45 ` Krzysztof Kozlowski
2026-03-29 15:10 ` [GIT PULL 7/7] arm64: tegra: Default configuration " Thierry Reding
2026-03-30 11:39 ` [GIT PULL 1/7] dt-bindings: Changes " Krzysztof Kozlowski
2026-03-30 11:40 ` Krzysztof Kozlowski
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=058d79b7-3d4c-4f0a-a95f-b2e3582a4fa7@kernel.org \
--to=krzk@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 \
--cc=thierry.reding@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