From: Robin Murphy <robin.murphy@arm.com>
To: Alexey Kardashevskiy <aik@ozlabs.ru>, joro@8bytes.org, will@kernel.org
Cc: jean-philippe@linaro.org, zhang.lyra@gmail.com,
linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org,
thierry.reding@gmail.com, gerald.schaefer@linux.ibm.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 09/14] iommu/ipmmu-vmsa: Clean up bus_set_iommu()
Date: Wed, 6 Jul 2022 11:54:27 +0100 [thread overview]
Message-ID: <8915e679-71b2-eef4-88d5-127bcc6cf990@arm.com> (raw)
In-Reply-To: <aef1d470-e8a0-4ba8-2a55-adf05b836684@ozlabs.ru>
On 2022-07-06 09:38, Alexey Kardashevskiy wrote:
>
>
> On 28/04/2022 23:18, Robin Murphy wrote:
>> Stop calling bus_set_iommu() since it's now unnecessary. This also
>> leaves the custom initcall effectively doing nothing but register
>> the driver, which no longer needs to happen early either, so convert
>> it to builtin_platform_driver().
>>
>> Signed-off-by: Robin Murphy <robin.murphy@arm.com>
>> ---
>> drivers/iommu/ipmmu-vmsa.c | 35 +----------------------------------
>> 1 file changed, 1 insertion(+), 34 deletions(-)
>>
>> diff --git a/drivers/iommu/ipmmu-vmsa.c b/drivers/iommu/ipmmu-vmsa.c
>> index 8fdb84b3642b..2549d32f0ddd 100644
>> --- a/drivers/iommu/ipmmu-vmsa.c
>> +++ b/drivers/iommu/ipmmu-vmsa.c
>> @@ -1090,11 +1090,6 @@ static int ipmmu_probe(struct platform_device
>> *pdev)
>> ret = iommu_device_register(&mmu->iommu, &ipmmu_ops,
>> &pdev->dev);
>> if (ret)
>> return ret;
>> -
>> -#if defined(CONFIG_IOMMU_DMA)
>> - if (!iommu_present(&platform_bus_type))
>> - bus_set_iommu(&platform_bus_type, &ipmmu_ops);
>> -#endif
>> }
>> /*
>
> The comment which starts here did not make it to the patch but it should
> have as it mentions bus_set_iommu() which is gone by the end of the series.
Heh, busted! In fact I think the whole point of that comment stops being
true, but I couldn't be bothered to reason about it since one of the
next steps after this is to start ripping all the arm_iommu_* stuff out
anyway.
> More general question/request - could you please include the exact sha1
> the patchset is based on? It did not apply to any current trees and
> while it was trivial, it was slightly annoying to resolve the conflicts
> :) Thanks,
v3 is based directly on 5.19-rc3:
https://lore.kernel.org/lkml/cover.1657034827.git.robin.murphy@arm.com/
And if it helps I have it on a branch here as well:
https://gitlab.arm.com/linux-arm/linux-rm/-/tree/bus-set-iommu-v3
Robin.
next prev parent reply other threads:[~2022-07-06 10:54 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-28 13:18 [PATCH v2 00/14] iommu: Retire bus_set_iommu() Robin Murphy
2022-04-28 13:18 ` [PATCH v2 01/14] iommu/vt-d: Temporarily reject probing non-PCI devices Robin Murphy
2022-04-28 13:18 ` [PATCH v2 02/14] iommu: Always register bus notifiers Robin Murphy
2022-04-28 13:18 ` [PATCH v2 03/14] iommu: Move bus setup to IOMMU device registration Robin Murphy
2022-04-29 6:57 ` Baolu Lu
2022-04-29 8:50 ` Robin Murphy
2022-04-29 18:06 ` Robin Murphy
2022-07-05 4:51 ` Baolu Lu
2022-07-05 9:06 ` Robin Murphy
2022-04-28 13:18 ` [PATCH v2 04/14] iommu/amd: Clean up bus_set_iommu() Robin Murphy
2022-04-28 13:18 ` [PATCH v2 05/14] iommu/arm-smmu: " Robin Murphy
2022-04-28 13:18 ` [PATCH v2 06/14] iommu/arm-smmu-v3: " Robin Murphy
2022-04-28 13:18 ` [PATCH v2 07/14] iommu/dart: " Robin Murphy
2022-04-28 13:18 ` [PATCH v2 08/14] iommu/exynos: " Robin Murphy
2022-04-28 13:18 ` [PATCH v2 09/14] iommu/ipmmu-vmsa: " Robin Murphy
2022-07-06 8:38 ` Alexey Kardashevskiy
2022-07-06 10:54 ` Robin Murphy [this message]
2022-04-28 13:18 ` [PATCH v2 10/14] iommu/mtk: " Robin Murphy
2022-04-28 13:18 ` [PATCH v2 11/14] iommu/omap: " Robin Murphy
2022-04-28 13:18 ` [PATCH v2 12/14] iommu/tegra-smmu: " Robin Murphy
2022-04-28 13:18 ` [PATCH v2 13/14] iommu/virtio: " Robin Murphy
2022-04-28 13:18 ` [PATCH v2 14/14] iommu: " Robin Murphy
2022-04-28 14:16 ` [PATCH v2 00/14] iommu: Retire bus_set_iommu() Robin Murphy
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=8915e679-71b2-eef4-88d5-127bcc6cf990@arm.com \
--to=robin.murphy@arm.com \
--cc=aik@ozlabs.ru \
--cc=gerald.schaefer@linux.ibm.com \
--cc=iommu@lists.linux-foundation.org \
--cc=jean-philippe@linaro.org \
--cc=joro@8bytes.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=thierry.reding@gmail.com \
--cc=will@kernel.org \
--cc=zhang.lyra@gmail.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