From: Peter Ujfalusi <peter.ujfalusi@nokia.com>
To: "ext ylin@mail.com" <ylin@mail.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: Channel swapping issue on TI OMAP3/TWL4030
Date: Tue, 08 Mar 2011 15:36:07 +0200 [thread overview]
Message-ID: <4D7630C7.2080105@nokia.com> (raw)
In-Reply-To: <8CDA3184E0F0520-4AC-24D6@web-mmc-d01.sysops.aol.com>
Hi,
Sorry, I got lost of this mail thread...
On 02/25/11 17:32, ext ylin@mail.com wrote:
> Finally, after 4 days, we caught the problem again. When channel is
> swapped, the IRQ is trigger with receive underrun (IRQ_STATUS_REG =
> 0x171e). And, from the status register, the transmit is overflow as
> well. However, I didn't fill zero to one of the transmit channel, and
> couldn't tell if the playback is swap as well. Any idea why underun
> happens, or any suggestion to fix it?
Hrm, underflow on receive, and overflow on transmit at the same time?
Do you had the transmit overflow irq enabled as well?
Do you have access to the OMAP Errata documents? I have seen an Errata
for McBSP2, which was about corruption on transmit operation. It might
be, that the same thing causes nasty effects on the receive side as well.
Because of the nature of this happening in your case, I suspect that we
are facing with some HW race/bug problem.
Receive underflow happens, if DMA tries to read data from McBSP receive
data register when it is empty.
This should not happen, since the McBSP threshold and the DMA size is in
sync, so we should read an amount of data, which is for sure was in the
buffer, when McBSP signaled DMA.
Do you have support contact with TI?
I'll try to reach ours meanwhile, if they have any idea.
Regards,
Péter
next prev parent reply other threads:[~2011-03-08 13:36 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-12 16:16 Channel swapping issue on TI OMAP3/TWL4030 ylin
2011-02-13 9:25 ` Jarkko Nikula
2011-02-13 9:48 ` peter.ujfalusi
2011-02-13 10:20 ` Jarkko Nikula
2011-02-13 9:51 ` peter.ujfalusi
2011-02-14 17:58 ` ylin
2011-02-14 23:33 ` ylin
2011-02-15 7:15 ` Peter Ujfalusi
2011-02-15 6:59 ` Peter Ujfalusi
2011-02-15 16:23 ` ylin
2011-02-16 7:20 ` Peter Ujfalusi
2011-02-17 3:40 ` ylin
2011-02-17 11:44 ` Peter Ujfalusi
2011-02-19 16:08 ` ylin
2011-02-20 4:01 ` ylin
2011-02-22 7:27 ` Peter Ujfalusi
2011-02-23 15:26 ` ylin
2011-02-25 15:32 ` ylin
2011-03-08 13:36 ` Peter Ujfalusi [this message]
2011-02-19 16:17 ` ylin
2011-02-15 8:28 ` Jarkko Nikula
2011-02-15 16:28 ` ylin
2011-02-17 3:53 ` ylin
2011-02-17 8:17 ` Jarkko Nikula
2011-02-17 11:48 ` Peter Ujfalusi
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=4D7630C7.2080105@nokia.com \
--to=peter.ujfalusi@nokia.com \
--cc=alsa-devel@alsa-project.org \
--cc=ylin@mail.com \
/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;
as well as URLs for NNTP newsgroup(s).