Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
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.5
Date: Fri, 9 Jun 2023 10:14:36 +0100	[thread overview]
Message-ID: <20230609091435.GA3741@willie-the-truck> (raw)

Hi Joerg,

Please pull these Arm SMMU updates for 6.5. There's the usual summary
in the tag, but the most important thing is a crop of errata workarounds
from Robin for Arm's MMU-700 SMMUv3 implementation.

Cheers,

Will

--->8

The following changes since commit 44c026a73be8038f03dbdeef028b642880cf1511:

  Linux 6.4-rc3 (2023-05-21 14:05:48 -0700)

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 c5fb66a17a4362a8990e0d3d050c1c5a415dfc7e:

  Merge branch 'for-joerg/arm-smmu/bindings' into for-joerg/arm-smmu/updates (2023-06-08 22:27:26 +0100)

----------------------------------------------------------------
Arm SMMU updates for 6.5

- Device-tree binding updates:
  * Add missing clocks for SC8280XP and SA8775 Adreno SMMUs
  * Add two new Qualcomm SMMUs in SDX75 and SM6375

- Workarounds for Arm MMU-700 errata:
  * 1076982: Avoid use of SEV-based cmdq wakeup
  * 2812531: Terminate command batches with a CMD_SYNC
  * Enforce single-stage translation to avoid nesting-related errata

- Set the correct level hint for range TLB invalidation on teardown

----------------------------------------------------------------
Bartosz Golaszewski (1):
      dt-bindings: iommu: arm,smmu: enable clocks for sa8775p Adreno SMMU

Bjorn Andersson (1):
      dt-bindings: arm-smmu: Fix SC8280XP Adreno binding

Konrad Dybcio (1):
      dt-bindings: arm-smmu: Add SM6375 GPU SMMU

Robin Murphy (5):
      iommu/arm-smmu-v3: Work around MMU-600 erratum 1076982
      iommu/arm-smmu-v3: Document MMU-700 erratum 2812531
      iommu/arm-smmu-v3: Add explicit feature for nesting
      iommu/arm-smmu-v3: Document nesting-related errata
      iommu/arm-smmu-v3: Set TTL invalidation hint better

Rohit Agarwal (1):
      dt-bindings: arm-smmu: Add SDX75 SMMU compatible

Will Deacon (1):
      Merge branch 'for-joerg/arm-smmu/bindings' into for-joerg/arm-smmu/updates

 Documentation/arm64/silicon-errata.rst             |  4 ++
 .../devicetree/bindings/iommu/arm,smmu.yaml        | 12 +++--
 drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c        | 59 +++++++++++++++++++++-
 drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.h        |  8 +++
 4 files changed, 78 insertions(+), 5 deletions(-)

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

             reply	other threads:[~2023-06-09  9:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-09  9:14 Will Deacon [this message]
2023-06-09 12:58 ` [GIT PULL] iommu/arm-smmu: Updates for 6.5 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=20230609091435.GA3741@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