[alsa-devel] [PATCH] OMAP general SOC driver.

David Brownell david-b at pacbell.net
Wed Nov 26 19:34:41 CET 2008

On Wednesday 26 November 2008, Jarkko Nikula wrote:
> And as a first step, I recommend to start merging only those EVM & SDP
> boards with Beagle since they seems to be most close to each other.
> Even the Overo seems to be close also, it was discussed earlier to keep
> it separated now since Steve was going to send some new features into
> it.

This seems to focus on just the McBSP channel out of the OMAP ...
except that it hides (in that nasty #ifdeffery) the codec data.

The fact that it doesn't allow EAC or a McBSP successor says
to me it's not really "general".  Heck ... it even hard-wires
McBSP2, preventing another channel from being used.  So IMO
a different name would be appropriate...

Re TWL4030 codec configuration ... I count three microphone
input channels not used on Beagle, plus a speaker output
and some other stuff.  So it's obvious that something which
works on Beagle won't handle more interesting configurations
of that audio support.  

Plus, if there's going to be a board-specific platform device
created, and stuffed with data like codec descriptions and
configuration data ... that's what arch/arm/mach-*/board-*.c
files are for.

I'm told that the ASoC stuff "should" go in a separate ASoC
area for some reason.  That still makes no good sense to me,
so if there's a brief explanation as to why it's done that
way, please fling me a URL.  :)

- Dave

More information about the Alsa-devel mailing list