linux-toradex.git/drivers/clk/mvebu, branch v3.14.20

clk: mvebu: kirkwood: maintain clock init order

2014-02-06T18:07:01+00:00

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 
Tested-by: Ezequiel Garcia 
Signed-off-by: Jason Cooper

clk: mvebu: dove: maintain clock init order

2014-02-06T18:06:52+00:00

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 
Tested-by: Ezequiel Garcia 
Signed-off-by: Jason Cooper

clk: mvebu: armada-xp: maintain clock init order

2014-02-06T18:06:50+00:00

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 
Signed-off-by: Jason Cooper

clk: mvebu: armada-370: maintain clock init order

2014-02-06T18:06:28+00:00

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 
Tested-by: Ezequiel Garcia 
Signed-off-by: Jason Cooper

clk: mvebu: Add Core Divider clock

2013-11-24T17:29:25+00:00

This commit introduces a new group of clocks present in Armada 370/XP
SoCs (called "Core Divider" clocks) and add a provider for them.
The only clock supported for now is the NAND clock (ndclk), but the
infrastructure to add the rest is already set.

Reviewed-by: Gregory CLEMENT 
Signed-off-by: Ezequiel Garcia 
Signed-off-by: Mike Turquette

clk: mvebu: staticize of_cpu_clk_setup

2013-11-24T03:21:36+00:00

This symbol is used only in this file. The patch fix the following
sparse warning:
warning: symbol 'of_cpu_clk_setup' was not declared. Should it be static?

Signed-off-by: Jisheng Zhang 
Acked-by: Jason Cooper 
Acked-by: Gregory CLEMENT 
Signed-off-by: Jason Cooper

clk: armada-370: fix tclk frequencies

2013-10-07T00:39:46+00:00

This patch fixes the tclk frequency array for the Armada-370 SoC.
This bug has been introduced by commit 6b72333d
("clk: mvebu: add Armada 370 SoC-centric clock init").

A wrong tclk frequency affects the following drivers: mvsdio, mvneta,
i2c-mv64xxx and mvebu-devbus. This list may be incomplete.

About the mvneta Ethernet driver, note that the tclk frequency is used
to compute the Rx time coalescence. Then, this bug harms the coalescence
configuration and also degrades the networking performances with the
default values.

Signed-off-by: Simon Guinot 
Cc: Andrew Lunn 
Cc: Gregory CLEMENT 
Cc: Sebastian Hesselbarth 
Acked-by: Jason Cooper 
Cc: stable@vger.kernel.org
Signed-off-by: Michael Turquette

clk: kirkwood: Fix incorrect placement of __initconst

2013-08-28T01:35:19+00:00

__initconst should be placed between the variable name and equal
sign for the variable to be placed in the intended section.

Signed-off-by: Sachin Kamat 
Acked-by: Gregory Clement 
Signed-off-by: Mike Turquette

clk: dove: Fix incorrect placement of __initconst

2013-08-28T01:35:07+00:00

__initconst should be placed between the variable name and equal
sign for the variable to be placed in the intended section.

Signed-off-by: Sachin Kamat 
Acked-by: Gregory Clement 
Signed-off-by: Mike Turquette

clk: armada-xp: Fix incorrect placement of __initconst

2013-08-28T01:34:40+00:00

__initconst should be placed between the variable name and equal
sign for the variable to be placed in the intended section.

Signed-off-by: Sachin Kamat 
Acked-by: Gregory Clement 
Signed-off-by: Mike Turquette