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

[alsa-devel] Getting Started on Alsa
by Chris Schumann 06 May '07

06 May '07

Hello, I'd like to take action on bug #305, since it's my own itch. I've done very low-level programming, but not on Linux device drivers. I'm very familiar with command line development tools. Is there any documentation on how to get started doing bugfixes or development for Alsa, or do I just look for source and start hacking? Thanks, Chrs

1 0

[alsa-devel] [PATCH] hda_codec: restore control element values during resume
by Daniel Drake 06 May '07

06 May '07

After resume from suspend-to-RAM, there is no sound output from my Intel HDA hardware: 00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 01) Found in a Dell Inspiron 640m, SigmaTel STAC9200 chip. After resuming, sound immediately returns when you adjust the volume one notch in either direction. I reported this on the ALSA bug tracker (#0002989). Further investigation shows that the AC_VERB_SET_AMP_GAIN_MUTE verb is not being executed during resume, which seems strange. Does other hardware really store this value during a suspend/resume cycle? Or maybe the volume is generally controlled through other means on other setups? I'm not entirely sure what the difference is between kcontrol and kcontrol_new structures, but I note that there is already some code to restore the values for kcontrol_new elements. I solved the issue with the following patch. Is it correct? Signed-off-by: Daniel Drake <dsd(a)gentoo.org> Index: linux-2.6/sound/pci/hda/hda_codec.c =================================================================== --- linux-2.6.orig/sound/pci/hda/hda_codec.c +++ linux-2.6/sound/pci/hda/hda_codec.c @@ -2248,15 +2248,39 @@ EXPORT_SYMBOL(snd_hda_suspend); int snd_hda_resume(struct hda_bus *bus) { struct list_head *p; + struct snd_ctl_elem_value *val = kmalloc(sizeof(*val), GFP_KERNEL); + + if (!val) + return -ENOMEM; list_for_each(p, &bus->codec_list) { struct hda_codec *codec = list_entry(p, struct hda_codec, list); + struct snd_kcontrol *kctl; + + codec->in_resume = 1; + hda_set_power_state(codec, codec->afg ? codec->afg : codec->mfg, AC_PWRST_D0); + + + list_for_each_entry(kctl, &bus->card->controls, list) { + memset(val, 0, sizeof(*val)); + val->id = kctl->id; + /* Assume that get callback reads only from cache, + * not accessing the real hardware + */ + if (snd_ctl_elem_read(bus->card, val) < 0) + continue; + snd_ctl_elem_write(bus->card, NULL, val); + } + if (codec->patch_ops.resume) codec->patch_ops.resume(codec); + + codec->in_resume = 0; } + kfree(val); return 0; }

2 4

[alsa-devel] New Soundcard Matrix
by Jaroslav Kysela 05 May '07

05 May '07

Hello all, I moved the contents of matrix from XML files to Wiki - see http://bugtrack.alsa-project.org/main/index.php/Matrix:Main Please, no more updates to old matrix now. I left the information structure (we can update it later): Vendor -> Device -> ALSA Module If any volunteers are watching this list, we have many "wanted" pages now: http://bugtrack.alsa-project.org/main/index.php/Special:Wantedpages Example page for Matrix:Tag-* : http://bugtrack.alsa-project.org/main/index.php?title=Matrix:Tag-PCI&action… Example page for Matrix:Module-* : http://bugtrack.alsa-project.org/main/index.php?title=Matrix:Module-ali5451… Jaroslav ----- Jaroslav Kysela <perex(a)suse.cz> Linux Kernel Sound Maintainer ALSA Project, SUSE Labs

1 0

Re: [alsa-devel] Wiki Site
by Jaroslav Kysela 05 May '07

05 May '07

On Fri, 4 May 2007, cameron porter wrote: > Greetings, > > I noticed the notice on your front page needing people to help transfer the > site contents over to your wiki that you set up. I did a little bit of work, > and managed to get a navigation, downloads page, application page, and some > other links. Your work is greatly appreciated here. > I would be glad to continue, if you think I am doing things right. The next > thing I had planned to make some changes to was the documentation section, > add a changes section, add a structure whereby you have an article for each > package, and then the folder for that package contains all the different > versions that have been or will be released. Please give me any thoughts on > any of these, and tell me if you think they are a good idea, and whether I > should continue or not. We need to move the contents at first, but I agree that a good page structure should be created during this process. Please, go ahead - the nice thing on wiki is that we can rearrange information later (if we find a problem with the structure). I just started to move probably most problematic part - soundcard matrix to wiki. Thanks, Jaroslav ----- Jaroslav Kysela <perex(a)suse.cz> Linux Kernel Sound Maintainer ALSA Project, SUSE Labs

1 0

[alsa-devel] Call for Explanation of ALSA Config Behavior
by Jeff Rush 05 May '07

05 May '07

I'm trying to get ALSA to support all the little features of my laptop, which is based on the Intel HDA chipset with the Realtek codec. I'm also playing with the softvol plug to add a volume controls over certain virtual devices. A few questions I can't figure out: 1. Isn't it the standard convention that there be a control named "Master" that adjusts the overall volume of a device? So why does the Intel HDA ALSA driver define one named "Headphone" that does the same thing instead of following that convention? Is there some reason, or perhaps a difference in opinion within the ALSA community on the naming of controls? Shouldn't every ALSA driver define a "Master" control? 2. When I add a control using the softvol plugin, the mixer GUI shows it in both the playback and the capture set of controls. Why and how can I tag a control to belong to only one set or the other? Being a volume control it seems it should only be in the playback collection. 3. Once I add such a control, it -never- goes away. What I mean is that if I rename it, or remove it, and restart ALSA or even restart the entire computer, the old name for the control always shows up in the mixer GUI. I've grepped *all* of /etc, looking in the /etc/asound.conf, /etc/asound.state and ~/.asoundrc files but the old name isn't anywhere -- where is it coming from? Thanks very much for any help you can provide, For years I've just tried to "use" ALSA but now I'm trying to actually understand its subtle nuances. -Jeff

2 1

[alsa-devel] DMix period_size should always be half of buffer size?
by Prabhu Sivaraja 04 May '07

04 May '07

This is a followup to my earlier question about dmix not being able to mix small files. I investigated it more and here is what I found. Again background info. I have a 64KB as kernel buffer and a 64KB circular buffer for my device. In a poll thread I copy the data obtained from ALSA lib from the kernel buffer to my device circular buffer by keeping track of appl_ptr and hw_ptr(dmix only). Everything was working fine except when I was trying to mix files smaller than 64KB(my buffer size), the small file was not getting mixed through the dmix plugin. Anything over 64KB was getting mixed just fine. So I set about reducing my period size from 32KB to 4KB while maintaining my buffer size at 64KB. When I tried to do this my hw_ptr never gets incremented from 0. Hence my driver is stuck in a loop waiting for bytes to copy. This is only observed when I am using dmix plugin and NOT when using hw or plughw. When my period size is half the size of my buffer everything works fine with dmix (I verified this by reducing my buffer size to 8KB and making my period size 4KB. hw_ptr gets incremented then but I get buffer problems). It seems like dmix is forcing me to keep my period size half the size of my buffer. hw and plughw devices do not seem to do that. Is this a limitation of dmix. Could anyone comment on the dmix limitation that I am experiencing. Thanks a lot of all your help. Prabhu.

2 2

[alsa-devel] Aureon 7.1 Firewire supported by ALSA ?
by Michael Gerdau 04 May '07

04 May '07

Hi list, looking for an external (USB or Firewire) interface to record at least a single stereo 44.1kHz/24bit S/P-DIF signal I've come across the Aureon 7.1 Firewire but have not been able to find out whether it is already supported by ALSA. Another option would be the Aureon 5.1 USB MKII but according to the specs it is 16bit only. However when feeding S/P-DIF with a stereo 44.1kHz/24bit would the driver be recognize that and give me that signal unaltered or would it be trimmed to 16bit ? [Or is my understanding of S/P-DIF just plain wrong and such a signal would not go through the box at all ?] Any advice welcome, best, Michael -- Technosis GmbH, Geschäftsführer: Michael Gerdau, Tobias Dittmar Sitz Hamburg; HRB 89145 Amtsgericht Hamburg Vote against SPAM - see http://www.politik-digital.de/spam/ Michael Gerdau email: mgd(a)technosis.de GPG-keys available on request or at public keyserver

2 2

[alsa-devel] [PATCH] multi-channel playback and capture fixes for stac92xx codecs
by Steve Longerbeam 04 May '07

04 May '07

Hi, I have picked up where Matt Porter left off on stac92xx HDA codec devel. I've been working with the 9200, 9221, 9202, 9250, and 9205 codecs, and I found some problems with muti-channel playback on 922x and 9205. Also a problem with input mux selection for codecs with more than one configured input pin. I've tested the attached patch on all the above listed codecs. Steve

2 3

[alsa-devel] [PATCH] snd-usb-audio: Add another QuickCam ID
by Daniel Drake 04 May '07

04 May '07

This adds another Logitech QuickCam USB ID. These devices have vendor-specific device class values, but standards-compliant audio interfaces. 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 @@ -53,6 +53,16 @@ .bInterfaceClass = USB_CLASS_AUDIO, .bInterfaceSubClass = USB_SUBCLASS_AUDIO_CONTROL }, +{ + .match_flags = USB_DEVICE_ID_MATCH_DEVICE | + USB_DEVICE_ID_MATCH_INT_CLASS | + USB_DEVICE_ID_MATCH_INT_SUBCLASS, + .idVendor = 0x046d, + .idProduct = 0x08f6, + .bInterfaceClass = USB_CLASS_AUDIO, + .bInterfaceSubClass = USB_SUBCLASS_AUDIO_CONTROL +}, + /* * Yamaha devices

1 0

[alsa-devel] support for Medion laptops
by albox＠free.fr 04 May '07

04 May '07

Hi, I installed Ubuntu Feisty a few days ago and my sound card driver doesn't work anymore. It was working perfectly before updating to Feisty but I'm not sure the problem comes from the update since I was not using the last ALSA version but an older one patched with a patch released by Tobin Davis a few months ago (something else could have been changed in the ALSA source code since then) : --- alsa-driver/alsa-kernel/pci/hda/patch_realtek.c.orig 2006-10-08 10:58:28.000000000 -0700 +++ alsa-driver/alsa-kernel/pci/hda/patch_realtek.c 2006-10-09 10:50:03.000000000 -0700 @@ -112,6 +112,7 @@ ALC883_6ST_DIG, ALC888_DEMO_BOARD, ALC883_ACER, + ALC883_MEDION, ALC883_AUTO, ALC883_MODEL_LAST, }; @@ -5080,6 +5081,8 @@ .config = ALC883_ACER }, { .pci_subvendor = 0x1025, .pci_subdevice = 0x009f, .config = ALC883_ACER }, + { .pci_subvendor = 0x161f, .pci_subdevice = 0xd82b, + .modelname = "medion", .config = ALC883_MEDION } { .modelname = "auto", .config = ALC883_AUTO }, {} }; @@ -5167,6 +5170,20 @@ .channel_mode = alc883_3ST_2ch_modes, .input_mux = &alc883_capture_source, }, + [ALC883_MEDION] = { + .mixers = { alc883_base_mixer, + alc883_chmode_mixer }, + .init_verbs = { alc883_init_verbs, + alc882_eapd_verbs }, + .num_dacs = ARRAY_SIZE(alc883_dac_nids), + .dac_nids = alc883_dac_nids, + .num_adc_nids = ARRAY_SIZE(alc883_adc_nids), + .adc_nids = alc883_adc_nids, + .num_channel_mode = ARRAY_SIZE(alc883_sixstack_modes), + .channel_mode = alc883_sixstack_modes, + .input_mux = &alc883_capture_source, + } + }; You can find some parts of the emails about this subject on this web page : http://www.spinics.net/lists/alsa-devel/msg04396.html The driver (Developement release 1.0.14rc3) can detect my sound card but I can't figure out what's wrong. Can anybody help me ? $ dmesg | grep alsa [ 20.468000] ALSA /home/alboot/Sources/alsa/alsa-driver-1.0.14rc3/pci/hda/../../alsa-kernel/pci/hda/hda_intel.c:696: codec_mask = 0x3 [ 20.648000] ALSA /home/alboot/Sources/alsa/alsa-driver-1.0.14rc3/pci/hda/hda_codec.c:1768: hda_codec: model 'medion' is selected for config 161f:2054 (Medion laptop) [ 21.376000] ALSA /home/alboot/Sources/alsa/alsa-driver-1.0.14rc3/pci/hda/../../alsa-kernel/pci/hda/patch_si3054.c:245: si3054: cannot initialize. EXT MID = 0000 [ 21.384000] ALSA /home/alboot/Sources/alsa/alsa-driver-1.0.14rc3/pci/hda/../../alsa-kernel/pci/hda/patch_si3054.c:257: Link Frame Detect(FDT) is not ready (line status: 0000) [ 76.256000] ALSA /home/alboot/Sources/alsa/alsa-driver-1.0.14rc3/pci/hda/../../alsa-kernel/pci/hda/hda_intel.c:1158: azx_pcm_prepare: bufsize=0x10000, fragsize=0x1000, format=0x11 [ 76.256000] ALSA /home/alboot/Sources/alsa/alsa-driver-1.0.14rc3/pci/hda/hda_codec.c:627: hda_codec_setup_stream: NID=0x2, stream=0x5, channel=0, format=0x11 [ 76.264000] ALSA /home/alboot/Sources/alsa/alsa-driver-1.0.14rc3/pci/hda/hda_codec.c:627: hda_codec_setup_stream: NID=0x4, stream=0x5, channel=0, format=0x11 [ 76.272000] ALSA /home/alboot/Sources/alsa/alsa-driver-1.0.14rc3/pci/hda/hda_codec.c:627: hda_codec_setup_stream: NID=0x3, stream=0x5, channel=0, format=0x11 [ 76.280000] ALSA /home/alboot/Sources/alsa/alsa-driver-1.0.14rc3/pci/hda/hda_codec.c:627: hda_codec_setup_stream: NID=0x5, stream=0x5, channel=0, format=0x11 [ 76.292000] ALSA /home/alboot/Sources/alsa/alsa-driver-1.0.14rc3/pci/hda/hda_codec.c:627: hda_codec_setup_stream: NID=0x2, stream=0x0, channel=0, format=0x0 [ 76.300000] ALSA /home/alboot/Sources/alsa/alsa-driver-1.0.14rc3/pci/hda/hda_codec.c:627: hda_codec_setup_stream: NID=0x4, stream=0x0, channel=0, format=0x0 [ 76.308000] ALSA /home/alboot/Sources/alsa/alsa-driver-1.0.14rc3/pci/hda/hda_codec.c:627: hda_codec_setup_stream: NID=0x3, stream=0x0, channel=0, format=0x0 [ 76.320000] ALSA /home/alboot/Sources/alsa/alsa-driver-1.0.14rc3/pci/hda/hda_codec.c:627: hda_codec_setup_stream: NID=0x5, stream=0x0, channel=0, format=0x0 [ 76.332000] ALSA /home/alboot/Sources/alsa/alsa-driver-1.0.14rc3/pci/hda/../../alsa-kernel/pci/hda/hda_intel.c:1158: azx_pcm_prepare: bufsize=0x10000, fragsize=0x1000, format=0x11 [ 76.332000] ALSA /home/alboot/Sources/alsa/alsa-driver-1.0.14rc3/pci/hda/hda_codec.c:627: hda_codec_setup_stream: NID=0x2, stream=0x5, channel=0, format=0x11 [ 76.344000] ALSA /home/alboot/Sources/alsa/alsa-driver-1.0.14rc3/pci/hda/hda_codec.c:627: hda_codec_setup_stream: NID=0x4, stream=0x5, channel=0, format=0x11 [ 76.356000] ALSA /home/alboot/Sources/alsa/alsa-driver-1.0.14rc3/pci/hda/hda_codec.c:627: hda_codec_setup_stream: NID=0x3, stream=0x5, channel=0, format=0x11 [ 76.364000] ALSA /home/alboot/Sources/alsa/alsa-driver-1.0.14rc3/pci/hda/hda_codec.c:627: hda_codec_setup_stream: NID=0x5, stream=0x5, channel=0, format=0x11 [ 76.376000] ALSA /home/alboot/Sources/alsa/alsa-driver-1.0.14rc3/pci/hda/hda_codec.c:627: hda_codec_setup_stream: NID=0x2, stream=0x0, channel=0, format=0x0 [ 76.384000] ALSA /home/alboot/Sources/alsa/alsa-driver-1.0.14rc3/pci/hda/hda_codec.c:627: hda_codec_setup_stream: NID=0x4, stream=0x0, channel=0, format=0x0 [ 76.392000] ALSA /home/alboot/Sources/alsa/alsa-driver-1.0.14rc3/pci/hda/hda_codec.c:627: hda_codec_setup_stream: NID=0x3, stream=0x0, channel=0, format=0x0 [ 76.408000] ALSA /home/alboot/Sources/alsa/alsa-driver-1.0.14rc3/pci/hda/hda_codec.c:627: hda_codec_setup_stream: NID=0x5, stream=0x0, channel=0, format=0x0 [ 76.592000] ALSA /home/alboot/Sources/alsa/alsa-driver-1.0.14rc3/pci/hda/../../alsa-kernel/pci/hda/hda_intel.c:1158: azx_pcm_prepare: bufsize=0x10000, fragsize=0x1000, format=0x11 [ 76.592000] ALSA /home/alboot/Sources/alsa/alsa-driver-1.0.14rc3/pci/hda/hda_codec.c:627: hda_codec_setup_stream: NID=0x2, stream=0x5, channel=0, format=0x11 [ 76.600000] ALSA /home/alboot/Sources/alsa/alsa-driver-1.0.14rc3/pci/hda/hda_codec.c:627: hda_codec_setup_stream: NID=0x4, stream=0x5, channel=0, format=0x11 [ 76.608000] ALSA /home/alboot/Sources/alsa/alsa-driver-1.0.14rc3/pci/hda/hda_codec.c:627: hda_codec_setup_stream: NID=0x3, stream=0x5, channel=0, format=0x11 [ 76.616000] ALSA /home/alboot/Sources/alsa/alsa-driver-1.0.14rc3/pci/hda/hda_codec.c:627: hda_codec_setup_stream: NID=0x5, stream=0x5, channel=0, format=0x11 [ 153.564000] ALSA /home/alboot/Sources/alsa/alsa-driver-1.0.14rc3/pci/hda/hda_codec.c:627: hda_codec_setup_stream: NID=0x2, stream=0x0, channel=0, format=0x0 [ 153.572000] ALSA /home/alboot/Sources/alsa/alsa-driver-1.0.14rc3/pci/hda/hda_codec.c:627: hda_codec_setup_stream: NID=0x4, stream=0x0, channel=0, format=0x0 [ 153.580000] ALSA /home/alboot/Sources/alsa/alsa-driver-1.0.14rc3/pci/hda/hda_codec.c:627: hda_codec_setup_stream: NID=0x3, stream=0x0, channel=0, format=0x0 [ 153.588000] ALSA /home/alboot/Sources/alsa/alsa-driver-1.0.14rc3/pci/hda/hda_codec.c:627: hda_codec_setup_stream: NID=0x5, stream=0x0, channel=0, format=0x0 [ 216.896000] ALSA /home/alboot/Sources/alsa/alsa-driver-1.0.14rc3/pci/hda/../../alsa-kernel/pci/hda/hda_intel.c:1158: azx_pcm_prepare: bufsize=0x10000, fragsize=0x1000, format=0x11 [ 216.896000] ALSA /home/alboot/Sources/alsa/alsa-driver-1.0.14rc3/pci/hda/hda_codec.c:627: hda_codec_setup_stream: NID=0x2, stream=0x5, channel=0, format=0x11 [ 216.904000] ALSA /home/alboot/Sources/alsa/alsa-driver-1.0.14rc3/pci/hda/hda_codec.c:627: hda_codec_setup_stream: NID=0x4, stream=0x5, channel=0, format=0x11 [ 216.912000] ALSA /home/alboot/Sources/alsa/alsa-driver-1.0.14rc3/pci/hda/hda_codec.c:627: hda_codec_setup_stream: NID=0x3, stream=0x5, channel=0, format=0x11 [ 216.920000] ALSA /home/alboot/Sources/alsa/alsa-driver-1.0.14rc3/pci/hda/hda_codec.c:627: hda_codec_setup_stream: NID=0x5, stream=0x5, channel=0, format=0x11 [ 216.932000] ALSA /home/alboot/Sources/alsa/alsa-driver-1.0.14rc3/pci/hda/hda_codec.c:627: hda_codec_setup_stream: NID=0x2, stream=0x0, channel=0, format=0x0 [ 216.940000] ALSA /home/alboot/Sources/alsa/alsa-driver-1.0.14rc3/pci/hda/hda_codec.c:627: hda_codec_setup_stream: NID=0x4, stream=0x0, channel=0, format=0x0 [ 216.948000] ALSA /home/alboot/Sources/alsa/alsa-driver-1.0.14rc3/pci/hda/hda_codec.c:627: hda_codec_setup_stream: NID=0x3, stream=0x0, channel=0, format=0x0 [ 216.956000] ALSA /home/alboot/Sources/alsa/alsa-driver-1.0.14rc3/pci/hda/hda_codec.c:627: hda_codec_setup_stream: NID=0x5, stream=0x0, channel=0, format=0x0 [ 216.972000] ALSA /home/alboot/Sources/alsa/alsa-driver-1.0.14rc3/pci/hda/../../alsa-kernel/pci/hda/hda_intel.c:1158: azx_pcm_prepare: bufsize=0x10000, fragsize=0x1000, format=0x11 [ 216.972000] ALSA /home/alboot/Sources/alsa/alsa-driver-1.0.14rc3/pci/hda/hda_codec.c:627: hda_codec_setup_stream: NID=0x2, stream=0x5, channel=0, format=0x11 [ 216.980000] ALSA /home/alboot/Sources/alsa/alsa-driver-1.0.14rc3/pci/hda/hda_codec.c:627: hda_codec_setup_stream: NID=0x4, stream=0x5, channel=0, format=0x11 [ 216.988000] ALSA /home/alboot/Sources/alsa/alsa-driver-1.0.14rc3/pci/hda/hda_codec.c:627: hda_codec_setup_stream: NID=0x3, stream=0x5, channel=0, format=0x11 [ 216.996000] ALSA /home/alboot/Sources/alsa/alsa-driver-1.0.14rc3/pci/hda/hda_codec.c:627: hda_codec_setup_stream: NID=0x5, stream=0x5, channel=0, format=0x11 [ 218.824000] ALSA /home/alboot/Sources/alsa/alsa-driver-1.0.14rc3/pci/hda/hda_codec.c:627: hda_codec_setup_stream: NID=0x2, stream=0x0, channel=0, format=0x0 [ 218.832000] ALSA /home/alboot/Sources/alsa/alsa-driver-1.0.14rc3/pci/hda/hda_codec.c:627: hda_codec_setup_stream: NID=0x4, stream=0x0, channel=0, format=0x0 [ 218.840000] ALSA /home/alboot/Sources/alsa/alsa-driver-1.0.14rc3/pci/hda/hda_codec.c:627: hda_codec_setup_stream: NID=0x3, stream=0x0, channel=0, format=0x0 [ 218.848000] ALSA /home/alboot/Sources/alsa/alsa-driver-1.0.14rc3/pci/hda/hda_codec.c:627: hda_codec_setup_stream: NID=0x5, stream=0x0, channel=0, format=0x0 Thanks

2 1