Re: Reg: Implementation of GSM digital audio path

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Mark,

      Thanks for response.

      On my hardware, GSM is connected to McBSP3 not to the TWL4030 CODEC
directly. What  I have to do is Copy from McBSP3 and redirect this to

      McBSP2.


                        USB GSM chip -> McBSP3

                                                    McBSP2 -> TWL4030

        I have understood some thing from ur mail. I will study Openmoko
ASoC and I will get back to you.

        Suggest me wat else I can do?

Regards,
Shariff

On Thu, Jun 25, 2009 at 4:11 PM, Mark Brown <
broonie@xxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

> On Thu, Jun 25, 2009 at 03:17:54PM +0530, shariff wrote:
>
> >         Iam working on OMAP3 based custom board. On our board, GSM
> digital
> > audio path is connected to McBSP3 and
> > TWL4030 digital audio path is connected to McBSP2.
>
> In this scenario your GSM modem is essentially functioning as a CODEC
> within ASoC.  The simplest thing to do is set up a dummy DAI in your
> machine driver for the GSM modem, register that at startup and then set
> up a dai_link for that as normal.  You can then address the two streams
> individually as devices on the card.
>
> The OpenMoko is doing something similar with its bluetooth chipset,
> though that is connected to a second DAI on the CODEC rather than the
> CPU.
>
_______________________________________________
Alsa-devel mailing list
Alsa-devel@xxxxxxxxxxxxxxxx
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

[Index of Archives]     [ALSA User]     [Linux Audio Users]     [Kernel Archive]     [Asterisk PBX]     [Photo Sharing]     [Linux Sound]     [Video 4 Linux]     [Gimp]     [Yosemite News]

  Powered by Linux