[alsa-devel] PulseAudio and SNDRV_PCM_INFO_BATCH

[Alexander E. Patrakov]

15.06.2015 13:03, Lars-Peter Clausen wrote:
> On 06/12/2015 02:29 PM, Arun Raghavan wrote:
>> So I guess the first thing that would be nice to have is a clear
>> meaning of these two flags. With this done, we could potentially get
>> to the API to report the transfer size from the driver.
>
> Yeah, the meaning of those flags is somewhat fuzzy and may have changed
> over time as well. Here is my understanding of the flags, might not
> necessarily be 100% correct.
>
> SNDRV_PCM_INFO_BLOCK_TRANSFER means that the data is copied from the
> user accessible buffer in blocks of one period. Typically these kinds of
> devices have some dedicated audio memory that is not accessible via
> normal memory access and a DMA is setup to copy data from main memory to
> the dedicated memory. This DMA transfers the data from the main memory
> to the dedicated memory in chunks of period size. But otherwise the
> controller might still be capable of reporting a accurate pointer
> position down to the sample/frame level.
>
> So SNDRV_PCM_INFO_BLOCK_TRANSFER is mainly important for rewind handling
> and devices with that flag set might need additional headroom since the
> data up to one period after the pointer position has already been copied
> to the dedicated memory and hence can no longer be overwritten.
>
> SNDRV_PCM_INFO_BATCH on the other hand has become to mean that the
> device is only capable of reporting the audio pointer with a coarse
> granularity. Typically this means a period sized granularity, but there
> are some other cases as well.

I have tried to convert this text into something that can be added to 
the doxygen documentation in alsa-lib, but failed to verify the text. 
Here is why.

In kernel sources, sound/pci/hda/hda_controller.c mentions 
SNDRV_PCM_INFO_BLOCK_TRANSFER. However, sub-period rewinds work fine on 
this driver, and the avail granularity is something like 64 bytes. So, 
either the description is wrong (i.e., "large blocks, possibly up to one 
period size, but 64 bytes still counts as large" is actually meant - but 
that would be useless), or the flag is wrongly set in the driver.

-- 
Alexander E. Patrakov