On Thursday, May 31, 2018 07:02 PM, Rob Herring wrote:
On Tue, May 29, 2018 at 10:23:48PM +0200, Daniel Mack wrote:
If that's the case, could you depict how the DT bindings should look like by
example?
In clock providers, you just add #clock-cells. Then the consumer side
defines 'clocks'. Which clock(s) comes from the dai is defined by the
index in the 'clocks' property for that node.
Both ends can be providers, but who is active is determined by defining
the actual connections with 'clocks'. Or perhaps you have both
directions shown and there is some other means to select which one is
active such as solving for who can provide the desired freq.
How about entities that are a clock producer and consume their clocks
themselves? That's a rather typical thing for DAIs. Is that expressible
in DT?
Thanks,
Daniel
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
