> >> The DaVinci ASoC code is indeed in mainline, but not all of the > >> DaVinci core (in this case the pin mux) is yet in mainline. I will be > >> pushing it during the next merge window. > > > > That doesn't really answer my question. > > > > I can see that David Brownell pushed a patch to the davinci tree > > directly modifying sound/soc/davinci/davinci-evm.c which IS in > > mainline. Does this means that as of now all ASoC patches should be sent > first to > > the Davinci list, and then you will push those to the mainline kernel? > > > > No ASoc patches should be generated against an ASoC tree and submitted > to alsa-devel, and CC davinci list. > > This means that the until the DaVinci core is in mainline, DaVinci git > will have > slightly different looking ASoC drivers, but those changes will be > minimal. > > Kevin > Kevin,
We are planning to submit the patches for dm646x ASoC driver which has McASP. But as dm646x support is not available in mainline, the driver will not build. We can break down the patches to EVM specific and non-EVM specific parts, but no one will be able to test the dm646x ASoC driver in mainline. How should we go about this? Regards, Sudhakar _______________________________________________ Davinci-linux-open-source mailing list [email protected] http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
