All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eliot Blennerhassett <linux@audioscience.com>
To: alsa-devel@alsa-project.org
Subject: Understanding SND_PCM_INFO_ [BATCH, BLOCK_TRANSFER, DOUBLE]
Date: Wed, 17 Feb 2010 20:35:36 +1300	[thread overview]
Message-ID: <4B7B9C48.5070608@audioscience.com> (raw)

I've been looking at these info flags, and whether they cause the driver
to be accessed any differently by the upper layers.
So far I can find hardly any examples where they are used in any
significant way - what am I missing if anything?

SND_/SNDRV_
_PCM_INFO_BATCH
double buffering
skips the check enabled by XRUN_DEBUG_JIFFIESCHECK
alsa-lib returns it in snd_pcm_hw_params_is_batch()

_PCM_INFO_BLOCK_TRANSFER
/* hardware transfer block of samples */
translated by pcm_oss.c into ~DSP_CAP_REALTIME
lib: snd_pcm_hw_params_is_block_transfer()

_PCM_INFO_DOUBLE
/* double buffering needed for PCM start/stop */
snd_pcm_hw_params_is_double()

I don't see any of these functions called by aplay...


--
Eliot

                 reply	other threads:[~2010-02-17  7:36 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4B7B9C48.5070608@audioscience.com \
    --to=linux@audioscience.com \
    --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.