From: Jean-Philippe Brucker <jean-philippe@linaro.org>
To: Robin Murphy <robin.murphy@arm.com>
Cc: Will Deacon <will@kernel.org>, Joerg Roedel <joro@8bytes.org>,
linux-acpi@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, iommu@lists.linux.dev,
devicetree@vger.kernel.org, Rob Herring <robh@kernel.org>,
Saravana Kannan <saravanak@google.com>,
Lorenzo Pieralisi <lpieralisi@kernel.org>,
Hanjun Guo <guohanjun@huawei.com>,
Sudeep Holla <sudeep.holla@arm.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Len Brown <lenb@kernel.org>
Subject: Re: [PATCH 0/4] iommu: Remove iommu_fwspec ops
Date: Tue, 23 Apr 2024 15:08:03 +0100 [thread overview]
Message-ID: <20240423140803.GA931103@myrica> (raw)
In-Reply-To: <cover.1713523251.git.robin.murphy@arm.com>
On Fri, Apr 19, 2024 at 05:55:58PM +0100, Robin Murphy wrote:
> Hi All,
>
> Building on top of the arch_setup_dma_ops() cleanup[1], the next step
> down the chain is {acpi,of}_dma_configure()... There's plenty to do
> here, but it may as well start with this fairly self-contained little
> cleanup, pruning yet more redundancy and exposed API surface.
Tested with QEMU: SMMUv3 DT/IORT, virtio-iommu builtin/module DT/VIOT arm64/x86
Tested-by: Jean-Philippe Brucker <jean-philippe@linaro.org>
>
> Thanks,
> Robin.
>
> [1] https://lore.kernel.org/linux-iommu/cover.1713523152.git.robin.murphy@arm.com
>
>
> Robin Murphy (4):
> iommu: Resolve fwspec ops automatically
> ACPI: Retire acpi_iommu_fwspec_ops()
> OF: Simplify of_iommu_configure()
> iommu: Remove iommu_fwspec ops
>
> drivers/acpi/arm64/iort.c | 19 +++-------
> drivers/acpi/scan.c | 38 +++++---------------
> drivers/acpi/viot.c | 11 ++----
> drivers/iommu/arm/arm-smmu/arm-smmu.c | 3 +-
> drivers/iommu/iommu-priv.h | 7 ++++
> drivers/iommu/iommu.c | 20 +++++------
> drivers/iommu/mtk_iommu_v1.c | 2 +-
> drivers/iommu/of_iommu.c | 50 ++++++++++-----------------
> drivers/iommu/tegra-smmu.c | 2 +-
> drivers/of/device.c | 30 ++++++----------
> include/acpi/acpi_bus.h | 3 +-
> include/linux/iommu.h | 15 ++------
> 12 files changed, 66 insertions(+), 134 deletions(-)
>
> --
> 2.39.2.101.g768bb238c484.dirty
>
prev parent reply other threads:[~2024-04-23 14:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-19 16:55 [PATCH 0/4] iommu: Remove iommu_fwspec ops Robin Murphy
2024-04-19 16:55 ` [PATCH 1/4] iommu: Resolve fwspec ops automatically Robin Murphy
2024-04-22 5:00 ` Andy Shevchenko
2024-04-19 16:56 ` [PATCH 2/4] ACPI: Retire acpi_iommu_fwspec_ops() Robin Murphy
2024-04-22 16:18 ` Rafael J. Wysocki
2024-04-19 16:56 ` [PATCH 3/4] OF: Simplify of_iommu_configure() Robin Murphy
2024-04-19 22:00 ` Rob Herring
2024-04-19 16:56 ` [PATCH 4/4] iommu: Remove iommu_fwspec ops Robin Murphy
2024-04-23 14:08 ` Jean-Philippe Brucker [this message]
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=20240423140803.GA931103@myrica \
--to=jean-philippe@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=guohanjun@huawei.com \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=rafael@kernel.org \
--cc=robh@kernel.org \
--cc=robin.murphy@arm.com \
--cc=saravanak@google.com \
--cc=sudeep.holla@arm.com \
--cc=will@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