[alsa-devel] Reg: Implementation of GSM digital audio path
shariffsinbox at gmail.com
Thu Jun 25 13:27:46 CEST 2009
Thanks for quick response. I understood some what from your mail.
I will explain, how my hardware is connected.
USB GSM chip -> McBSP3
McBSP2 -> TWL4030
Here, playback functionality will not be there in the GSM path. I need
to take audio data from GSM. and redirect this
to TWL4030 codec.
The thing is, How and where to implement this GSM path without
playback? as I am new to this ASoC framework.
What I understood from ur mail is. Audio is being redirected from the
application space i.e arecord will record and store in buffer and this
being played using aplay to other hardware (twl4030).
Can we handle the same thing in kernel space ( i.e in driver itself).
On Thu, Jun 25, 2009 at 4:05 PM, Peter Ujfalusi <peter.ujfalusi at nokia.com>wrote:
> On Thursday 25 June 2009 12:47:54 ext shariff wrote:
> > Hi all,
> > Iam working on OMAP3 based custom board. On our board, GSM
> > audio path is connected to McBSP3 and
> > TWL4030 digital audio path is connected to McBSP2.
> > I want to implement a module that transfers GSM audio data and store
> > data into some buffer and redirect it to TWL4030 audio codec through
> > McBSP2.
> > I question is how can I implement this in ASoC?
> > I studied ASoC framework, but I am unable to understand where to
> > my stuff.
> I think the following should do something like that:
> arecord -Dplughw:0.0 | aplay -Dplughw:0.1
> arecord -Dhw:0.0 | aplay -Dhw:0.1
> I don't know what is the order of the PCMs with the twl4030 codec on your
> board, this is with the assumption:
> plughw:0.0 - Voice PCM (McBSP3)
> plughw:0.1 - Digital audio PCM (McBSP2)
> You might want to try the --rate parameter for arecord to use 16KHz
> from the Voice interface..
> > Regards,
> > Shariff
> > _______________________________________________
> > Alsa-devel mailing list
> > Alsa-devel at alsa-project.org
> > http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
More information about the Alsa-devel