On Tue, 5 Apr 2022 15:32:50 +0100, Robin Murphy wrote:
> Defer the IOMMU domain setup until after successfully binding
> components, so we can figure out IOMMU support directly from the VOP
> devices themselves, rather than manually inferring it from the DT (which
> also fails to account for whether the IOMMU driver is actually loaded).
> Although this is somewhat of a logical cleanup, the main motivation is
> to prepare for a change in the iommu_domain_alloc() interface.
Applied, thanks!
[1/1] drm/rockchip: Refactor IOMMU initialisation
commit: 421be3ee36a497949a4b564cd1e4f7f9fe755f57
Additionally tested on rk3288, rk3399 and px30.
Best regards,
--
Heiko Stuebner <he...@sntech.de>
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
