From: Jack Mitchell <ml@communistcode.co.uk>
To: alsa-devel@alsa-project.org
Subject: Re: [3.13-rc8] AM335x BeagleBone Buffer XRUN
Date: Thu, 16 Jan 2014 10:44:53 +0000 [thread overview]
Message-ID: <52D7B825.30305@communistcode.co.uk> (raw)
In-Reply-To: <52D59E8A.1010400@communistcode.co.uk>
On 14/01/14 20:31, Jack Mitchell wrote:
> I am currently trying to debug a buffer overrun when capturing with the
> BeagleBone Black and Audio Cape attached on 3.13-rc8, this is pretty
> much the same setup as the am335x-evm. The following is the traceback
> captured using the XRUN_BUFFER_DEBUG kernel config option. I think an
> interrupt is taking too long to return.
>
> [snip
>
Ok, so I managed to enlarge the buffer by increasing the
max_buffer_bytes in snd_pcm_hardware capture struct. However, it doesn't
really make sense... The original value was (128*1024) which should give
a buffer of 128K, but in reality it gave a buffer of 32K. Now when I was
hacking last night it got to the point where I just started twiddling
knobs to see what would happen, and it turns out that changing the
max_buffer_bytes to (256*1024) gave me 64K of buffer. So, I don't have a
clue what is going on here, but I now have enough buffer to get the
audio data captured and written out before an overflow occurs.
Cheers,
--
Jack Mitchell (jack@embed.me.uk)
Embedded Systems Engineer
Cambridgeshire, UK
http://www.embed.me.uk
--
prev parent reply other threads:[~2014-01-16 10:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-14 20:31 [3.13-rc8] AM335x BeagleBone Buffer XRUN Jack Mitchell
2014-01-16 10:44 ` Jack Mitchell [this message]
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=52D7B825.30305@communistcode.co.uk \
--to=ml@communistcode.co.uk \
--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