On 04/18, Mark Brown wrote: > On Mon, Apr 18, 2016 at 06:50:52PM +0300, Peter Ujfalusi wrote: > > On 02/17/2016 09:52 PM, Peter Ujfalusi wrote: > > > > On the other hand this ABI is backwards compatible since if it is missing it > > > will default to the configuration we right now have regarding to sysclk_dir > > > and sysclk_id. > > > > I will look at the CCF implementation for McASP first then for aic3x. > > > The first issue with converting the McASP to use CCF internally for clock > > selection, muxing and rate configuration is that the daVinci platform does not > > use CCF at all. Given that the davinci-mcasp driver is used by daVinci, we > > need to have non CCF way supported in ASoC... > > Well, at least long term we do need daVinci converting to CCF - this is > going to continue to cause problems, devices not part of the SoC can and > do contain clocks and are going to end up being supported via the clock > API. Does anyone here know what's involved in converting daVinci to CCF? It doesn't look too far off from what is in the CCF today, so I'm not sure what's blocking the transition. -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project _______________________________________________ Alsa-devel mailing list Alsa-devel@xxxxxxxxxxxxxxxx http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
