[PATCH 1/4] clk: mvebu: armada-370: maintain clock init order

2014-01-25 Thread Sebastian Hesselbarth
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.

[PATCH 1/4] clk: mvebu: armada-370: maintain clock init order

2014-01-25 Thread Sebastian Hesselbarth
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.