Re: [PATCH 3/7] clk: mvebu: cp110: do not depend anymore of the *-clock-output-names

2017-05-23 Thread Rob Herring
On Fri, May 19, 2017 at 05:55:21PM +0200, Gregory CLEMENT wrote: > Using the *-clock-output-names property was a convenient way to have a > unique name for each clock even when there are multiple cp110 blocks > as we can find on Armada 8K. > > However it has some drawbacks: the main one being a

Re: [PATCH 3/7] clk: mvebu: cp110: do not depend anymore of the *-clock-output-names

2017-05-23 Thread Rob Herring
On Fri, May 19, 2017 at 05:55:21PM +0200, Gregory CLEMENT wrote: > Using the *-clock-output-names property was a convenient way to have a > unique name for each clock even when there are multiple cp110 blocks > as we can find on Armada 8K. > > However it has some drawbacks: the main one being a

[PATCH 3/7] clk: mvebu: cp110: do not depend anymore of the *-clock-output-names

2017-05-19 Thread Gregory CLEMENT
Using the *-clock-output-names property was a convenient way to have a unique name for each clock even when there are multiple cp110 blocks as we can find on Armada 8K. However it has some drawbacks: the main one being a stronger link than necessary between the driver and the device tree. For

[PATCH 3/7] clk: mvebu: cp110: do not depend anymore of the *-clock-output-names

2017-05-19 Thread Gregory CLEMENT
Using the *-clock-output-names property was a convenient way to have a unique name for each clock even when there are multiple cp110 blocks as we can find on Armada 8K. However it has some drawbacks: the main one being a stronger link than necessary between the driver and the device tree. For