Re: [PATCH RFC v3 2/2] clk: Add handling of clk parent and rate assigned from DT

From: Laurent Pinchart
Date: Fri Mar 28 2014 - 12:42:32 EST

Hi Sascha,

On Thursday 27 March 2014 15:47:12 Sascha Hauer wrote:
> On Thu, Mar 27, 2014 at 03:08:10PM +0100, Laurent Pinchart wrote:


> > That's clearer indeed. Can the parents and rates depend on the board, or
> > on the SoC only ? We might be getting dangerously close to specifying
> > platform configuration instead of describing the hardware. A real example
> > might be nice to support the discussion.
> This patch comes just at the right time. This is what I do with it:
> #define cko1_sel 57
> #define pll4_audio_div 203
> #define pll4_audio 173
> #define ssi3_sel 47
> &clks {
> assigned-clocks {
> clocks = <&clks cko1_sel>, <&clks ssi3_sel>, <&clks pll4_audio>;
> clock-parents = <&clks pll4_audio_div>, <&clks pll4_audio_div>, <0>;
> clock-rates = <0>, <0>, <786432000>;
> };
> };
> cko1_sel is a clock that can be routed out of the SoC. In my case it is
> connected the sysclk of an external Audio Codec. ssi3_sel drives my SoC
> internal I2S unit which I use in master mode. The above makes sure that
> the I2S unit and the the external codec both get their clock from the
> audio PLL. The audio PLL is configured to a rate of 786432000Hz which
> is an exact multiple of the desired audio clock.

Thank you for the example.

Are the cko1_sel and ssi3_sel used only by the external audio codec and
internal I2S unit respectively ? If so, it might make sense to move the
configuration of their parent to the audio codec and I2S unit DT nodes.
However, grouping the parent configuration and the pll4 rate configuration in
a single place makes sense as well. Guidelines are probably needed.

I get a slight feeling of uneasiness about this, probably because we're at the
boundary between hardware description and system configuration. Encoding in DT
that "for this particular board this particular clock must be configured this
particular way" sounds fine to me, but we need to make sure it won't turn to
software-driven rather than hardware-driven use case descriptions.


Laurent Pinchart

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at