From: Thierry Reding <thierry.reding@gmail.com>
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 3/3] arm64: tegra: Device tree fixes for v6.14-rc1
Date: Fri, 10 Jan 2025 19:53:53 +0100 [thread overview]
Message-ID: <20250110185355.4143505-3-thierry.reding@gmail.com> (raw)
In-Reply-To: <20250110185355.4143505-1-thierry.reding@gmail.com>
Hi ARM SoC maintainers,
The following changes since commit 40384c840ea1944d7c5a392e8975ed088ecf0b37:
Linux 6.13-rc1 (2024-12-01 14:28:56 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git tags/tegra-for-6.14-arm64-dt
for you to fetch changes up to b615fbd70fce8582d92b3bdbbf3c9b80cadcfb55:
arm64: tegra: Fix Tegra234 PCIe interrupt-map (2025-01-10 18:47:01 +0100)
Thanks,
Thierry
----------------------------------------------------------------
arm64: tegra: Device tree fixes for v6.14-rc1
These patches fix up an issue with the DMA support on one of the SPI
controllers, as well as properly identify the SCE fabric and disable
it to prevent accessing registers that may not be accessible to the
CPU. Finally, the GIC's #address-cells property is set to 0 to fix a
problem in the PCIe interrupt-map property.
----------------------------------------------------------------
Akhil R (1):
arm64: tegra: Fix DMA ID for SPI2
Brad Griffis (1):
arm64: tegra: Fix Tegra234 PCIe interrupt-map
Sumit Gupta (2):
arm64: tegra: Fix typo in Tegra234 dce-fabric compatible
arm64: tegra: Disable Tegra234 sce-fabric node
arch/arm64/boot/dts/nvidia/tegra234.dtsi | 8 +++++---
1 file changed, 5 insertions(+), 3 deletions(-)
prev parent reply other threads:[~2025-01-10 18:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-10 18:53 [GIT PULL 1/3] soc/tegra: Cleanups for v6.14-rc1 Thierry Reding
2025-01-10 18:53 ` [GIT PULL 2/3] ARM: tegra: Device tree fixes " Thierry Reding
2025-01-10 18:53 ` Thierry Reding [this message]
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=20250110185355.4143505-3-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 \
--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;
as well as URLs for NNTP newsgroup(s).