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

[alsa-devel] spdif/iec958 outputs at VT1708S not recognized
by Sentinel 26 May '09

26 May '09

I tried using the snapshot because I was having the same problem as Peter was. No spdif out on my vt1708s. Unfortunately for me my build didn't go quite as well, for some reason I had 2 undefined which make the snd.ko fail to load. Is there something that I'm missing? I am running slamd64 distro current, with the latest kernel along with the alsa kernel patch "2.6.29.4-rt15". Please help. Building modules, stage 2. MODPOST 131 modules WARNING: "register_sound_special_device" [/usr/src/alsa-driver/acore/snd.ko] undefined! WARNING: "unregister_sound_special" [/usr/src/alsa-driver/acore/snd.ko] undefined! make[1]: Leaving directory `/usr/src/linux-2.6.29.4' utils/link-modules /usr/src/alsa-driver

1 0

[alsa-devel] [PATCH V4 0/5] AC97 driver for mpc5200
by Jon Smirl 26 May '09

26 May '09

Version 4. Changed timeouts to use relax_cpu() instead of udelay(). Fixed locking to lock bestcomm instead of registers. Code reorg as requested in the various comments. Removed sysfs over/underrun reporting. Removed reset retries. Removing the retries makes the driver fail to load about 5% of the time. An oscilliscope is needed to figure out what is going on with failed resets. Both pcm030 and Efika ocasionally fail to reset and they use different codec chips. --- Jon Smirl (5): Fabric bindings for STAC9766 on the Efika Support for AC97 on Phytec pmc030 base board. AC97 driver for mpc5200 Main rewite of the mpc5200 audio DMA code The macro spin_event_timeout() takes a condition and timeout value arch/powerpc/include/asm/delay.h | 33 +++ sound/soc/fsl/Kconfig | 27 ++ sound/soc/fsl/Makefile | 5 sound/soc/fsl/efika-audio-fabric.c | 90 +++++++ sound/soc/fsl/mpc5200_dma.c | 442 ++++++++++++++++++++++------------- sound/soc/fsl/mpc5200_dma.h | 43 ++- sound/soc/fsl/mpc5200_psc_ac97.c | 331 ++++++++++++++++++++++++++ sound/soc/fsl/mpc5200_psc_ac97.h | 15 + sound/soc/fsl/mpc5200_psc_i2s.c | 247 +++----------------- sound/soc/fsl/mpc5200_psc_i2s.h | 12 + sound/soc/fsl/pcm030-audio-fabric.c | 90 +++++++ 11 files changed, 946 insertions(+), 389 deletions(-) create mode 100644 sound/soc/fsl/efika-audio-fabric.c create mode 100644 sound/soc/fsl/mpc5200_psc_ac97.c create mode 100644 sound/soc/fsl/mpc5200_psc_ac97.h create mode 100644 sound/soc/fsl/mpc5200_psc_i2s.h create mode 100644 sound/soc/fsl/pcm030-audio-fabric.c -- Jon Smirl jonsmirl(a)gmail.com

7 24

[alsa-devel] Fixes in intel8x0.c
by Pavel Hofman 26 May '09

26 May '09

Hi, while trying to dive into complexities of intel8x0.c I found the following: static struct snd_pci_quirk intel8x0_clock_list[] __devinitdata = { SND_PCI_QUIRK(0x0e11, 0x008a, "AD1885", 41000), SND_PCI_QUIRK(0x1028, 0x00be, "AD1885", 44100), ..... Is it really supposed to be 41000, instead of 44100? In static int snd_intel8x0_pcm_open(struct snd_pcm_substream *substream, struct ichdev *ichdev) ... runtime->hw.rates = ichdev->pcm->rates; The pcm field in ichdev is snd_ac97, while the rates field in snd_ac97 is defined unsigned int rates[6]; /* see AC97_RATES_* defines */ I guess this way always rates[0] from the list is taken, unlike e.g. in via82xx.c: runtime->hw.rates = chip->ac97->rates[AC97_RATES_SPDIF]; It seems a bug to me, though I may be wrong of course. Thanks and regards, Pavel

2 5

[alsa-devel] period_size and .asoundrc
by Canella Matteo 26 May '09

26 May '09

Hi everybody, I'm writing a little software that play a tone on a pcm device. In the hw param initialization I'm hardcoding the "periods" and "period_size" values: unsigned int periods = 4; if (snd_pcm_hw_params_set_periods_near(buzzer_device.pcm_handle, buzzer_device.hwparams, &periods, 0) < 0) { fprintf(stderr, "Error setting periods.\n"); return 1; } ///* set the period time */ period_size = 8192; err = snd_pcm_hw_params_set_period_size_near(buzzer_device.pcm_handle, buzzer_device.hwparams, &period_size, 0); if (err < 0) { printf("Unable to get period size for playback: %s\n", snd_strerror(err)); return err; } I'd like to read this parameter form the .asoundrc file, so I'm wondering if there were API that does this task. Thanks Matteo Canella

2 1

[alsa-devel] 2.6.30: xruns caused by "ALSA: pcm - Safer boundary checks"
by Chuck Ebbert 26 May '09

26 May '09

Bug report: https://bugzilla.redhat.com/show_bug.cgi?id=498858 To reproduce, pause a video in mplayer and then hit play: ALSA sound/core/pcm_lib.c:263: hda_codec: hw_ptr skipping! [Q] (pos=11263, delta=17400, period=1024, jdelta=21/362/0) ALSA sound/core/pcm_lib.c:337: hda_codec: hw_ptr skipping! (pos=11730, delta=1490, period=1024, jdelta=10/31) ALSA sound/core/pcm_lib.c:337: hda_codec: hw_ptr skipping! (pos=11734, delta=1494, period=1024, jdelta=10/31) ALSA sound/core/pcm_lib.c:337: hda_codec: hw_ptr skipping! (pos=11734, delta=1494, period=1024, jdelta=10/31) ALSA sound/core/pcm_lib.c:337: hda_codec: hw_ptr skipping! (pos=11735, delta=1495, period=1024, jdelta=10/31) ALSA sound/core/pcm_lib.c:263: hda_codec: hw_ptr skipping! [Q] (pos=12287, delta=2047, period=1024, jdelta=21/42/0) ALSA sound/core/pcm_lib.c:337: hda_codec: hw_ptr skipping! (pos=12449, delta=2209, period=1024, jdelta=4/46)

5 13

[alsa-devel] spdif/iec958 outputs at VT1708S not recognized
by Sentinel 26 May '09

26 May '09

I tried using the snapshot because I was having the same problem as Peter was. No spdif out on my vt1708s. Unfortunately for me my build didn't go quite as well, for some reason I had 2 undefined which make the snd.ko fail to load. Is there something that I'm missing? I am running slamd64 distro current, with the latest kernel along with the alsa kernel patch "2.6.29.4-rt15". Please help. Building modules, stage 2. MODPOST 131 modules WARNING: "register_sound_special_device" [/usr/src/alsa-driver/acore/snd.ko] undefined! WARNING: "unregister_sound_special" [/usr/src/alsa-driver/acore/snd.ko] undefined! make[1]: Leaving directory `/usr/src/linux-2.6.29.4' utils/link-modules /usr/src/alsa-driver

1 0

Re: [alsa-devel] Help on writing an ALSA ASoC Driver for WM8985
by Leung Chi Tat 26 May '09

26 May '09

Mark, I got it. Once we set those volume update bits in wm8990_init(), those bits in the wm8985 register cache array, wm8985_reg[], will then be set too. So, whenever we write a new value to a volume register, wm8985_write() will then write the new value to the volume register and update the corresponding volume update bit also. This is the trick. A Great Idea! Thank you so much! Chitat On Mon, May 25, 2009 at 08:47:31PM +0800, Leung Chi Tat wrote: > I'm right now studying the driver code for wm8980 codec (from the main > trunk of linux-2.6-asoc) as it seems to be more close to wm8985. I > can't find any code for triggering those volume update bits after > modified those volume registers. But, the wm8980 datasheet states > that we have to do so to make those volume updates properly. Is there > some black magic in the code? The normal approach for volume update bits is to set them when initialising the CODEC at startup - this is what the wm8990 driver is doing when it writes to the volume registers in wm8990_init(). This means that any further register writes which only change the volume field in the registers will also have the volume update bit set.

1 0

[alsa-devel] Question about snd_dma_buffer bytes field
by Troy Kisky 25 May '09

25 May '09

Does (substream->dma_buffer.bytes) need to equal (snd_pcm_lib_period_bytes(substream) * runtime->periods) ? When this is not true, it seems like the buffer is not being filled correctly. for testing, this works .buffer_bytes_max = 16 * 7 * 512, .period_bytes_min = 32, .period_bytes_max = 7 * 512, /* This is size of ping + pong buffer*/ and this doesn't. .buffer_bytes_max = 16 * 7 * 512 + 512, .period_bytes_min = 32, .period_bytes_max = 7 * 512, /* This is size of ping + pong buffer*/ When playing back a sine wave, I can hear breaks. Thanks Troy

2 2

[alsa-devel] [snd-ctxfi] Test EMU20K2
by Sylvain Loulergue 25 May '09

25 May '09

Hi, Modules snd-ctxfi works fine for me (http://www.alsa-project.org/db/?f=e90356f82f257f499e8028d8a28c98775fd765e7). If you need some specific test just say it. thanks for this devel

1 0

[alsa-devel] Alsamixer isn't working properly with HDA VIA VT82xx with Realtek ALC888 Codec
by Stephan Jänecke 25 May '09

25 May '09

Dear developers, alsamixer doesn't work on my fedora machine. When I type in 'alsamixer -c 0', I get "hda_codec: num-steps=0 for NID=0xf (ctl=Side Playback Volume)" "alsamixer: function snd_mixer_load failed: Invalid argument" Although Pulseaudio and OSS Mixers seem to be present, I don't get any sound. Please have a look at http://www.alsa- project.org/db/?f=15c9f665eb141dee755a533d804456e81442f270 or check the attachment. I hope you can help me solving my problem. Regards, Stephan Jänecke PS: I had the same mixer problem with Mandriva 2009.0 before I installed Fedora 10 to check whether it's an distribution specific bug. Whereas alsamixer didn't work properly as well, I could enjoy working sound. -- Powered by openSUSE 11.1 and KMail 1.10.3

2 5