clk: mvebu: armada-370: maintain clock init order
authorSebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
Sat, 25 Jan 2014 18:19:07 +0000 (19:19 +0100)
committerJason Cooper <jason@lakedaemon.net>
Thu, 6 Feb 2014 18:06:28 +0000 (18:06 +0000)
commit07ad6836fa21b8ae1715d5f82a0d28c4140e1e73
treebeb052774029d2e7222b4b5835d2ddd9cb9cc930
parent38dbfb59d1175ef458d006556061adeaa8751b72
clk: mvebu: armada-370: maintain clock init order

Init order of CLK_OF_DECLARE'd drivers depends on compile order.
Unfortunately, clk_of_init does not allow drivers to return errors,
e.g. -EPROBE_DEFER if parent clocks have not been registered, yet.

To avoid init order woes for MVEBU clock drivers, we take care of
proper init order ourselves. This patch joins core-clk and gating-clk
init to maintain proper init order.

Signed-off-by: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
Tested-by: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
Signed-off-by: Jason Cooper <jason@lakedaemon.net>
drivers/clk/mvebu/armada-370.c