* Understanding SND_PCM_INFO_ [BATCH, BLOCK_TRANSFER, DOUBLE]
@ 2010-02-17 7:35 Eliot Blennerhassett
0 siblings, 0 replies; only message in thread
From: Eliot Blennerhassett @ 2010-02-17 7:35 UTC (permalink / raw)
To: alsa-devel
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
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2010-02-17 7:36 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-02-17 7:35 Understanding SND_PCM_INFO_ [BATCH, BLOCK_TRANSFER, DOUBLE] Eliot Blennerhassett
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).