From: Clemens Ladisch <clemens@ladisch.de>
To: alsa-devel@alsa-project.org
Subject: Re: what is period_size, buffer_size and boundary size, i confuse them
Date: Sun, 09 Dec 2012 17:22:27 +0100 [thread overview]
Message-ID: <50C4BAC3.4030300@ladisch.de> (raw)
In-Reply-To: <65bdafa4.4e24.13b8019be47.Coremail.l9jj@163.com>
l9jj wrote:
> can anyone help me to figure out the concepts between period_size ,buffer_size and boundary size?
> n * period_size = buffer_size?
Yes. On many devices, n is not required to be an integer.
> m * buffer_size = boundary_size?
Yes, where m is very big. In applications, the actual value of the boundary
size does not matter (except as a special value for some sw params).
> and how the dma buffer mapped to the alsa buffer?
The DMA buffer _is_ the ALSA buffer.
Regards,
Clemens
next prev parent reply other threads:[~2012-12-09 16:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-09 14:37 what is period_size, buffer_size and boundary size, i confuse them l9jj
2012-12-09 16:22 ` Clemens Ladisch [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-12-10 8:09 l9jj
2012-12-10 8:24 ` Clemens Ladisch
2012-12-10 9:19 l9jj
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=50C4BAC3.4030300@ladisch.de \
--to=clemens@ladisch.de \
--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