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

Re: [alsa-devel] capturing data from the microphone
by Mark Brown 06 Jan '10

06 Jan '10

On Wed, Jan 06, 2010 at 11:44:04AM +0100, Marc Garnier wrote: > OK, well, I work on a custom device platform based on an Atmel > at91sam9261. I wrote an alsa driver composed of 2 files CCing in the list and Sedji, who wrote the driver. Please also try avoid top posting - Linux lists generally intersperse replies with the relevant context from the original message since it makes mails much more legible. > But when I want to record a pcm stream I have this error: > # arecord -v -c 1 -t wav -f S16_LE -r 8000 -d 10 input.wav > arecord: pcm_read:1629: read error: Input/output error [With an AT91 in slave mode...] > and actually no interrupt occur and I > wonder why... Can you see clocks on the audio interface? Have you checked that the pins on the processor are configured to route the signals to the correct IP block?

2 1

[alsa-devel] ASoC updates for 2.6.33
by Mark Brown 04 Jan '10

04 Jan '10

The following changes since commit c5974b835a909ff15c3b7e6cf6789b5eb919f419: Linus Torvalds (1): Merge branch 'limits_cleanup' of git://decibel.fi.muni.cz/~xslaby/linux are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound-2.6.git for-2.6.33 Takashi is on holiday for the first few weeks of the year so he said to send direct pull requests in the interim. The patch from Morimoto-san is finishing off a cross-tree merge while the others are driver-specific fixes. Guennadi Liakhovetski (1): ASoC: fix params_rate() macro use in several codecs Kuninori Morimoto (1): ASoC: fsi-ak4642: Remove ak4642_add_i2c_device Manuel Lauss (1): ASoC: fixup oops in generic AC97 codec glue Mark Brown (1): Merge commit 'v2.6.33-rc2' into for-2.6.33 sound/soc/codecs/ac97.c | 6 ++++++ sound/soc/codecs/wm8510.c | 14 +++++++------- sound/soc/codecs/wm8940.c | 14 +++++++------- sound/soc/codecs/wm8974.c | 14 +++++++------- sound/soc/sh/fsi-ak4642.c | 30 ------------------------------ 5 files changed, 27 insertions(+), 51 deletions(-)

1 0

[alsa-devel] [PATCH] ASoc: tpa6130a2: Remove unnecessary variable
by Ilkka Koskinen 04 Jan '10

04 Jan '10

Signed-off-by: Ilkka Koskinen <ilkka.koskinen(a)nokia.com> --- sound/soc/codecs/tpa6130a2.c | 4 ---- 1 files changed, 0 insertions(+), 4 deletions(-) diff --git a/sound/soc/codecs/tpa6130a2.c b/sound/soc/codecs/tpa6130a2.c index 0eb33d4..8e98ccf 100644 --- a/sound/soc/codecs/tpa6130a2.c +++ b/sound/soc/codecs/tpa6130a2.c @@ -267,12 +267,8 @@ static const struct snd_kcontrol_new tpa6130a2_controls[] = { */ static void tpa6130a2_channel_enable(u8 channel, int enable) { - struct tpa6130a2_data *data; u8 val; - BUG_ON(tpa6130a2_client == NULL); - data = i2c_get_clientdata(tpa6130a2_client); - if (enable) { /* Enable channel */ /* Enable amplifier */ -- 1.6.0.4

3 2

[alsa-devel] [PATCH] ASoC: fixup oops in generic AC97 codec glue
by Manuel Lauss 04 Jan '10

04 Jan '10

Initialize the glue by calling snd_soc_new_ac97_codec() as is done in other ASoC AC97 codecs. Fixes an oops caused by dereferencing uninitialized members in snd_soc_new_pcms(). Run-tested on Au1250. Signed-off-by: Manuel Lauss <manuel.lauss(a)gmail.com> --- Fixes the oops I reported here: http://mailman.alsa-project.org/pipermail/alsa-devel/2009-December/023995.h… sound/soc/codecs/ac97.c | 6 ++++++ 1 files changed, 6 insertions(+), 0 deletions(-) diff --git a/sound/soc/codecs/ac97.c b/sound/soc/codecs/ac97.c index 69bd0ac..a1bbe16 100644 --- a/sound/soc/codecs/ac97.c +++ b/sound/soc/codecs/ac97.c @@ -102,6 +102,12 @@ static int ac97_soc_probe(struct platform_device *pdev) INIT_LIST_HEAD(&codec->dapm_widgets); INIT_LIST_HEAD(&codec->dapm_paths); + ret = snd_soc_new_ac97_codec(codec, &soc_ac97_ops, 0); + if (ret < 0) { + printk(KERN_ERR "ASoC: failed to init gen ac97 glue\n"); + goto err; + } + /* register pcms */ ret = snd_soc_new_pcms(socdev, SNDRV_DEFAULT_IDX1, SNDRV_DEFAULT_STR1); if (ret < 0) -- 1.6.6.rc3

2 1

[alsa-devel] Underrun problem and some basic queries
by ANISH KUMAR 04 Jan '10

04 Jan '10

1 0

[alsa-devel] [PATCH 0/5] ASoC: tlv320dac33: Adding new FIFO mode
by Peter Ujfalusi 04 Jan '10

04 Jan '10

Hello, the following series adds new FIFO operating mode to the tlv320dac33 codec driver. To be able to add new FIFO mode the code has to be restructured in order to keep it readable after the new mode is added. Since both of the support FIFO mode in the driver needs the codec to be the master, an additional check is added to avoid misconfiguration. --- Peter Ujfalusi (5): ASoC: tlv320dac33: Change nsample switch to FIFO mode enum ASoC: tlv320dac33: Introduce prefill and playback state handlers ASoC: tlv320dac33: Clean up the hardware configuration code ASoC: tlv320dac33: Add new FIFO mode: mode 7 ASoC: tlv320dac33: Safety check for codec slave mode sound/soc/codecs/tlv320dac33.c | 190 ++++++++++++++++++++++++++++++++-------- 1 files changed, 153 insertions(+), 37 deletions(-)

2 8

[alsa-devel] Underrun problem and some basic queries
by ANISH KUMAR 04 Jan '10

04 Jan '10

1 0

[alsa-devel] Echoaudio, suspend/resume question on rawmidi device
by Giuliano Pochini 03 Jan '10

03 Jan '10

I have some patches that add PM support to all echoaudio drivers. It seems to work fine, but it has been tested on two cards only and the rawmidi device hasn't been tested at all. I can't test it because suspend-to-anything does not work on my pmac. I want to be sure at least it cannot deadlock. * On suspend: Rawmidi input is interrupt-driven. The driver tells the card to stop accepting data. Rawmidi output is timer-driven. The driver uses a timer to check if the card's output buffer has room for more data to send. Do del_timer_sync() and wait until all buffered data is sent, which may take 20ms (64 bytes at 31250bps). * On resume: Input: Re-enable midi in. Output: Restart the timer. Do you see any race condition or weak points in this scheme, especially in the midi-out part ? Is del_timer_sync() safe ? -- Giuliano.

1 0

[alsa-devel] Cross-compile problem with alsa-driver version 1.0.22
by Jie Jiang 03 Jan '10

03 Jan '10

Hi all, Recently I downloaded alsa-driver 1.0.22 and tried to build for i.MX27 platform. The "INSTALL" file enclosed in this release requires "--with-cross=arm-linux-" configuration option to cross-compile alsa driver for this ARM platform. Here is my build process #./configure --with-cross=arm-linux- --with-kernel=/home/working/bsp/Kernel/linux-2.6.19.2 --with-build=/home/working/bsp/ Kernel/linux-2.6.19.2 --with-moddir=/home/working/bsp/tmp --with-debug=full --enable-dynamic-minors --with-cards=all checking for gcc... arm-linux-gcc checking for C compiler default output file name... a.out checking whether the C compiler works... configure: error: cannot run C compiled programs. If you meant to cross compile, use `--host'. See `config.log' for more details. It seems that "--host=arm-linux" should be provided to configure script. However, when given the --host option, in the generated "Makefile.conf", I saw the following outputs, which are very confusing: NEW_KBUILD = mainsrcdir = . MAINSRCDIR = /work/63/alsa/alsa-driver-1.0.22 CROSS_COMPILE ?= arm-linux- ARCH ?= ifdef NEW_KBUILD CC = $(CROSS_COMPILE)arm-linux-gcc CPP = $(CROSS_COMPILE)arm-linux-gcc -E export CROSS_COMPILE ARCH else AS = $(CROSS_COMPILE)as LD = $(CROSS_COMPILE)ld CC = $(CROSS_COMPILE)arm-linux-gcc CPP = $(CROSS_COMPILE)arm-linux-gcc -E AR = $(CROSS_COMPILE)ar MODFLAGS = -DMODULE=1 CFLAGS_KERNEL = GENKSYMS = /sbin/genksyms -k 0.0.0 endif Obviously, the CC and CPP variables are not expected as "arm-linux-gcc". (There is one more $(CROSS_COMPILE)!) I overcome this problem by providing CC and CROSS_COMPILE variables with configure script: CC=gcc CROSS_COMPILE=arm-linux-gcc ./configure --with-cross=arm-linux- --with-kernel=/home/working/bsp/Kernel/linux-2.6.19.2 --with-build=/home/working/bsp/Kernel/linux-2.6.19.2 --with-moddir=/home/working/bsp/tmp --with-debug=full --enable-dynamic-minors --with-cards=all Then things become OK. What's wrong with the "INSTALL" file? Another problem. Even if "--with-cards=all" is given, codes in soc/codecs, soc/imx, and many other subdirs are not built. It seems that the configure script sets some variables according to the kernel version and target platform and outputs into "toplevel.config". Is it possible to manually edit "toplevel.config" file (after configure process) to get soc/codecs, soc/imx codes compiled? Regards, Jie

2 1

[alsa-devel] Trouble with sound over HDMI with Nvidia MCP7A HDMI
by Austin Robertson 03 Jan '10

03 Jan '10

I am having trouble getting sound over hdmi with my Nvidia MCP7A HDMI. The strange thing is that everything works fine in a Live disc, but once I do a fresh install of that Live disc I get no sound, even though my configuration is exactly the same (as far as I can tell). I've checked the little things like alsamixer volumes, aplay -l, etc etc. Everything looks good to me. I can reproduce on multiple TVs so its not the receiver. Video drivers are the same in both live version and installed. aplay -l detects my device. sound/pci/hda/patch_nvhdmi.c already has my correct vendor id in it. Perhaps the following info can help figure out what my installed environment is lacking. I've been at it for days now and I'm stumped! Any ideas? *Live Disc Info* XMBC Live 9.11 (basically a optimized version of Karmic configured to start XBMC, or Xbox Media Center, see http://www.xbmc.org for more info) NOTE: My problem is not specific to the XBMC program. Things like aplay and speaker-test don't work either. *Hardware* Acer Aspire Revo R1600 http://www.newegg.com/Product/Product.aspx?Item=N82E16883103228&Tpk=AR1600 *XBMC Live installed to hard disk via Ubuntu installer* (This setup gives me no sound over HDMI) (This is a fresh install. No additional changes were made) alsa-info.sh http://www.alsa-project.org/db/?f=ab7cef7c7233f8c42756d36e362df684b9147d38 xbmc@XBMCLive:~$ aplay -l **** List of PLAYBACK Hardware Devices **** card 0: NVidia [HDA NVidia], device 0: ALC662 rev1 Analog [ALC662 rev1 Analog] Subdevices: 0/1 Subdevice #0: subdevice #0 card 0: NVidia [HDA NVidia], device 3: NVIDIA HDMI [NVIDIA HDMI] Subdevices: 1/1 Subdevice #0: subdevice #0 xbmc@XBMCLive:~$ aplay -L default:CARD=NVidia HDA NVidia, ALC662 rev1 Analog Default Audio Device front:CARD=NVidia,DEV=0 HDA NVidia, ALC662 rev1 Analog Front speakers surround40:CARD=NVidia,DEV=0 HDA NVidia, ALC662 rev1 Analog 4.0 Surround output to Front and Rear speakers surround41:CARD=NVidia,DEV=0 HDA NVidia, ALC662 rev1 Analog 4.1 Surround output to Front, Rear and Subwoofer speakers surround50:CARD=NVidia,DEV=0 HDA NVidia, ALC662 rev1 Analog 5.0 Surround output to Front, Center and Rear speakers surround51:CARD=NVidia,DEV=0 HDA NVidia, ALC662 rev1 Analog 5.1 Surround output to Front, Center, Rear and Subwoofer speakers surround71:CARD=NVidia,DEV=0 HDA NVidia, ALC662 rev1 Analog 7.1 Surround output to Front, Center, Side, Rear and Woofer speakers hdmi:CARD=NVidia,DEV=0 HDA NVidia, NVIDIA HDMI HDMI Audio Output null Discard all samples (playback) or generate zero samples (capture) * ### speaker-test executes but NO SOUND over hdmi*. *I've also tried other devices like -D hdmi:0 -D hw:0,3 -D hdmi -D plug:hdmi, etc, etc* xbmc@XBMCLive:~$ speaker-test -D plughw:0,3 -c2 speaker-test 1.0.20 Playback device is plughw:0,3 Stream parameters are 48000Hz, S16_LE, 2 channels Using 16 octaves of pink noise Rate set to 48000Hz (requested 48000Hz) Buffer size range from 64 to 16384 Period size range from 32 to 8192 Using max buffer size 16384 Periods = 4 was set period_size = 4096 was set buffer_size = 16384 0 - Front Left 1 - Front Right Time per period = 5.637709 0 - Front Left xbmc@XBMCLive:~$ cat /proc/driver/nvidia/version NVRM version: NVIDIA UNIX x86 Kernel Module 190.53 Tue Dec 8 18:51:41 PST 2009 GCC version: gcc version 4.4.1 (Ubuntu 4.4.1-4ubuntu8) * XMBC Live Disc * ** (This setup gives me audio over hdmi perfectly) (This is running as a Live disc, ie not installed) ** alsa-info.sh http://www.alsa-project.org/db/?f=c95bebdc433f15147fb0be415be4e61e4d0b72ad [ ^<http://www.alsa-project.org/db/?f=c95bebdc433f15147fb0be415be4e61e4d0b72ad> ] xbmc@XBMCLive:~$ aplay -l **** List of PLAYBACK Hardware Devices **** card 0: NVidia [HDA NVidia], device 0: ALC662 rev1 Analog [ALC662 rev1 Analog] Subdevices: 0/1 Subdevice #0: subdevice #0 card 0: NVidia [HDA NVidia], device 3: NVIDIA HDMI [NVIDIA HDMI] Subdevices: 1/1 Subdevice #0: subdevice #0 xbmc@XBMCLive:~$ aplay -L default:CARD=NVidia HDA NVidia, ALC662 rev1 Analog Default Audio Device front:CARD=NVidia,DEV=0 HDA NVidia, ALC662 rev1 Analog Front speakers surround40:CARD=NVidia,DEV=0 HDA NVidia, ALC662 rev1 Analog 4.0 Surround output to Front and Rear speakers surround41:CARD=NVidia,DEV=0 HDA NVidia, ALC662 rev1 Analog 4.1 Surround output to Front, Rear and Subwoofer speakers surround50:CARD=NVidia,DEV=0 HDA NVidia, ALC662 rev1 Analog 5.0 Surround output to Front, Center and Rear speakers surround51:CARD=NVidia,DEV=0 HDA NVidia, ALC662 rev1 Analog 5.1 Surround output to Front, Center, Rear and Subwoofer speakers surround71:CARD=NVidia,DEV=0 HDA NVidia, ALC662 rev1 Analog 7.1 Surround output to Front, Center, Side, Rear and Woofer speakers hdmi:CARD=NVidia,DEV=0 HDA NVidia, NVIDIA HDMI HDMI Audio Output null Discard all samples (playback) or generate zero samples (capture) ###* speaker-test plays audio over hdmi perfectly. other programs play audio over hdmi.* xbmc@XBMCLive:~$ speaker-test -D plughw:0,3 -c2 speaker-test 1.0.20 Playback device is plughw:0,3 Stream parameters are 48000Hz, S16_LE, 2 channels Using 16 octaves of pink noise Rate set to 48000Hz (requested 48000Hz) Buffer size range from 64 to 16384 Period size range from 32 to 8192 Using max buffer size 16384 Periods = 4 was set period_size = 4096 was set buffer_size = 16384 0 - Front Left 1 - Front Right Time per period = 5.638693 xbmc@XBMCLive:~$ cat /proc/driver/nvidia/version NVRM version: NVIDIA UNIX x86 Kernel Module 190.53 Tue Dec 8 18:51:41 PST 2009 GCC version: gcc version 4.4.1 (Ubuntu 4.4.1-4ubuntu8) *Additional Information * I had an idea to run a diff on the two alsa-info.sh outputs of my installed and live version. (non-working and working, see above) I figured that might give me a clue on what I was missing. Most things should be identical with a few exceptions like timestamps, etc. MacBook-Austin:Desktop Austin$ diff -crB alsa-info_installed.txt alsa-info_live.txt > alsa-infodiff.diff alsa-info_installed.txt: http://pastebin.com/f63afa045 (non-working, same as above) alsa-info_live.txt: http://pastebin.com/f7b47d46d (working, same as above) alsa-infodiff.diff: http://pastebin.com/f79cf9c15 Only a few things caught my attention. At first I thought I had my playback volumes muted (line 525,532) according to the diff. But then I realized that was just for the mic, so that shouldn't matter. The only other thing that I saw was that my Amp-Out vals differed (line 123, 129). Perhaps, a more trained eye will have better luck. Bug has also been reported here: https://bugtrack.alsa-project.org/alsa-bug/view.php?id=4865

1 0