On Thu, Oct 09, 2008 at 08:17:08PM +0300, Jarkko Nikula wrote: > Actually devconf register definitions for 2430 and 34xx, what patch 1 is > using, are already in mainline and new McBSP DMA port and base address > definitions are covered by CONFIG_ARCH_OMAPxxxx so ASoC for osk5912 should > still compile. So they should be safe to push already, then? > I heard yesterday from Tony Lindgren that TWL4030 changes might be also > coming into mainline now. Then Steve would be able send his TWL4030 codec > driver and machine driver for Overo. Machine driver for Beagle exists as Yes, Samuel Ortiz said he'd merged David's patch for the core so the codec driver should be good to go once Linus pulls the MFD tree. Chances are that this will also be about the same time as the other stuff I'm queuing if you want to go that way? > well and question is should the same machine driver cover both boards since > now they are very similar? Current understanding is to keep them separated > since Overo will be extended in the future. Some discussion about it: > http://www.mail-archive.com/linux-omap@xxxxxxxxxxxxxxx/msg04389.html Given that Overo will be extended beyond what the Beagle board is capable of it probably does make sense to separate the two drivers - using the same one initially might confuse whoever comes along and does the more detailed Overo board support. The main argument for doing them within the one driver would be if the Beagle and Overo boards were generally understood by OMAP users as being subfitted versions of the same family. Really, whatever makes life easiest for you guys is fine. _______________________________________________ Alsa-devel mailing list Alsa-devel@xxxxxxxxxxxxxxxx http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
