aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMika Westerberg <mika.westerberg@linux.intel.com>2018-09-24 13:20:45 +0300
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2018-10-02 10:51:16 -0700
commiteafa717bc145963c944bb0a64d16add683861b35 (patch)
tree171eb90974675c96882f8c2c8eca93339a01157f
parentthunderbolt: Do not handle ICM events after domain is stopped (diff)
downloadlinux-dev-eafa717bc145963c944bb0a64d16add683861b35.tar.xz
linux-dev-eafa717bc145963c944bb0a64d16add683861b35.zip
thunderbolt: Initialize after IOMMUs
If IOMMU is enabled and Thunderbolt driver is built into the kernel image, it will be probed before IOMMUs are attached to the PCI bus. Because of this DMA mappings the driver does will not go through IOMMU and start failing right after IOMMUs are enabled. For this reason move the Thunderbolt driver initialization happen at rootfs level. Signed-off-by: Mika Westerberg <mika.westerberg@linux.intel.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
-rw-r--r--drivers/thunderbolt/nhi.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/thunderbolt/nhi.c b/drivers/thunderbolt/nhi.c
index 88cff05a1808..5cd6bdfa068f 100644
--- a/drivers/thunderbolt/nhi.c
+++ b/drivers/thunderbolt/nhi.c
@@ -1191,5 +1191,5 @@ static void __exit nhi_unload(void)
tb_domain_exit();
}
-fs_initcall(nhi_init);
+rootfs_initcall(nhi_init);
module_exit(nhi_unload);