summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorFederico Fuga <fuga@studiofuga.com>2012-07-30 12:50:26 +0800
committerAndy Green <andy.green@linaro.org>2012-07-30 12:50:26 +0800
commitd7e3487966e5194098a2782989dbe55691507ed8 (patch)
treecc9f830ee3070888a729f54a6e378ff09b262b7d
parente2c2b8b7fe7f3bfae499de131898826aa51403c3 (diff)
rpmsg: fix dependency on initialization order
When rpmsg drivers are built into the kernel, they must not initialize before the rpmsg bus does, otherwise they'd trigger a BUG() in drivers/base/driver.c line 169 (driver_register()). To fix that, and to stop depending on arbitrary linkage ordering of those built-in rpmsg drivers, we make the rpmsg bus initialize at subsys_initcall. Cc: stable <stable@vger.kernel.org> Signed-off-by: Federico Fuga <fuga@studiofuga.com> [ohad: rewrite the commit log] Signed-off-by: Ohad Ben-Cohen <ohad@wizery.com>
-rw-r--r--drivers/rpmsg/virtio_rpmsg_bus.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/rpmsg/virtio_rpmsg_bus.c b/drivers/rpmsg/virtio_rpmsg_bus.c
index fea1c6b7d6d..35a63d38581 100644
--- a/drivers/rpmsg/virtio_rpmsg_bus.c
+++ b/drivers/rpmsg/virtio_rpmsg_bus.c
@@ -1123,7 +1123,7 @@ static int __init rpmsg_init(void)
return ret;
}
-module_init(rpmsg_init);
+subsys_initcall(rpmsg_init);
static void __exit rpmsg_fini(void)
{