From: Will Deacon <will@kernel.org>
To: joro@8bytes.org
Cc: iommu@lists.linux.dev, 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 6.7
Date: Fri, 13 Oct 2023 13:02:06 +0100 [thread overview]
Message-ID: <20231013120205.GA13843@willie-the-truck> (raw)
Hi Joerg,
Please pull these Arm SMMU updates for 6.7. Usual summary in the tag,
but the bulk of this is refactoring to the way in which the SMMUv3
driver handles context descriptors in preparation for implementing the
'->set_dev_pasid()' operation for non-SVA domains. And of course there's
the obligatory DT updates for Qualcomm platforms.
Cheers,
Will
--->8
The following changes since commit d5afb4b47e13161b3f33904d45110f9e6463bad6:
iommu/arm-smmu-v3: Fix soft lockup triggered by arm_smmu_mm_invalidate_range (2023-09-22 11:15:42 +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 548650921e617c7909c7f3229067e58ad3cb8088:
Merge branch 'for-joerg/arm-smmu/bindings' into for-joerg/arm-smmu/updates (2023-10-13 11:43:12 +0100)
----------------------------------------------------------------
Arm SMMU updates for 6.7
- Device-tree binding update:
* Add qcom,sm7150-smmu-v2 for Adreno on SM7150 SoC
- SMMUv2:
* Support for Qualcomm SDM670 (MDSS) and SM7150 SoCs
- SMMUv3:
* Large refactoring of the context descriptor code to
move the CD table into the master, paving the way
for '->set_dev_pasid()' support on non-SVA domains
* Minor cleanups to the SVA code
----------------------------------------------------------------
Danila Tikhonov (2):
dt-bindings: arm-smmu: Add SM7150 GPU SMMUv2
iommu/arm-smmu-qcom: Add SM7150 SMMUv2
Michael Shavit (11):
iommu/arm-smmu-v3: Move ctx_desc out of s1_cfg
iommu/arm-smmu-v3: Replace s1_cfg with cdtab_cfg
iommu/arm-smmu-v3: Encapsulate ctx_desc_cfg init in alloc_cd_tables
iommu/arm-smmu-v3: move stall_enabled to the cd table
iommu/arm-smmu-v3: Refactor write_ctx_desc
iommu/arm-smmu-v3: Move CD table to arm_smmu_master
iommu/arm-smmu-v3: Cleanup arm_smmu_domain_finalise
iommu/arm-smmu-v3: Update comment about STE liveness
iommu/arm-smmu-v3: Rename cdcfg to cd_table
iommu/arm-smmu-v3-sva: Remove unused iommu_sva handle
iommu/arm-smmu-v3-sva: Remove bond refcount
Richard Acayan (1):
iommu/arm-smmu-qcom: Add SDM670 MDSS compatible
Will Deacon (1):
Merge branch 'for-joerg/arm-smmu/bindings' into for-joerg/arm-smmu/updates
.../devicetree/bindings/iommu/arm,smmu.yaml | 2 +
drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3-sva.c | 71 +++---
drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c | 253 ++++++++++-----------
drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.h | 17 +-
drivers/iommu/arm/arm-smmu/arm-smmu-qcom.c | 2 +
5 files changed, 178 insertions(+), 167 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:[~2023-10-13 12:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-13 12:02 Will Deacon [this message]
2023-10-16 7:35 ` [GIT PULL] iommu/arm-smmu: Updates for 6.7 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=20231013120205.GA13843@willie-the-truck \
--to=will@kernel.org \
--cc=iommu@lists.linux.dev \
--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