Quoting Mark Brown (2016-02-16 05:42:33) > On Tue, Feb 16, 2016 at 11:46:52AM +0200, Peter Ujfalusi wrote: > > > As for codecs, tlv320aic3106 is also pretty simple device from the outside, it > > can receive it's reference clock via: > > MCLK pin, GPIO2 pin or it can use the BCLK from the bus. Based on the incoming > > frequency it can use it directly or it needs to use the internal PLL to > > generate the cocks. > > It can output generated clock via GPIO1 > > That already sounds like there is room for configuration and hooking > into a wider clock tree - we've got three different source options and > an output plus a PLL that can presumably take in non-audio rates. It makes sense to use an already existing clock framework, but I'm wondering, how do we model the clock select function? Using a clock mux? Somewhere, somehow, something needs to look at the setup and decide which pin on the codec should be the clock source (e.g. MCLK, GPIO2, or BCLK in the case of the tlv320aic3106). /Ricard -- Ricard Wolf Wanderlöf ricardw(at)axis.com Axis Communications AB, Lund, Sweden www.axis.com Phone +46 46 272 2016 Fax +46 46 13 61 30 _______________________________________________ Alsa-devel mailing list Alsa-devel@xxxxxxxxxxxxxxxx http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
