diff options
author | Shawn Guo <shawn.guo@linaro.org> | 2016-09-23 01:45:08 (GMT) |
---|---|---|
committer | Stephen Boyd <sboyd@codeaurora.org> | 2016-09-23 21:42:13 (GMT) |
commit | c72f2883c31e8c21832f3d48d5aa6ee8d83b3c43 (patch) | |
tree | 94d1812825022be0f4f08ec4a27f847f746f1428 /drivers/oprofile | |
parent | a0245eb76ad0f652f1eb14f48ca2d3c4391aef66 (diff) | |
download | linux-c72f2883c31e8c21832f3d48d5aa6ee8d83b3c43.tar.xz |
clk: zx296718: register driver earlier with core_initcall
Clock driver should be registered with an earlier initcall than
module_init which is used by most of client device drivers. Otherwise,
probing of these client drivers will likely be deferred due to that
calls into clk API will return -EPROBE_DEFER.
Deferred probing is not a problem for most subsystems, but could bring
some side effect for particular subsystem, like display. On ZX296718
platform, we get Linux logo and boot log lost from display device, just
because the DRM/KMS driver gets -EPROBE_DEFER from devm_clk_get() call.
Let's use core_initcall (qcom and a few other clk drivers use that) for
driver registration to avoid those unnecessary -EPROBE_DEFER and get rid
of the side effect with ZX296718 display system.
Signed-off-by: Shawn Guo <shawn.guo@linaro.org>
Signed-off-by: Stephen Boyd <sboyd@codeaurora.org>
Diffstat (limited to 'drivers/oprofile')
0 files changed, 0 insertions, 0 deletions