This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

audio driver problem based on AM35x-OMAP35x-PSP-SDK-03.00.01.06

Other Parts Discussed in Thread: TPS65930, OMAP3530

Hi,

    I used omap3530 with tps65930 to develop a voip project, and my project is based on a open source

project "linphone", and linphone uses ALSA audio framework. when I used the version of 2.6.28 linux

kernel,  audio is ok, I can capture and playback at the same time, but when I ported the project to

PSP-03.00.01.06(2.6.32 ), I only can capture or playback at a time, can't capture and playback at  the

same time.  I checked  sound driver, I found that this version of sound driver has been changed to use

omap3530 internal audio buffer(McBSP2: 4096 bytes), on the function of "omap_mcbsp_dai_startup()", this

buffer will be all alocated to tx or rx, so this driver didn't consider the case of audio rx and tx at

the same time. Could anyone please tell me how to modify this driver? thanks

Best regards
everest.zhang

 

  • Hi Zang,

    We do have similar test case as part of our unit-test matrix and after your query I verified it in log and test report of Audio driver. Just for your reference below is the command which we use and simulate loopback use-case -

    ----------Log-----------------

    # arecord -f dat | aplay -f dat

    Recording WAVE 'stdin' : Signed 16 bit Little Endian, Rate 48000 Hz, Stereo\r

    Playing WAVE 'stdin' : Signed 16 bit Little Endian, Rate 48000 Hz, Stereo\r

    Aborted by signal Interrupt...\r

    Aborted by signal Interrupt...\r

    ----------End Log-----------------

     

    Thanks,

    Vaibhav

     

     

  • I too had trouble with audio and linphone. on an EVM Mistral AM37X eval board. the kernel version 2.6.32.

    My complain was linphone did not detect a suitable sound card (i guess it was looking for something like a /dev/dsp, which is no longer needed)

    Any clues as to how you went about resolving this issue?