[alsa-devel] [topic/asoc][DON'T PUSH][PATCH 0/3] ASoC: OMAP: McBSP DAI driver updates

[Jarkko Nikula]

On Thu, Oct 9, 2008 at 6:10 PM, Mark Brown <broonie at sirena.org.uk> wrote:

> On Thu, Oct 09, 2008 at 04:02:29PM +0100, Mark Brown wrote:
>
> > These all look good.  How do you want to merge them?  They could either
> > go in with the McBSP changes they depend on or via ALSA.  If via ALSA
> > then if you like I'm happy to queue them up and submit them once their
> > dependencies are merged (I've got some other changes in a similar
> > situation myself).  Otherwise I guess you could resubmit them once the
> > McBSP changes are merged.
>
> Hrm.  Looking at the ARM list just now it seems both this and the things
> my other patches are waiting for are now in rmk's tree so I'm already
> tracking stuff in the same tree for submission - I guess that makes
> adding these to my queue the most simple approach?
>

Commenting from my another address. Yeah, I just saw Russell's mail that he
pulled in those McBSP patches so should be safe enough to track these
patches via your queue.

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.

---

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
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@vger.kernel.org/msg04389.html


Jarkko