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

[alsa-devel] hda Regression: jack doesn't mute speaker
by Ortwin Glück 16 Apr '09

16 Apr '09

Hi, Since 2.6.30-rc1 when I plug in headphones in the side jack the built-in speakers are not muted any more. Worked fine until 2.6.29.1. Also the "Front" and "Surround" outputs are now both labeled "Speaker" (see attached images of kmix). lspci: 00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 02) uname -a: Linux mithril 2.6.30-rc2 #2 SMP PREEMPT Wed Apr 15 22:51:36 CEST 2009 i686 Intel(R) Core(TM)2 CPU T7600 @ 2.33GHz GenuineIntel GNU/Linux dmesg: HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22 HDA Intel 0000:00:1b.0: setting latency timer to 6 hda_codec: STAC922x, Apple subsys_id=106b1a00 input: HDA Intel Line In at Ext Left Jack as /class/input/input8 input: HDA Intel Mic at Ext Left Jack as /class/input/input9 hda-intel: IRQ timing workaround is activated for card #0. Suggest a bigger bdl_pos_adj. uname -a: Linux mithril 2.6.29.1 #3 SMP PREEMPT Wed Apr 15 23:03:20 CEST 2009 i686 Intel(R) Core(TM)2 CPU T7600 @ 2.33GHz GenuineIntel GNU/Linux dmesg: HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22 HDA Intel 0000:00:1b.0: setting latency timer to 64 hda_codec: STAC922x, Apple subsys_id=106b1a00 Apr 15 23:20:22 mithril input: HDA Intel Line In at Ext Left Jack as /class/input/input8 Apr 15 23:20:22 mithril input: HDA Intel Mic at Ext Left Jack as /class/input/input9 Apr 15 23:20:22 mithril input: HDA Intel HP Out at Ext Left Jack as /class/input/input10 hda-intel: IRQ timing workaround is activated for card #0. Suggest a bigger bdl_pos_adj.

2 4

Re: [alsa-devel] 15 April unstable does not handle wave-in
by Takashi Iwai 16 Apr '09

16 Apr '09

At Wed, 15 Apr 2009 12:13:51 -0400 (GMT-04:00), Susan Cragin wrote: > > >> >> I just downloaded and installed the unstable snapshot 15-April 9:55. > >> >> Both my sound cards are shown by asoundconf, but neither works. The wave-in wave-out is still not recognized. > >> > > >> >I suppose you are referring to CA0110? Could you elaborate? > >> > > >> >The ca0110 codec support itself has no big change. The last one was > >> >in Feb. 18. The rest is either HD-audio core or PCM core. But these > >> >have little to do with the probing... > >> > > >> > > >> >Takashi > >> > >> Please excuse my technical ignorance. Here is everything I know. > >> My hda-intel card is also not being recognized after installing alsa-driver-unstable. The only thing that works is my usb microphone. > >> I think that the program is not giving the instruction to have > >> modules inserted on bootup. > >> I have attached sample modprobe, aplay, asoundconf, modules, > >> alsa-base.conf > > > >Check /proc/asound/version. Is it the latest one? > > > >> $ modprobe snd-card-hda-intel > > > >modprobe snd-hda-intel > > > > > >Takashi > > $ sudo cat /proc/asound/version > Advanced Linux Sound Architecture Driver Version 1.0.19. > Compiled on Apr 15 2009 for kernel 2.6.28-11-generic (SMP). Then it looks OK. The problem might be a patch currently included in the unstable tree, which could be broken. I'll check it later. Meanwhile, if ca0110 worked fine with unstable tree before, it means that the hda-ca0110 patch can go in to the sound git tree. This would be a better option for both of us. thanks, Takashi

1 2

Re: [alsa-devel] SALSA library and recording
by reetesh chandran 16 Apr '09

16 Apr '09

Hi Manisha, Sorry this is not a response which will help you. I am facing similar issue. I am using SALSA and I am trying to record from a USB headset. The USB headset does have a mixer elem "Mic". But when I use snd_mixer_selem_get_capture_dB_range() or snd_mixer_selem_get_capture_volume_range() I just get zeroes. I did not do any set() functions like snd_mixer_selem_set_capture_switch_all(). Do I need to do that ? What is your source of info about how to set up the mixer for capture ? Thanks in advance Reetesh --- On Wed, 4/15/09, Manisha Sankpal <manisha.sankpal(a)gmail.com> wrote: From: Manisha Sankpal <manisha.sankpal(a)gmail.com> Subject: [alsa-devel] SALSA library and recording To: alsa-devel(a)alsa-project.org Date: Wednesday, April 15, 2009, 9:32 AM Hi All, I am using salsa library to capture the data from the sound card. The requirement is that the recording should be done from line-in port of the sound card. The selection of "Line-in" port should be done programatically. With ALSA library, I am able to select the line-in by calling snd_mixer_selem_set_capture_switch_all() function. However, this function is returning an error when SALSA library is used. Is there any other function/way to select the line-in mixer element in the SALSA API? The help would be appreciated. Thanks & regards, manisha _______________________________________________ Alsa-devel mailing list Alsa-devel(a)alsa-project.org http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

2 1

[alsa-devel] SALSA library and recording
by Manisha Sankpal 16 Apr '09

16 Apr '09

Hi All, I am using salsa library to capture the data from the sound card. The requirement is that the recording should be done from line-in port of the sound card. The selection of "Line-in" port should be done programatically. With ALSA library, I am able to select the line-in by calling snd_mixer_selem_set_capture_switch_all() function. However, this function is returning an error when SALSA library is used. Is there any other function/way to select the line-in mixer element in the SALSA API? The help would be appreciated. Thanks & regards, manisha

3 3

[alsa-devel] [PATCH] Intel8x0: Remove conflicting quirk for SSID 0x103c0934
by Daniel T Chen 16 Apr '09

16 Apr '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 While cleaning up quirks, I noticed that there is a duplicated quirk for the SSID 0x103c0934. Looking back through the bug reports, I've concluded that there is only one necessary quirk (hp_mute_led), so this patch removes the conflicting one. Thanks, Daniel T Chen -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iD8DBQFJ5nEoe9GwFciKvaMRAqf+AJ45j7iM7XYnV+bDO9sa7fj4XjpHlQCfSSAw mOJvx87TYvsMbGw5g/aS8Ds= =rvle -----END PGP SIGNATURE-----

2 1

[alsa-devel] [PATCH] Intel8x0: Add hp_only quirk for SSID 0x1028016a (Dell Inspiron 8600)
by Daniel T Chen 16 Apr '09

16 Apr '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Subject says it all. Briefly, use hp_only for another Dell Inspiron 8600. Thanks, Daniel T Chen -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iD8DBQFJ5nI5e9GwFciKvaMRAqyEAKDEzBbqoTVX84Mnh3G/5NtRsy7hbACcC/8a xoAY8903z+8x7oIB3WKoZkA= =r3JR -----END PGP SIGNATURE-----

1 0

[alsa-devel] Alsa Pulse plugin pcm->ptr initialization problem
by Dake Gu 16 Apr '09

16 Apr '09

Hi all, By looking through the pcm_pulse.c(1.0.18), I found there is a possible error in initializing the pcm->ptr. Some background: see update_ptr() function in pcm_pulse.c: Basically the pcm->ptr is increased when pa_stream_writable_size() increases. The last pa_stream_writable_size() is saved in pcm->last_size, so if new pa_stream_writable_size() value is larger than pcm->last_size, the pcm->ptr is increased. For example, the pa_stream_writable_size() increases from 800 to 1400, then pcm->ptr is increased by 400. Alsa-lib's snd_pcm_ioplug_hw_ptr_update() function is calling pulse_pointer() to get pcm->ptr, then pcm_ioplug.c calculates the hw.ptr from the changes of pulse_pointer(). The hw.ptr is used in snd_pcm_mmap_playback_avail(). However, there is an issue that during the pulse is started, the pcm->last_size jumps from 0 to a positive value, which should not be counted as pcm->ptr increase. It's causing the hw.ptr wrongly calculated. Wrong senario pa_writable (N/A) 1000 900 800 1200 pcm->ptr 0 1000 1000 1000 1400 ..... hw.ptr 0 1000 1000 1000 1400 Correct scenario: pa_writable (N/A) 1000 900 800 1200 pcm->ptr 0 0 0 0 400 ..... hw.ptr 0 0 0 0 400 If hw.ptr is incorrectly set larger than actual size, it causes avail>"real avail" and client sends more data than pulse can accept. Dake

1 0

[alsa-devel] [PATCH] ASoC: pxa-ssp: allow setting of dai format 0
by Daniel Mack 15 Apr '09

15 Apr '09

pxa_ssp_set_dai_fmt() currently has an early exit if the desired format equals the current configuration. This is correct behaviour unless this function is called with a zero value parameter for the first time. Zero is a valid value for this function, but the early exit is bogus in this case. Hence, set priv->dai_fmt to -1 in the beginning so we can configure the port. Signed-off-by: Daniel Mack <daniel(a)caiaq.de> Cc: Mark Brown <broonie(a)sirena.org.uk> Cc: pHilipp Zabel <philipp.zabel(a)gmail.com> --- sound/soc/pxa/pxa-ssp.c | 1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/sound/soc/pxa/pxa-ssp.c b/sound/soc/pxa/pxa-ssp.c index 308a657..de22544 100644 --- a/sound/soc/pxa/pxa-ssp.c +++ b/sound/soc/pxa/pxa-ssp.c @@ -806,6 +806,7 @@ static int pxa_ssp_probe(struct platform_device *pdev, goto err_priv; } + priv->dai_fmt = (unsigned int) -1; dai->private_data = priv; return 0; -- 1.6.2.1

2 1

[alsa-devel] [PATCH] hda_intel.c - Consolidate bitfields
by Joe Perches 15 Apr '09

15 Apr '09

Previously sent to linux-kernel. Commit fa00e046b41663cbda9b1affc0594669e5f14219 added a new bitfield not adjacent to other bitfields in the same struct. Moved the new one. Signed-off-by: Joe Perches <joe(a)perches.com> diff --git a/sound/pci/hda/hda_intel.c b/sound/pci/hda/hda_intel.c index bc882f8..21e99cf 100644 --- a/sound/pci/hda/hda_intel.c +++ b/sound/pci/hda/hda_intel.c @@ -312,7 +312,6 @@ struct azx_dev { unsigned int period_bytes; /* size of the period in bytes */ unsigned int frags; /* number for period in the play buffer */ unsigned int fifo_size; /* FIFO size */ - unsigned int start_flag: 1; /* stream full start flag */ unsigned long start_jiffies; /* start + minimum jiffies */ unsigned long min_jiffies; /* minimum jiffies before position is valid */ @@ -333,6 +332,7 @@ struct azx_dev { unsigned int opened :1; unsigned int running :1; unsigned int irq_pending :1; + unsigned int start_flag: 1; /* stream full start flag */ /* * For VIA: * A flag to ensure DMA position is 0

1 0

Re: [alsa-devel] 15 April unstable does not handle wave-in
by Susan Cragin 15 Apr '09

15 Apr '09

>>> >> I just downloaded and installed the unstable snapshot 15-April 9:55. >>> >> Both my sound cards are shown by asoundconf, but neither works. The wave-in wave-out is still not recognized. >>> > >>> >I suppose you are referring to CA0110? Could you elaborate? >>> > >>> >The ca0110 codec support itself has no big change. The last one was >>> >in Feb. 18. The rest is either HD-audio core or PCM core. But these >>> >have little to do with the probing... >>> > >>> > >>> >Takashi >>> >>> Please excuse my technical ignorance. Here is everything I know. >>> My hda-intel card is also not being recognized after installing alsa-driver-unstable. The only thing that works is my usb microphone. >>> I think that the program is not giving the instruction to have >>> modules inserted on bootup. >>> I have attached sample modprobe, aplay, asoundconf, modules, >>> alsa-base.conf >> >>Check /proc/asound/version. Is it the latest one? >> >>> $ modprobe snd-card-hda-intel >> >>modprobe snd-hda-intel >> >> >>Takashi > >$ sudo cat /proc/asound/version >Advanced Linux Sound Architecture Driver Version 1.0.19. >Compiled on Apr 15 2009 for kernel 2.6.28-11-generic (SMP). >susan@ubuntu:~$ modprobe snd-hda-intel >WARNING: All config files need .conf: /etc/modprobe.d/oss-compat, it will be ignored in a future release. >susan@ubuntu:~$ I should mention something else. This happened once before, a couple of weeks ago, I think. Then header updates came out of the Ubuntu-Jaunty repository, and then the problem went away. I wish I had been paying more attention to what happened. Susan

1 0