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

[alsa-devel] 2.6.21: known regressions with patches (for -stable team)
by Michal Piotrowski 02 May '07

02 May '07

Hi all, Here is a list of known regressions with patches available. Feel free to add new regressions/remove fixed etc. http://kernelnewbies.org/known_regressions Subject : 2.6.21: longhaul freq-scaling broken References : http://lkml.org/lkml/2007/5/1/260 Submitter : Jan Kiszka <jan.kiszka(a)web.de> Patch : http://git.kernel.org/?p=linux/kernel/git/davej/cpufreq.git;a=commitdiff_pl… Status : patch available Subject : Kernel hang at "kernel: switched to high resolution mode on cpu 0" when either/both of CONFIG_NO_HZ, CONFIG_HIGH_RES_TIMERS is used References : http://lkml.org/lkml/2007/4/30/464 Submitter : Mark Lord <lkml(a)rtr.ca> Handled-By : Daniel Walker <dwalker(a)mvista.com> Thomas Gleixner <tglx(a)linutronix.de> Patch : http://lkml.org/lkml/2007/4/13/190 Status : patch was suggested Subject : ACPI related kernel panic References : http://lkml.org/lkml/2007/4/30/193 http://bugzilla.kernel.org/show_bug.cgi?id=8385 Submitter : Sebastian Kemper <sebastian_ml(a)gmx.net> Patches : http://bugzilla.kernel.org/attachment.cgi?id=11331&action=view http://bugzilla.kernel.org/attachment.cgi?id=11332&action=view Status : patches was suggested Subject : sis900 oops in 2.6.21.1 after bringing up the network References : http://lkml.org/lkml/2007/4/29/138 http://lkml.org/lkml/2007/4/29/151 Patch : http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdi… Submitter : Brett Ryland <nappers(a)gmail.com> Status : patch available Subject : reiserfs -- circular locking References : http://lkml.org/lkml/2007/4/26/648 Submitter : David Brownell < david-b(a)pacbell.net > Handled-By : Jeff Mahoney < jeffm(a)suse.com > Patch : http://lkml.org/lkml/2007/4/27/332 Status : patch available Subject : Oops when changing USB DVB-T adapter References : http://lkml.org/lkml/2007/3/9/212 http://lkml.org/lkml/2007/4/5/154 Submitter : CIJOML <cijoml(a)volny.cz> Handled-By : Markus Rechberger < markus.rechberger(a)amd.com > Status : patches available Subject : snd_intel8x0: divide error: 0000 References : http://lkml.org/lkml/2007/3/5/252 Submitter : Michal Piotrowski < michal.k.k.piotrowski(a)gmail.com > Handled-By : Takashi Iwai < tiwai(a)suse.de > Patch : http://lkml.org/lkml/2007/4/20/117 Status : patch available Subject : qla2xxx driver no longer works References : http://lkml.org/lkml/2007/4/16/49 http://lkml.org/lkml/2007/4/20/224 Submitter : David Miller < davem(a)davemloft.net > Robert Peterson < rpeterso(a)redhat.com > Handled-By : David Miller < davem(a)davemloft.net > Patch : http://lkml.org/lkml/2007/4/16/234 Status : patch was suggested Regards, Michal -- Michal K. K. Piotrowski Kernel Monkeys (http://kernel.wikidot.com/start)

1 0

[alsa-devel] [PATCH] snd-usb-audio: explicitly match Logitech QuickCam
by Daniel Drake 02 May '07

02 May '07

Commit 93c8bf45e083b89dffe3a708363c15c1b220c723 modified the USB device matching behaviour to ignore interface class matches if the device class is vendor-specific. This patch adds an explicit ID match for the Logitech QuickCam Messenger, which has a vendor specific device class (but standards-compliant audio interfaces). This fixes a 2.6.20 regression where the audio component of this device was no longer usable. http://bugs.gentoo.org/show_bug.cgi?id=175715 https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/93822 https://bugtrack.alsa-project.org/alsa-bug/view.php?id=3040 Based on a patch from sergiom Signed-off-by: Daniel Drake <dsd(a)gentoo.org> Index: linux/sound/usb/usbquirks.h =================================================================== --- linux.orig/sound/usb/usbquirks.h +++ linux/sound/usb/usbquirks.h @@ -40,6 +40,21 @@ .bInterfaceClass = USB_CLASS_VENDOR_SPEC /* + * Logitech QuickCam: bDeviceClass is vendor-specific, so generic interface + * class matches do not take effect without an explicit ID match. + */ + +{ + .match_flags = USB_DEVICE_ID_MATCH_DEVICE | + USB_DEVICE_ID_MATCH_INT_CLASS | + USB_DEVICE_ID_MATCH_INT_SUBCLASS, + .idVendor = 0x046d, + .idProduct = 0x08f0, + .bInterfaceClass = USB_CLASS_AUDIO, + .bInterfaceSubClass = USB_SUBCLASS_AUDIO_CONTROL +}, + +/* * Yamaha devices */

3 2

[alsa-devel] ALC260 patch for Packard Bell Easy Note v7900
by Andrea Gozzi 02 May '07

02 May '07

Please see if you can accept this patch that fixes sound/headphones/mic on Packard Bell EN v7900 notebook (ALC260 chipset). The code is not mine, I diff'ed using pshou's (https://bugtrack.alsa-project.org/alsa-bug/view.php?id=2189) but since it works perfectly it would be nice to see it in the next alsa release. Andrea

2 1

[alsa-devel] [ALSA][hda-codec] fix-connexant-headphone-mute
by Andrei Popa 02 May '07

02 May '07

Hi, The sound works ok with the built-in speakers on my Fujitsu laptop(amilo pro v3205). But if I plug in headphones in the audio out jack there is no sound in the headphones. With kernel 2.6.20 it worked ok. With 2.6.21 it doesn't. This BUG is reported in ALSA bugtracking system with ID 0003039. Patch that fixes this bug: diff --git a/sound/pci/hda/patch_conexant.c b/sound/pci/hda/patch_conexant.c index 46e93c6..5edd330 100644 --- a/sound/pci/hda/patch_conexant.c +++ b/sound/pci/hda/patch_conexant.c @@ -636,7 +636,7 @@ static void cxt5045_hp_automute(struct hda_codec *codec) bits = (spec->hp_present || !spec->cur_eapd) ? 0x80 : 0; snd_hda_codec_amp_update(codec, 0x10, 0, HDA_OUTPUT, 0, 0x80, bits); - snd_hda_codec_amp_update(codec, 0x10, 1, HDA_OUTPUT, 0, 0x80, bits); + snd_hda_codec_amp_update(codec, 0x10, 1, HDA_OUTPUT, 0, 0, bits); } /* unsolicited event for HP jack sensing */ @@ -988,10 +988,10 @@ static void cxt5047_hp_automute(struct hda_codec *codec) bits = (spec->hp_present || !spec->cur_eapd) ? 0x80 : 0; snd_hda_codec_amp_update(codec, 0x1d, 0, HDA_OUTPUT, 0, 0x80, bits); - snd_hda_codec_amp_update(codec, 0x1d, 1, HDA_OUTPUT, 0, 0x80, bits); + snd_hda_codec_amp_update(codec, 0x1d, 1, HDA_OUTPUT, 0, 0, bits); /* Mute/Unmute PCM 2 for good measure - some systems need this */ snd_hda_codec_amp_update(codec, 0x1c, 0, HDA_OUTPUT, 0, 0x80, bits); - snd_hda_codec_amp_update(codec, 0x1c, 1, HDA_OUTPUT, 0, 0x80, bits); + snd_hda_codec_amp_update(codec, 0x1c, 1, HDA_OUTPUT, 0, 0, bits); } /* toggle input of built-in and mic jack appropriately */

2 2

Re: [alsa-devel] Boot failure with 2.6.21 with snd-maestro3
by Giridhar Pemmasani 02 May '07

02 May '07

--- Adrian Bunk <bunk(a)stusta.de> wrote: > On Sun, Apr 29, 2007 at 09:55:18AM -0700, Giridhar Pemmasani wrote: > > When snd-maestro3 (ESS Maestro 3 driver) is enabled, kernel 2.6.21 fails > to > > boot - it seems to stop at various points depending on what other modules > are > > enabled. Disabling snd-maestro3 fixes all issues. Moreover, with > everything > > else being same, using maestro3.c from 2.6.20 kernel and using it in > 2.6.21 > > kernel also works - i.e., system boots fine. I will try to isolate the > issue > > and follow up. > > There were only the two attached patches between 2.6.20 and 2.6.21 to > this driver: > - maestro3: add request_firmware() > - maestro3 - Use quirk list helper function > > 2.6.21 + 2.6.20 maestro3.c works for you. > > Does 2.6.21 + 2.6.20 maestro3.c + patch-maestro3-1 work? 2.6.21 with 2.6.20's maestro3.c with patch-maestro3-1 exhibited the same issue. However, I identified the cause: maestro3 driver in 2.6.21 (even just patch-maestro3-1) tries to load firmware file from user space. But each time request_firmware is called it takes about 1 minute to timeout (because I don't have the firmware installed?). If I let the system take its time, even with maestro3.c from 2.6.21, it boots after timing out twice. So after about 2 minutes of no activity, system does boot. Following are trace messages I added to identify the issue: [ 17.004000] input: TPPS/2 IBM TrackPoint as /class/input/input5 [ 70.904000] sound/pci/maestro3.c (snd_m3_create:2763): -2 [ 70.920000] sound/pci/maestro3.c (snd_m3_create:2774): -2 [ 130.940000] sound/pci/maestro3.c (snd_m3_create:2777): -2 [ 130.956000] sound/pci/maestro3.c (snd_m3_create:2788): -2 [ 130.972000] sound/pci/maestro3.c (snd_m3_create:2794): 0 [ 130.992000] sound/pci/maestro3.c (snd_m3_create:2797): 0 [ 131.012000] sound/pci/maestro3.c (snd_m3_create:2802): 0 [ 131.044000] sound/pci/maestro3.c (snd_m3_create:2804): 0 [ 131.580000] sound/pci/maestro3.c (snd_m3_create:2807): 0 [ 131.596000] sound/pci/maestro3.c (snd_m3_create:2810): 0 [ 131.612000] sound/pci/maestro3.c (snd_m3_create:2814): 0 [ 131.628000] sound/pci/maestro3.c (snd_m3_create:2821): 0 [ 132.364000] device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised: dm-d evel(a)redhat.com Giri __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

2 1

[alsa-devel] Audio DMA buffer layout and setup
by Markus Korber 02 May '07

02 May '07

Hi, I'm working with a custom sound chip with its own DMA hardware. The figure shows how the I2S DMA expects data to be prepared: IRQ1 +----------------+ | page_3 (right) |\ +----------------+ > double buffer 1 | page_2 (left) |/ IRQ0 +----------------+ | page_1 (right) |\ +----------------+ > double buffer 0 | page_0 (left) |/ +----------------+ The hardware has 2 double buffers, each containing left and right sample regions, i.e. it alternately transmits samples from page_0 and page_1, i.e. double buffer 0, then generates an interrupt and starts transmitting page_2 and page_3. After that another interrupt is generated and the process begins again with double buffer 0. So my question is, how to tell ALSA about this memory layout? Is it possible to operate in MMAP mode with SNDRV_PCM_INFO_NONINTERLEAVED? But then, how to tell the application that it should either fill double buffer 0 or 1? Or should I use RW mode? Or something else? Furthermore, since the hardware doesn't provide a 'current' DMA pointer containing the DMA address being transmitted at the moment (I only have interrupts generated after each double buffer has been transmitted), what should the pcm_pointer() callback return? (I guess it should return 0 when called before IRQ0 and sizeof(double buffer 0) between IRQ0 and IRQ1?) Best regards, Markus Korber

1 0

[alsa-devel] driver mixer control questions
by Tim Harvey 02 May '07

02 May '07

I'm troubleshooting an issue with an ALSA driver I wrote for a very unique hardware platform. In this case I have an audio codec which only has a usable 'line-in' capture source. Currently the only mixer control I've created is a 'Master Playback Volume'. Do I need to create some kind of control for 'line-in'? I'm unclear how to 'register' capture inputs so that they will be returned by the OSS mixer emulation's ioctl SOUND_MIXER_READ_RECMASK. Currently that ioctl returns 0 for my mixer device. Also, is a control 'switch' such as 'Master Playback Switch' simply a mute control or is it intended to be any type of control which could have enumerated values? Thanks, Tim

1 0

Re: [alsa-devel] Support for SAM9407?
by Ash Willis 02 May '07

02 May '07

Thanks for your detailed response. That chip definitely does seem like a beast that I really don't want to tame... > > How about a Media Vision Pro Audio Spectrum 16? Those can still be found > relatively easily and it's one the cards for which an OSS/Free driver is > still kept in the tree. I have a pair of those as well so I'll happily test > if you want to write a driver for it... > Yeah, we have a winner. I just ordered one. I'm busy right now but I will get this started in 4 weeks. Thanks for the offer of testing. I'll hunt you down when I have something to show you :) Ash =

1 0

[alsa-devel] porter wanted: AMD Geode SCx200 driver OSS to ALSA
by Martin-Éric Racine 02 May '07

02 May '07

Greetings, I work for a company that develops hardware using the AMD Geode chipset. While our current product line is based on the Geode LX model (which is very well supported in ALSA), our legacy products are based on the earlier Geode SC1200 and SC2200, for which no ALSA support exists. However, AMD has OSS driver source code available at: http://www.amd.com/us-en/ConnectivitySolutions/TechnicalResources/0,,50_233… We basically need this ported to an ALSA snd-scx200 module to replace it. (Would now also be a good time to ask for snd-sc5535audio to be renamed snd-sc5535 for consistence with other driver names?) We could provide a sample SC2200-based unit to whoever volunteers for porting AMD's old OSS code to ALSA, Please contact me for details. The resulting code will be directly submitted to the ALSA project for inclusion in the mainstream kernel, to make sure that everyone can benefit from it. Best Regards, -- Martin-Éric Racine http://q-funk.iki.fi

1 1

Re: [alsa-devel] Endiannes and alsa (in an embedded device)
by Ciaccia 01 May '07

01 May '07

Forget about that, it took 4 hours but I understood why it was not working... Since I'm working with 24bit resolution (and not 16 as I usually do), the samples were to little... Now I replaced the sin line with: sample = (int)(4000000.0f * sin((float)i * 2.0f * M_PI / (512.0f / 50.0f))); and it's working fine. I really thought it was too strange to be true... Sorry for the spam :-| Andrea ----- Original Message ---- From: Ciaccia <ciacciax(a)yahoo.com> To: alsa-devel(a)alsa-project.org Sent: Tuesday, May 1, 2007 8:49:18 PM Subject: [alsa-devel] Endiannes and alsa (in an embedded device) Dear all, I have a question that really puzzles me, I wonder if someone can explain to me what I'm doing wrong... :-| I have programmed an ALSA driver for an embedded device, everything works fine and all the application use my driver without any glitches. The snd_pcm_hardware for this device is defined as following: static const struct snd_pcm_hardware ep93xx_pcm_hardware = { .info= SNDRV_PCM_INFO_MMAP | SNDRV_PCM_INFO_MMAP_VALID | SNDRV_PCM_INFO_INTERLEAVED | SNDRV_PCM_INFO_BLOCK_TRANSFER, .rates = SNDRV_PCM_RATE_8000_48000, .rate_min = 8000, .rate_max = 48000, .channels_min = 2, .channels_max = 2, .formats = SNDRV_PCM_FMTBIT_S24_LE, .buffer_bytes_max = 131072, .period_bytes_min = 512, .period_bytes_max = 32768, .periods_min = 1, .periods_max = MAX_PERIODS, .fifo_size = 32, }; Then I tried to program a test application that uses the hardware device directly (without using alsa-lib to convert the format and so on). I open the device as following: if ((err = snd_pcm_open (&playback_handle, "hw:0,0", SND_PCM_STREAM_PLAYBACK, 0)) < 0) { Everything works fine until I try to write data to the stream. I tried both SND_PCM_ACCESS_RW_INTERLEAVED and SND_PCM_ACCESS_MMAP_INTERLEAVED, but I always have the following problem. When I want to write data to the stream, I have to "reverse" the byte order, otherwise I hear noise on the speaker. The system I am working on is little-endian (it has cirrus ep93xx arm core), so I assume I could write data directly to the buffer. Here is what I have to do: // fill the buffer for (i = 0; i < 512; i++) { int sample = (int)(20000.0f * sin((float)i * 2.0f * M_PI / 512.0f)); int reversed; char *src = (char *)(&sample); char *dst = (char *)(&reversed); dst[0] = src[3]; dst[1] = src[2]; dst[2] = src[1]; dst[3] = src[0]; *(buffer++) = reversed; *(buffer++) = reversed; } It this normal? I thought that since the system is little-endian and the format of the driver is S24_LE, I could copy the data directly to the stream (either using snd_pcm_writei or snd_pcm_mmap_begin). I think the driver is ok, since all the applications run with no problem at all. Can someone explain to me how/why the applications such as aplay/arecord work ok? Every help is greatly appreciated Thanks in advance Andrea __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com _______________________________________________ Alsa-devel mailing list Alsa-devel(a)alsa-project.org http://mailman.alsa-project.org/mailman/listinfo/alsa-devel __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

1 0