From: Will Deacon <will@kernel.org>
To: joro@8bytes.org
Cc: iommu@lists.linux-foundation.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, robin.murphy@arm.com,
kernel-team@android.com
Subject: [GIT PULL] iommu/arm-smmu: Updates for 5.19
Date: Tue, 10 May 2022 17:01:06 +0100 [thread overview]
Message-ID: <20220510160106.GA28351@willie-the-truck> (raw)
Hi Joerg,
Please pull these Arm SMMU updates for 5.19. The bulk of it is just adding
new device-tree compatible strings for the existing drivers, but there
are some non-critical fixes in here as well. Please see the tag for more
details.
I used the previous fixes pull as a base for this so that you shouldn't
run into any conflicts with upstream.
Cheers,
Will
--->8
The following changes since commit 4a25f2ea0e030b2fc852c4059a50181bfc5b2f57:
iommu: arm-smmu: disable large page mappings for Nvidia arm-smmu (2022-04-22 11:21:30 +0100)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/will/linux.git tags/arm-smmu-updates
for you to fetch changes up to 628bf55b620497a105f4963ee8fb84769f7e6bb4:
iommu/arm-smmu: Force identity domains for legacy binding (2022-05-10 12:01:31 +0100)
----------------------------------------------------------------
Arm SMMU updates for 5.19
- Add new Qualcomm device-tree compatible strings
- Add new Nvidia device-tree compatible string for Tegra234
- Fix UAF in SMMUv3 shared virtual addressing code
- Force identity-mapped domains for users of ye olde SMMU legacy binding
- Minor cleanups
----------------------------------------------------------------
Bjorn Andersson (2):
dt-bindings: arm-smmu: Add compatible for Qualcomm SC8280XP
iommu/arm-smmu-qcom: Add SC8280XP support
Jean-Philippe Brucker (1):
iommu/arm-smmu-v3-sva: Fix mm use-after-free
Robin Murphy (1):
iommu/arm-smmu: Force identity domains for legacy binding
Rohit Agarwal (1):
dt-bindings: arm-smmu: Add binding for SDX65 SMMU
Thierry Reding (3):
dt-bindings: arm-smmu: Document nvidia,memory-controller property
dt-bindings: arm-smmu: Add compatible for Tegra234 SOC
iommu/arm-smmu: Support Tegra234 SMMU
Yang Yingliang (2):
iommu/arm-smmu: fix possible null-ptr-deref in arm_smmu_device_probe()
iommu/arm-smmu-v3: check return value after calling platform_get_resource()
.../devicetree/bindings/iommu/arm,smmu.yaml | 25 ++++++++++++++++++++--
drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3-sva.c | 13 +++++++++--
drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c | 2 ++
drivers/iommu/arm/arm-smmu/arm-smmu-impl.c | 3 ++-
drivers/iommu/arm/arm-smmu/arm-smmu-qcom.c | 1 +
drivers/iommu/arm/arm-smmu/arm-smmu.c | 8 ++++---
6 files changed, 44 insertions(+), 8 deletions(-)
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2022-05-10 16:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-10 16:01 Will Deacon [this message]
2022-05-13 13:18 ` [GIT PULL] iommu/arm-smmu: Updates for 5.19 Joerg Roedel
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=20220510160106.GA28351@willie-the-truck \
--to=will@kernel.org \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robin.murphy@arm.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