From: Rajeev kumar <rajeev-dlh.kumar@st.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"lrg@slimlogic.co.uk" <lrg@slimlogic.co.uk>
Subject: Re: overrun in case of record
Date: Wed, 7 Sep 2011 09:44:59 +0530 [thread overview]
Message-ID: <4E66EFC3.2070706@st.com> (raw)
In-Reply-To: <20110906180138.GC2924@opensource.wolfsonmicro.com>
Hello Mark
On 9/6/2011 11:31 PM, Mark Brown wrote:
>> pcm_read error: For this I have seen a bug is locked in the
>> > bugzila(*Bug 472469*<show_bug.cgi?id=472469> -arecord: input/output
>> > error ). and the status is closed saying insufficient data.
>> > Could you please let me know what is the meaning of this bug? Is it
>> > like, data is not available in the buffer and pcm_read from the user
>> > space fails? But why this situation will
>> > arise?
> You'll need to investigate the bug.
> .
>
I analyzed the bug and found that if I use arecord in non-blocking
mode, it works fine.
#arecord -f dat --nonblock > t
Working in a non-blocking mode means there is no data available in ring
buffer and returning -EAGAIN from the alsa, so application is
wating for data to arrive in the ring buffer. Now it is not clear to me
why this situation will arise?
I have checked the clock and all the clock are intact. The calculation
for number of bytes received in a sec is correct.
Best Regards
Rajeev
next prev parent reply other threads:[~2011-09-07 4:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-06 9:34 overrun in case of record Rajeev kumar
2011-09-06 18:01 ` Mark Brown
2011-09-07 4:14 ` Rajeev kumar [this message]
2011-09-07 8:35 ` Clemens Ladisch
2011-11-17 13:35 ` Exporting playback and capture capability to user space Rajeev kumar
2011-11-17 15:19 ` Mark Brown
2011-11-21 5:49 ` Rajeev kumar
2011-11-21 6:23 ` Vinod Koul
2011-11-22 4:27 ` Rajeev kumar
2011-11-22 13:08 ` Mark Brown
2011-11-23 4:36 ` Rajeev kumar
2011-12-02 10:50 ` Rajeev kumar
2011-12-02 11:50 ` Vinod Koul
2012-01-09 6:31 ` Rajeev kumar
2012-01-12 8:45 ` Rajeev kumar
2011-11-21 10:55 ` Mark Brown
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=4E66EFC3.2070706@st.com \
--to=rajeev-dlh.kumar@st.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=lrg@slimlogic.co.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.