Questions about writing a new ALSA driver for a very limitted device
Thanks to the help I've gotten on this list my alsa driver is working great. I got a little hung up not realizing that the alsa core basically provides everything you need to implement your own circular buffer if you need to use an intermediate buffer.
The only question I still have is that if alsa allocates your DMA buffer for you based on snd_pcm_hardware_t buffer_bytes_max what exactly does snd_pcm_lib_preallocate_pages_for_all allocate buffers for? Does this allocate the buffers that would be passed to the copy callback?
Thanks,
Tim
Quoted 65 lines · --- Tim Harvey
Greetings,
I'm setting out to write an ALSA driver for a very limited device thats behind
a PLD. The actual codec is a uda1380 and does 16bit MSB stereo encode/decode.
The way the device is driven the sampling rate is limited to 8KHz and data transfer to/from the device I have to handle manually.I've read over the 'writing an ALSA driver' tutorial and have started the driver but have run into a few questions:
- for the specs I've given above: 8000Hz sampling rate, 16bit stereo MSB
samples does the followingsnd_pcm_hardware_tlook right?:static
snd_pcm_hardware_tmy_playback_hw= {
.info = (SNDRV_PCM_INFO_MMAP|
SNDRV_PCM_INFO_INTERLEAVED|
SNDRV_PCM_INFO_BLOCK_TRANSFER|
SNDRV_PCM_INFO_MMAP_VALID),
.formats =SNDRV_PCM_FMTBIT_U16_BE, // is this 16bit MSB?
.rates =SNDRV_PCM_RATE_8000, // seems redundant?
.rate_min = 8000,
.rate_max = 8000,
.channels_min = 2,
.channels_max = 2,
.buffer_bytes_max = 32768,
.period_bytes_min = 4096,
.period_bytes_max = 32768,
.periods_min = 1,
.periods_max = 1024,
};- I'm a little confused at how to deal with copying data from/to the device.
It looks like I would implement the copy callback and copy the passed buffer to
the device in the device specific manner I need to (playback), but I'm not clear where to put data that I receive from the device (capture). I notice that when thehw_paramscallback is called a dma buffer has been created by ALSA in thesubstream->runtimestruct. I assume this is created based on htebuffer_bytes_maxfield above and I'm to copy data to this buffer? How do I know where to copy it within the buffer and what data ALSA has already consumed
from the buffer?- I might need to create an intermediate buffer between ALSA's rather large
buffers and my hardware buffer. Is there any driver that I could look at that
does this? The tutorial talks about the vxpocket driver but that code looks very foriegn from the rest of the ALSA drivers.- I'm not sure I understand what the 'period' is about. Its clear to me
that
I need to callsnd_pcm_period_elapsed()periodically from either an IRQ or other timed callback, but I'm not clear what the hardware pointer is or how that converts to 'frames' and 'periods'.- in general, if my hardware device only allows 16bit MSB 8KHz, does ALSA
provides a mechanism for converting data from other formats?Thanks for any pointers,
Tim
At Thu, 26 Apr 2007 15:30:41 -0700 (PDT),
Quoted 10 lines · Tim Harvey
Thanks to the help I've gotten on this list my alsa driver is working great. I got a little hung up not realizing that the alsa core basically provides everything you need to implement your own circular buffer if you need to use an intermediate buffer.
The only question I still have is that if alsa allocates your DMA buffer for you based on
snd_pcm_hardware_tbuffer_bytes_maxwhat exactly doessnd_pcm_lib_preallocate_pages_for_allallocate buffers for? Does this allocate the buffers that would be passed to the copy callback?
hardware.buffer_bytes_max can be really big. Many hardwares have no hardware limitation, i.e. can be 4GB or more in theory. The paramters passed to preallocator is the "reasonable" buffer sizes for normal uses.
Without preallocator, you'll have to allocate buffer at each open. Particularly in the case of contiguous pages, it gets always more difficult because the whole memory area gets more fragmented. Thus, you'd like to preallocate the buffer and keep that area for later use.
Currently, there is a constraint that the max buffer size is limited by the preallocated size (if any), so a buffer bigger than preallocated won't work. I don't know why this constraint exists, and I believe it's fine to remove it. (You can see FIXME comment there indeed)
Takashi