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] arm64: tegra: Device tree fixes for v5.14-rc1
Date: Fri, 9 Jul 2021 17:02:20 +0200 [thread overview]
Message-ID: <20210709150220.2543875-1-thierry.reding@gmail.com> (raw)
Hi ARM SoC maintainers,
The following changes since commit c7289b1c8a4e10bbbdb7097a71a90652beb767a1:
arm64: tegra: Enable SMMU support on Tegra194 (2021-06-11 13:33:46 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git tags/tegra-for-5.14-arm64-dt-fixes
for you to fetch changes up to c667dcd4dfcd515ad2c9b3953a33d742985a0b5e:
arm64: tegra: Enable SMMU support for USB on Tegra194 (2021-07-09 16:50:44 +0200)
This is based on the main ARM64 device tree changes pull request that I
sent out a couple of weeks ago. It'd be great to get this into v5.14-rc1
or shortly after.
Thanks,
Thierry
----------------------------------------------------------------
arm64: tegra: Device tree fixes for v5.14-rc1
This contains two late fixes for Tegra194 device tree files to restore
USB and audio functionality after enabling system-wide IOMMU support.
----------------------------------------------------------------
Thierry Reding (2):
arm64: tegra: Enable audio IOMMU support on Tegra194
arm64: tegra: Enable SMMU support for USB on Tegra194
arch/arm64/boot/dts/nvidia/tegra194.dtsi | 13 +++++++++++++
1 file changed, 13 insertions(+)
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2021-07-09 15:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-09 15:02 Thierry Reding [this message]
2021-07-16 21:24 ` [GIT PULL] arm64: tegra: Device tree fixes for v5.14-rc1 Arnd Bergmann
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=20210709150220.2543875-1-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).