From: Pedro Sanchez <psanchez@fosstel.com>
To: alsa-devel@alsa-project.org
Subject: ASoC: Choppy audio on OMAP using McBSP3 interface
Date: Tue, 31 May 2011 09:21:47 -0400 [thread overview]
Message-ID: <4DE4EB6B.8090605@fosstel.com> (raw)
Hello,
I wrote a ASoC driver for a TI DM3730-based custom board interfacing a
TI TAS5709 codec over the McBSP2 interface. I'm using the Linux kernel
2.6.32. The driver works very well, no problems with the sound quality
at all.
Unfortunately due to reasons alien to me I needed to move the driver to
work using the McBSP3 interface instead. All I did was then to change
the pointer in my machine code to point to the McBSP3 interface:
static struct snd_soc_dai_link bp_audio_dai = {
.name = "tas5709",
.stream_name = "tas5709",
.cpu_dai = &omap_mcbsp_dai[2], <-- from [1] to [2]
.codec_dai = &tas5709_dai,
.init = bp_audio_init,
.ops = &bp_audio_ops,
};
and in my machine init code:
*(unsigned int *)bp_audio_dai.cpu_dai->private_data = 2;
With this change the audio driver works well when playing local audio
files via the aplay command. But it fails miserably when playing
streaming audio from a VoIP connection, the audio is very choppy as it
happens when there is a large packet loss. However audio is mono 16 bits
@8 KHz, not really very demanding.
I realize there is a big difference in the internal buffer size for the
two interfaces, the McBSP2 having 10 times the buffer space of the
McBSP3. I suspect this is somehow the source of my problems. I'm
inclined to believe that there is some DMA-related optimization issue
that has to be addressed somehow, but this is just a guess.
I fail to understand why is it that I can play local audio files but not
streaming audio. What makes the difference? Any suggestions on how to
address this issue?
Thank you,
--
Pedro
next reply other threads:[~2011-05-31 13:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-31 13:21 Pedro Sanchez [this message]
2011-05-31 17:57 ` ASoC: Choppy audio on OMAP using McBSP3 interface Pedro Sanchez
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4DE4EB6B.8090605@fosstel.com \
--to=psanchez@fosstel.com \
--cc=alsa-devel@alsa-project.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox