提交 caa62d64 编写于 作者: U Ulf Hansson 提交者: Samuel Ortiz

mfd: ab8500: sysctrl: Initialize driver at arch_initcall

The abx500-clk driver is initiated at arch_initcall level. Moreover it
is relying on the ab8500-sysctrl API to be available. Therefore move
ab8500-sysctrl to arch_initcall level as well. The device is already
added before the abx500 clk device, thus it will be probed before as
well, which is exactly what we want.
Signed-off-by: NUlf Hansson <ulf.hansson@linaro.org>
Signed-off-by: NSamuel Ortiz <sameo@linux.intel.com>
上级 741cdecf
...@@ -242,7 +242,7 @@ static int __init ab8500_sysctrl_init(void) ...@@ -242,7 +242,7 @@ static int __init ab8500_sysctrl_init(void)
{ {
return platform_driver_register(&ab8500_sysctrl_driver); return platform_driver_register(&ab8500_sysctrl_driver);
} }
subsys_initcall(ab8500_sysctrl_init); arch_initcall(ab8500_sysctrl_init);
MODULE_AUTHOR("Mattias Nilsson <mattias.i.nilsson@stericsson.com"); MODULE_AUTHOR("Mattias Nilsson <mattias.i.nilsson@stericsson.com");
MODULE_DESCRIPTION("AB8500 system control driver"); MODULE_DESCRIPTION("AB8500 system control driver");
......
Markdown is supported
0% .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑!
想要评论请 注册