On Tue, May 29, 2018 at 10:23:48PM +0200, Daniel Mack wrote: > On Tuesday, May 29, 2018 01:24 PM, Mark Brown wrote: > > If we want to get more complex usage of clocks in the DT we should be > > moving the CODECs over to using the standard clock bindings for this > > stuff rather than inventing custom ASoC clock bindings for it. That way > > we don't have to deal with the pain of trying to join things up in the > > future. > This will get rather complex too though, because most codec and cpu dais can > act as clock source xor clock consumer, depending on how the hardware is > built. Would you want to represent everything, bit clocks, frame clocks, > master clocks etc as clock nodes? We're probably OK just going down to the master clocks mostly I think. For the clocks on the actual bus we can probably have helpers in the core that generate the clocks and the drivers just tell the core the rates. > If that's the case, could you depict how the DT bindings should look like by > example? I've not been able to dig far enough into the clock bindings yet. That's not super helpful for you I appreciate, TBH nobody seemed to particularly need this so it wasn't super urgent - most of the things using alternative clocks on devices seem to also need custom machine drivers for other reasons.
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ Alsa-devel mailing list Alsa-devel@xxxxxxxxxxxxxxxx http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
