October 2007 - Alsa-devel - mailman.alsa-project.org

[alsa-devel] Snd problem ... ( ACCESS_TYPE )
by errordeveloper＠gmail.com 03 Oct '07

03 Oct '07

Hi list. I' m using alsa-lib v1.0.14rc2 on gentoo-linux (v2.6.20-gentoo-r8) my soundcard is RME Hammerfall HDSP9632 (snd-hdsp driver) i have been using it for a while - all fine i only run a few applications for my sound experiments. one of those is Snd (from CCRMA), it was okay until i have done a few updates lately - kernel from 2.6.17 to 2.6.20 and alsa-lib as well. i'm not sure about either of these but i check Snd src-tree and the mailing list - nothing was changed .. the error msg that i get is: :(play) ;status of hw:0 hw_params status of hw:0 ACCESS: MMAP_NONINTERLEAVED RW_NONINTERLEAVED FORMAT: S32_LE SUBFORMAT: STD SAMPLE_BITS: 32 FRAME_BITS: [128 384] CHANNELS: [4 12] RATE: [32000 192000] PERIOD_TIME: (333 256000] PERIOD_SIZE: [64 8192] PERIOD_BYTES: [2560 393216] PERIODS: 2 BUFFER_TIME: (666 512000] BUFFER_SIZE: [128 16384] BUFFER_BYTES: [2560 786432] TICK_TIME: 1000 sw_params status of hw:0 start_mode: DATA xrun_mode: STOP tstamp_mode: NONE period_step: 0 sleep_min: 0 avail_min: 0 xfer_align: 0 silence_threshold: 0 silence_size: 0 boundary: 0 ;Invalid argument: hw:0: access type RW_INTERLEAVED not available can't play : Invalid argument: hw:0: access type RW_INTERLEAVED not available #f : i had tried to modify audio.c in Snd's tree to use both ACCESS types given above , but it didn't help - showed device is busy error instead. i'm only studying C, so can't be sure .. anyway here is a problem which i could not solve yet and haven't seen anyone helpful around #alsa, neither i could google anything out. for a ref.: Cmdist mailing list Cmdist(a)ccrma.stanford.edu http://ccrma-mail.stanford.edu/mailman/listinfo/cmdist and our discussion is here: http://ccrma-mail.stanford.edu/pipermail/cmdist/2007-July/004221.html could anyone have a look at this at somepoint, please . -- thank you, Ilya. D errordeveloper|*@*|gmail|*dot*|com

1 0

[alsa-devel] ASOC: Best way to get private data from machine driver to the other drivers?
by Timur Tabi 02 Oct '07

02 Oct '07

I'm writing an ASOC driver. When my machine driver loads, it determines some hardware information for the DMA controllers, some other hardware information for the I2S controller, and even more information for the codec. I want to be able to pass all this information to each of the three other drivers. Unfortunately, it doesn't appear that I have enough "private_data" pointers available to me. The current ASOC drivers all use statically defined global structures and indexes into arrays of these structures to identify individual devices, such associating I2S controller #2 with DMA channels 3 and 4. On PowerPC, this doesn't work. The actual hardware configuration is determined at runtime (see arch/powerpc/boot/dts/), and so the machine driver needs to collect all the information and make all the device-to-device associations. For example, the PCM driver has an open function: static struct snd_pcm_ops fsl_dma_ops = { .open = fsl_dma_open, ... static int fsl_dma_open(struct snd_pcm_substream *substream) { ... What I would like is for fsl_dma_open() to be able to obtain pointers to the DMA controller's registers (there are two controllers with 4 channels each) by looking inside 'substream'. How can I do that? -- Timur Tabi Linux Kernel Developer @ Freescale

2 8

[alsa-devel] some problem about alsa lib usage on arm926
by Akio 02 Oct '07

02 Oct '07

Dear All: right now, I'm using alsa lib interface to work with voip application. Our hardware platform is an ARM926 266MHz box with Linux kernel 2.6.19.2. We got some problems. would you like to do us favors? 1. what is the different between "plughw:0,0", "defalut", "hw:0.0"? after reading the document in http://www.alsa-project.org/alsa-doc/alsa-lib/pcm.html about "PCM naming conventions", we still not very sure the relationship between those device conventions. is there any more detail documents talk about on this? right now, we are using alsa lib 1.0.13 and the device is "plughw:0,0". 2. Is there any documents detail discuss the setting about sample rate, buffer size, period size. because, I have two different voice codec to handle, one is narrow band(8k Hz), the other is wide band(16K Hz). right now, I using the following functions and setting to make alsa work. snd_pcm_hw_params_set_rate_near sets sample rate, 8k or 16k. snd_pcm_hw_params_set_period_size_near sets period size, current is 128. snd_pcm_hw_params_set_buffer_size_near sets buffer size, 8k is 2048, 16k is 4096. the unit seems be samples not byte. 3. the code was based on the following URL. http://www.suse.de/~mana/alsa090_howto.html http://www.equalarea.com/paul/alsa-audio.html open capture and playback at one function, and provide one read and one write interface to up layer. here comes three problems: a. the channel opened is just only one, but If I set the snd_pcm_hw_params_set_access as SND_PCM_ACCESS_RW_NONINTERLEAVED. using snd_pcm_readn and snd_pcm_writen the code will not work. what is the wrong? but if set snd_pcm_hw_params_set_access as SND_PCM_ACCESS_RW_INTERLEAVED and using snd_pcm_readi and snd_pcm_writei. the code work very well. one channel also have data interleave problem? I don't understand why? b. in snd_pcm_open the block flag is set as 0. what is the mode of the operation? blocking or non-blocking? c. call the xrun_recovery() timing. currently the xrun_recovery only do on EPIPE. the following is the handling core. err = snd_pcm_prepare(handle); if(err == -ESTRPIPE) { while ((err = snd_pcm_resume(handle)) == -EAGAIN) { nanosleep(&retryTime, &tmpTime); LOG("audio device resume fail, %s\n", snd_strerror(err)); } if(err < 0) { err = snd_pcm_prepare(handle); if(err < 0) LOG("audio data IO fail, %s\n", snd_strerror(err)); } } else { if(err < 0) LOG("audio device prepare fail, %s\n", snd_strerror(err)); } Does the code have any missing point to handle? If any missing, what should I to add? 4. BTW, I call xrun_recovery both in capture and playback direction. After long time test. the test procedure is as the following steps: 1. capture voice data as PCM data. 2. encoded as amr-wb bit stream. 3. decoded as PCM data from encoded bit stream. 4. playback PCM data. after 16 hours continue tests, there are some delay, about 800 mili seconds. is there any way to reduce the delay after long time test. we want make the delay about < 400 mili seconds after one week continue test. BTW, is there any way to prevent xrun_recovery calling? is there any index to monitor ALSA device buffer information? 5. If we want using salsa lib to replace the usage of alsa lib, what do we have to take care? how about the latency and performance between salsa and alsa? how about the stability of salsa? There are so many problems after many tests. If you found any documents we need to study more detail. please tell us. Thanks in advance. Thank you. Best Regards, Akio

2 3

[alsa-devel] issue with ADI A1986A
by l1983＠bankerinter.net 01 Oct '07

01 Oct '07

Hello, I need some help from you guys. I,m a new linux user and totally unfamiliar with all this coding... I have an issue with my motherboard "ASSUS M2N-MX" and it's onboard sound chip :"ADI AD1986A" witch supports 6 channel CODEC , Jack-Sensing & Enumeration technology , and with S/PDIF OUT interface. Can you please somehow, (or somebody you know) , make for me some installable .deb archive that will help me to set up my sound, since i can't do it on my own. :( Or help me some how else, (either sending me some address's or by giving me some other advice. HELP ME PLEASE!!!!!! l1983(a)bankerinter.net

1 0