Re: [PATCH] Alsa modularisations and support for tsc2101 0/7

["Daniel Petrini" <d.pensator@gmail.com>]

Hi Nishanth,

On 2/21/06, Menon, Nishanth <x0nishan@ti.com> wrote:
>
>
> Hi Daniel,
> Glad to see a clean organization coming in for the code :).
> >2) If it is acceptable to put the codecs under arch directory, would
> >plat-omap be better location than arch-omap1, for mcbsp supported
> >codecs? (Are there any omap2 boards with aic23 or tsc2101 codecs?)
> Yes, There are omap2 boards with tsc2101, and omap2 boards which can have
> pluggable codecs.

Yes, we can put that files in plat-omap instead.

>some interesting observations I have seen so far (it will
> be a small set compared to what others could add):

Good separation of functionalities it is more or less what we are
thinking about.

> Control paths:
> McSPI, uWire, I2C

This control path are mainly used by the codec file

> Data transfer paths:
> codecs with mcbsp/EAC on 2420
> codecs with mcbsp/mcbsplp(on2430)
> codecs on mcbsp1,2

Yes, they act as "bridges" between the main processor and the codec.
Maybe a future version of the modularisation will be responsible to
remove the dependence of mcbsp.

> Data formats:
> PCM,I2S,TDM
> could have supported uLaw data formats too
> Codecs:
> tsc2101, aic, others such as
> twl4030(http://focus.ti.com/general/docs/wtbu/wtbugencontent.tsp?templateId=6123&path=templatedata/cm/general/data/wtbmiddl/twl4030&DCMP=WTBU&HQS=ProductBulletin+OT+twl4030)codecs
> which are far more complex than these two, including data mixing,
> mono/stereo input/output capabilities.

Yes, isolating they from alsa is the first step.

> Regards,
> Nishanth Menon

Regards,
Daniel
--
INdT - Manaus - Brazil