Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Fri, 13 Jan 2023 11:03:18 +0000
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: Fixes for 6.2
Message-ID: <20230113110318.GA12771@willie-the-truck>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.10.1 (2018-07-13)
Precedence: bulk

Hi Joerg,

Please can you pull these Arm SMMU fixes for 6.2? The summary is in the
tag, but the main thing is fixing a VFIO regression due to the way in
which IOMMU_CAP_CACHE_COHERENCY is reported for SMMUv2 devices.

Cheers,

Will

--->8

The following changes since commit 1b929c02afd37871d5afb9d498426f83432e71c2:

  Linux 6.2-rc1 (2022-12-25 13:41:39 -0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/will/linux.git tags/arm-smmu-fixes

for you to fetch changes up to f1ba05a70f7df4e2e4d2d7fed2d4e63a1e700660:

  iommu/arm-smmu-v3: Don't unregister on shutdown (2023-01-11 12:20:00 +0000)

----------------------------------------------------------------
Arm SMMU fixes for 6.2

- Fix VFIO regression on NXP SoCs by reporting IOMMU_CAP_CACHE_COHERENCY

- Fix SMMU shutdown paths to avoid device unregistration race

----------------------------------------------------------------
Robin Murphy (1):
      iommu/arm-smmu: Report IOMMU_CAP_CACHE_COHERENCY even betterer

Vladimir Oltean (2):
      iommu/arm-smmu: Don't unregister on shutdown
      iommu/arm-smmu-v3: Don't unregister on shutdown

 drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c |  4 +++-
 drivers/iommu/arm/arm-smmu/arm-smmu.c       | 32 ++++++++++++++++++++---------
 2 files changed, 25 insertions(+), 11 deletions(-)