All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alan Young <Alan.Young@IEE.org>
To: alsa-devel@alsa-project.org
Subject: Difference between boundary and buffer_size
Date: Thu, 3 Nov 2016 09:11:04 +0000	[thread overview]
Message-ID: <581AFF28.5060500@IEE.org> (raw)

The code in the kernel, in /pcm_lib.c/ and /pcm_native.c/, uses fields 
buffer_size and boundary in struct snd_pcm_runtime. As far as I can see, 
there are always initialized to the same value. In what circumstance 
might they be different? There is clearly some relationship to 
hw_ptr_base, as illustrated by this repeated snipped from 
snd_pcm_update_hw_ptr0()

		hw_base += runtime->buffer_size;
		if (hw_base >= runtime->boundary) {
			hw_base = 0;
			crossed_boundary++;
		}
		new_hw_ptr = hw_base + pos;

Alan.

             reply	other threads:[~2016-11-03  9:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-03  9:11 Alan Young [this message]
2016-11-03 16:45 ` Difference between boundary and buffer_size Lars-Peter Clausen
2016-11-03 22:56   ` Lars-Peter Clausen
2016-11-03 20:01 ` Clemens Ladisch

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=581AFF28.5060500@IEE.org \
    --to=alan.young@iee.org \
    --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 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.