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

Re: [alsa-devel] hda-intel: no soundcard with current linus' git tree
by Jan-Simon Möller 21 Oct '07

21 Oct '07

I've also no sound. Had it working using the alsa.git tree _before_ the last merge (>48h). Needed to use model=asus for this fujitsu v5505 here. Now it doesn't work, even with other model-options (fujitsu, laptop). legolas:/proc/asound # cat cards 0 [Intel ]: HDA-Intel - HDA Intel HDA Intel at 0xfc400000 irq 22 legolas:/proc/asound # cat pcm 00-01: Conexant Digital : Conexant Digital : playback 1 00-00: CONEXANT Analog : CONEXANT Analog : playback 1 : capture 1 legolas:/proc/asound # cat hwdep 00-00: HDA Codec 0 legolas:/proc/asound # cat devices 2: : timer 3: [ 0- 1]: digital audio playback 4: [ 0- 0]: digital audio playback 5: [ 0- 0]: digital audio capture 6: [ 0- 0]: hardware dependent 7: [ 0] : control 8: : sequencer legolas:/proc/asound # cat card0/codec#0 Codec: Conexant CX20549 (Venice) Address: 0 Vendor Id: 0x14f15045 Subsystem Id: 0x1734110e Revision Id: 0x100100 No Modem Function Group found Default PCM: rates [0x140]: 48000 96000 bits [0xe]: 16 20 24 formats [0x1]: PCM Default Amp-In caps: N/A Default Amp-Out caps: N/A Node 0x10 [Pin Complex] wcaps 0x40058d: Stereo Amp-Out Amp-Out caps: ofs=0x2b, nsteps=0x2b, stepsize=0x05, mute=1 Amp-Out vals: [0x2b 0x2b] Pincap 0x0810014: OUT EAPD Detect Pin Default 0x92170110: [Fixed] Speaker at Int Front Conn = Analog, Color = Unknown Pin-ctls: 0x40: OUT Power: 0x0 Connection: 2 0x19 0x17* Node 0x11 [Pin Complex] wcaps 0x40058d: Stereo Amp-Out Amp-Out caps: ofs=0x2b, nsteps=0x2b, stepsize=0x05, mute=1 Amp-Out vals: [0x2b 0x2b] Pincap 0x08113c: IN OUT HP Detect Pin Default 0x0121401f: [Jack] HP Out at Ext Rear Conn = 1/8, Color = Green Pin-ctls: 0xc0: OUT HP Power: 0x0 Connection: 2 0x19 0x17* Node 0x12 [Pin Complex] wcaps 0x40058d: Stereo Amp-Out Amp-Out caps: ofs=0x2b, nsteps=0x2b, stepsize=0x05, mute=1 Amp-Out vals: [0x2b 0x2b] Pincap 0x08113c: IN OUT HP Detect Pin Default 0x01a19020: [Jack] Mic at Ext Rear Conn = 1/8, Color = Pink Pin-ctls: 0x20: IN Power: 0x0 Connection: 2 0x19 0x17* Node 0x13 [Pin Complex] wcaps 0x400301: Stereo Digital Pincap 0x0810: OUT Pin Default 0x214571f0: [Jack] SPDIF Out at Sep Rear Conn = Optical, Color = Yellow Pin-ctls: 0x00: Connection: 1 0x18 Node 0x14 [Pin Complex] wcaps 0x400081: Stereo Pincap 0x081124: IN Detect Pin Default 0x97a7012e: [Fixed] Mic at Int Riser Conn = Analog, Color = Unknown Pin-ctls: 0x24: IN Node 0x15 [Pin Complex] wcaps 0x400001: Stereo Pincap 0x0820: IN Pin Default 0x400001f0: [N/A] Line Out at Ext N/A Conn = Unknown, Color = Unknown Pin-ctls: 0x00: Node 0x16 [Beep Generator Widget] wcaps 0x70000c: Mono Amp-Out Amp-Out caps: ofs=0x07, nsteps=0x07, stepsize=0x0b, mute=1 Amp-Out vals: [0x06] Node 0x17 [Audio Mixer] wcaps 0x20050b: Stereo Amp-In Amp-In caps: ofs=0x14, nsteps=0x2b, stepsize=0x05, mute=1 Amp-In vals: [0x94 0x94] [0x94 0x94] [0x94 0x94] [0x94 0x94] [0x94 0x94] Power: 0x0 Connection: 5 0x19 0x14 0x12 0x11 0x15 Node 0x18 [Audio Output] wcaps 0x211: Stereo Digital PCM: rates [0x40]: 48000 bits [0x6]: 16 20 formats [0x5]: PCM AC3 Node 0x19 [Audio Output] wcaps 0xc11: Stereo PCM: rates [0x540]: 48000 96000 192000 bits [0xe]: 16 20 24 formats [0x1]: PCM Power: 0x0 Node 0x1a [Audio Input] wcaps 0x100d0b: Stereo Amp-In Amp-In caps: ofs=0x00, nsteps=0x17, stepsize=0x05, mute=1 Amp-In vals: [0x17 0x17] [0x00 0x00] [0x00 0x00] [0x00 0x00] [0x00 0x00] Power: 0x0 Connection: 5 0x17 0x14* 0x12 0x11 0x15 Node 0x1b [Vendor Defined Widget] wcaps 0xf00000: Mono Best regards Jan-Simon

2 9

Re: [alsa-devel] [Jackit-devel] RME HDSP driver enhancements for HDSPe cards
by John Rigg 19 Oct '07

19 Oct '07

On Fri, Oct 19, 2007 at 08:58:00AM +0100, Ed W wrote: > RME are also helpful to the extent that you ask them specific questions > and in the name of writing drivers. They should give you hardware > details, etc > > > As an aside, apart from CPU load I will be suprised if turning floats > into 32bit ints makes any difference to the audio, but I agree that it > would be a nice feature to have! IIRC the new RME cards convert 24 bit integers to 32 bit floats in hardware (and vice versa), thus saving apps like jackd (and the CPU) the trouble. jackd doesn't support that yet, but AFAIK it shouldn't be too much effort to change that. John

1 0

[alsa-devel] [PATCH] hda: Add dmux to STAC 9228
by Matthew Ranostay 19 Oct '07

19 Oct '07

Added a dmux to the STAC9228 cards with DMIC support. And added a STAC_DIGITAL_INPUT_SOURCE macro for repeating mixer code. --- Signed-off-by: Matthew Ranostay <mranostay(a)embeddedalley.com> diff -r 821a4558dd47 pci/hda/patch_sigmatel.c --- a/pci/hda/patch_sigmatel.c Thu Oct 18 17:38:17 2007 +0200 +++ b/pci/hda/patch_sigmatel.c Thu Oct 18 17:35:56 2007 -0400 @@ -430,6 +430,16 @@ static struct hda_verb stac9205_core_ini {} }; +#define STAC_DIGITAL_INPUT_SOURCE(cnt) \ + { \ + .iface = SNDRV_CTL_ELEM_IFACE_MIXER, \ + .name = "Digital Input Source", \ + .count = cnt, \ + .info = stac92xx_dmux_enum_info, \ + .get = stac92xx_dmux_enum_get, \ + .put = stac92xx_dmux_enum_put,\ + } + #define STAC_INPUT_SOURCE(cnt) \ { \ .iface = SNDRV_CTL_ELEM_IFACE_MIXER, \ @@ -482,14 +492,7 @@ static struct snd_kcontrol_new stac925x_ }; static struct snd_kcontrol_new stac9205_mixer[] = { - { - .iface = SNDRV_CTL_ELEM_IFACE_MIXER, - .name = "Digital Input Source", - .count = 1, - .info = stac92xx_dmux_enum_info, - .get = stac92xx_dmux_enum_get, - .put = stac92xx_dmux_enum_put, - }, + STAC_DIGITAL_INPUT_SOURCE(1), STAC_INPUT_SOURCE(2), STAC_ANALOG_LOOPBACK(0xFE0, 0x7E0), STAC_VOLKNOB(0x24), @@ -521,6 +524,7 @@ static struct snd_kcontrol_new stac922x_ static struct snd_kcontrol_new stac927x_mixer[] = { + STAC_DIGITAL_INPUT_SOURCE(1), STAC_INPUT_SOURCE(3), STAC_VOLKNOB(0x24), STAC_ANALOG_LOOPBACK(0xFEB, 0x7EB), @@ -2773,6 +2777,7 @@ static int patch_stac927x(struct hda_cod case 0x10280209: /* STAC 9228 */ spec->dmic_nids = stac927x_dmic_nids; spec->num_dmics = STAC927X_NUM_DMICS; + spec->dmux_nid = 0x1c; break; default: spec->num_dmics = 0;

3 5

[alsa-devel] ALSA Bluetooth connection issue
by 19 Oct '07

19 Oct '07

Hi All: Im using ALSA 1.0.14 and bluez 3.20 and linux 2.6.18.The linux 2.6.18 (montavista) is running on an embeded development board(using S3C2410). When i tried to use 'aplay' to connect my bluetooth headset, i got the following error from ALSA: $ aplay -D bluetooth /1.wav audio[326]: Accepted new client connection on unix socket (fd=8) audio[326]: Package PKT_TYPE_CFG_REQ:0 hcid[318]: /org/bluez: org.bluez.Manager.FindAdapter() audio[326]: Got path /org/bluez/hci0 for adapter with address 00:80:E1:00:00:00 hcid[318]: /org/bluez/hci0: org.bluez.Adapter.GetRemoteServiceHandles() hcid[318]: no matching session found. creating a new one hcid[318]: sdp session added to cache hcid[318]: /org/bluez/hci0: org.bluez.Adapter.GetRemoteServiceHandles() hcid[318]: found matching session, removing from list hcid[318]: sdp session added to cache hcid[318]: /org/bluez/hci0: org.bluez.Adapter.GetRemoteServiceHandles() hcid[318]: found matching session, removing from list hcid[318]: sdp session added to cache hcid[318]: /org/bluez/hci0: org.bluez.Adapter.GetRemoteServiceRecord() hcid[318]: found matching session, removing from list hcid[318]: sdp session added to cache hcid[318]: /org/bluez/hci0: org.bluez.Adapter.GetRemoteServiceRecord() hcid[318]: found matching session, removing from list hcid[318]: sdp session added to cache hcid[318]: /org/bluez/hci0: org.bluez.Adapter.GetRemoteServiceRecord() hcid[318]: found matching session, removing from list hcid[318]: sdp session added to cache hcid[318]: /org/bluez/hci0: org.bluez.Adapter.GetRemoteServiceRecord() hcid[318]: found matching session, removing from list hcid[318]: sdp session added to cache audio[326]: Audio service discovery completed with success hcid[318]: /org/bluez/hci0: org.bluez.Adapter.FinishRemoteServiceTransaction() hcid[318]: found matching session, removing from list audio[326]: Found Hansfree record audio[326]: Discovered Headset service on RFCOMM channel 1 audio[326]: Found Headset record audio[326]: Found Audio Sink audio[326]: Selecting default device audio[326]: avdtp_ref(0x3b018): ref=2 audio[326]: a2dp_source_request_stream: selected SEP 0x37250 audio[326]: avdtp_ref(0x3b018): ref=3 hcid[318]: link_key_request (sba=00:80:E1:00:00:00, dba=00:0D:3C:EB:53:F0) audio[326]: AVDTP: connected signaling channel to 00:0D:3C:EB:53:F0 audio[326]: session_cb audio[326]: DISCOVER request succeeded audio[326]: seid 1 type 1 media 0 in use 0 audio[326]: seid 2 type 1 media 0 in use 0 audio[326]: session_cb audio[326]: GET_CAPABILITIES request succeeded audio[326]: seid 1 type 1 media 0 hcid[318]: link_key_request (sba=00:80:E1:00:00:00, dba=00:0D:3C:EB:53:F0) hcid[318]: link_key_request (sba=00:80:E1:00:00:00, dba=00:0D:3C:EB:53:F0) audio[326]: session_cb audio[326]: GET_CAPABILITIES request succeeded audio[326]: seid 2 type 1 media 0 audio[326]: Discovery complete audio[326]: avdtp_set_configuration(0x3b018): int_seid=1, acp_seid=1 audio[326]: session_cb audio[326]: SET_CONFIGURATION request succeeded audio[326]: SBC Source: Set_Configuration_Cfm audio[326]: avdtp_ref(0x3b018): ref=4 audio[326]: stream state changed: IDLE -> CONFIGURED audio[326]: session_cb audio[326]: OPEN request succeeded audio[326]: stream state changed: CONFIGURED -> OPEN audio[326]: AVDTP: connected transport channel to 00:0D:3C:EB:53:F0 audio[326]: SBC Source: Open_Cfm audio[326]: session_cb audio[326]: START request succeeded audio[326]: SBC Source: Start_CAlignment trap: bluetoothd-serv (326) PC=0x0001be44 Instr=0xe1c320b0 Address=0xbec85c2d FSR 0x813 fm audio[326]: SBC Source SEP 0x37250 locked hcid[318]: Service owner exited: :1.2 aplay: main:550: audio open error: Input/output error hcid[318]: Audio service (audio) was killed by signal 7 ALSA's aplay reports an "Input/output error". Later i digged into alsa-lib-1.0.14/src/pcm/pcm.c and found that snd_config_search_definition() returns an error. It seems ALSA didn't find the proper conf definition or something like that. My ".asoundrc" is as followed: pcm.a2dpd { type a2dpd } pcm.bluetooth { type bluetooth device 00:0D:3C:EB:53:F0 } pcm.!default { type hw card 0 device 0 } pcm.card0 { type hw card 0 } ctl.card0 { type hw card 0 } Does someone have any idea about what's going wrong in this? Thanks in advance! semiyd _________________________________________________________________ Discover the new Windows Vista http://search.msn.com/results.aspx?q=windows+vista&mkt=en-US&form=QBRE

1 0

[alsa-devel] ALSA-for custom Operating System????
by Anoop Thomas 19 Oct '07

19 Oct '07

First of all don't make fun of me if i am asking a foolishness.Could you plz tell me can i use alsa for my custom OS which concentrates more on audio side.It doesn't uses linux kernel.Does it make a difference???? (ie. is it enough to give sufficient data to ALSA to help me to make the audio out of the system).If I can plz give me a brief description.... Help me plz................. --------------------------------- Forgot the famous last words? Access your message archive online. Click here.

1 0

[alsa-devel] [PATCH] s3c2443-ac97: compilation fix
by Krzysztof Helt 18 Oct '07

18 Oct '07

From: Krzysztof Helt <krzysztof.h1(a)wp.pl> The Samsung S3C24xx uses new architecture file layout in the post 2.6.23 kernel. This patch fixes include path for the s3c2443-ac97.c. Signed-off-by: Krzysztof Helt <krzysztof.h1(a)wp.pl> --- The patch was done against the 2.6.23-git13 kernel. diff -urp linux-ref/sound/soc/s3c24xx/s3c2443-ac97.c linux-new/sound/soc/s3c24xx/s3c2443-ac97.c --- linux-ref/sound/soc/s3c24xx/s3c2443-ac97.c 2007-10-09 22:31:38.000000000 +0200 +++ linux-new/sound/soc/s3c24xx/s3c2443-ac97.c 2007-10-18 22:27:43.547470033 +0200 @@ -32,7 +32,7 @@ #include <asm/hardware.h> #include <asm/io.h> -#include <asm/arch/regs-ac97.h> +#include <asm/plat-s3c/regs-ac97.h> #include <asm/arch/regs-gpio.h> #include <asm/arch/regs-clock.h> #include <asm/arch/audio.h> ---------------------------------------------------------------------- Jaros�aw Drob, Przyjdziemy i Spie***ymy - poznaj kandydata! Kliknij >>> http://link.interia.pl/f1bef

1 0

[alsa-devel] Kernel hierarchy
by Adrian McMenamin 18 Oct '07

18 Oct '07

Why are sound drivers in /sound and not /drivers/sound? Ok, not the world's most pressing problem, but enquiring minds want to know! Adrian

2 1

[alsa-devel] [PATCH] hda: STAC9228 DMIC Support
by Matthew Ranostay 18 Oct '07

18 Oct '07

Added DMIC support for STAC9228 cards, as well as adding terminators to other hda_nid DMIC arrays, and added a new Vendor ID tag. --- Signed-off-by: Matthew Ranostay <mranostay(a)embeddedalley.com> diff -r e91f57f8127a pci/hda/hda_codec.c --- a/pci/hda/hda_codec.c Tue Oct 09 11:58:41 2007 +0200 +++ b/pci/hda/hda_codec.c Wed Oct 17 11:59:47 2007 -0400 @@ -55,6 +55,7 @@ static struct hda_vendor_id hda_vendor_i { 0x10ec, "Realtek" }, { 0x1057, "Motorola" }, { 0x1106, "VIA" }, + { 0x111d, "IDT" }, { 0x11d4, "Analog Devices" }, { 0x13f6, "C-Media" }, { 0x14f1, "Conexant" }, diff -r e91f57f8127a pci/hda/patch_sigmatel.c --- a/pci/hda/patch_sigmatel.c Tue Oct 09 11:58:41 2007 +0200 +++ b/pci/hda/patch_sigmatel.c Wed Oct 17 13:06:58 2007 -0400 @@ -182,8 +182,9 @@ static hda_nid_t stac925x_dac_nids[1] = 0x02, }; -static hda_nid_t stac925x_dmic_nids[1] = { - 0x15, +static hda_nid_t stac925x_dmic_nids[2] = { + 0x15, + 0x00, /* terminator */ }; static hda_nid_t stac922x_adc_nids[2] = { @@ -202,6 +203,11 @@ static hda_nid_t stac927x_mux_nids[3] = 0x15, 0x16, 0x17 }; +static hda_nid_t stac927x_dmic_nids[3] = { + 0x13, 0x14, + 0x00, /* terminator */ +}; + static hda_nid_t stac9205_adc_nids[2] = { 0x12, 0x13 }; @@ -210,8 +216,9 @@ static hda_nid_t stac9205_mux_nids[2] = 0x19, 0x1a }; -static hda_nid_t stac9205_dmic_nids[2] = { +static hda_nid_t stac9205_dmic_nids[3] = { 0x17, 0x18, + 0x00, /* terminator */ }; static hda_nid_t stac9200_pin_nids[8] = { @@ -2716,7 +2723,6 @@ static int patch_stac927x(struct hda_cod spec->mux_nids = stac927x_mux_nids; spec->num_muxes = ARRAY_SIZE(stac927x_mux_nids); spec->num_adcs = ARRAY_SIZE(stac927x_adc_nids); - spec->num_dmics = 0; spec->init = d965_core_init; spec->mixer = stac927x_mixer; break; @@ -2725,7 +2731,6 @@ static int patch_stac927x(struct hda_cod spec->mux_nids = stac927x_mux_nids; spec->num_muxes = ARRAY_SIZE(stac927x_mux_nids); spec->num_adcs = ARRAY_SIZE(stac927x_adc_nids); - spec->num_dmics = 0; spec->init = d965_core_init; spec->mixer = stac927x_mixer; break; @@ -2734,9 +2739,18 @@ static int patch_stac927x(struct hda_cod spec->mux_nids = stac927x_mux_nids; spec->num_muxes = ARRAY_SIZE(stac927x_mux_nids); spec->num_adcs = ARRAY_SIZE(stac927x_adc_nids); - spec->num_dmics = 0; spec->init = stac927x_core_init; spec->mixer = stac927x_mixer; + } + + switch (codec->subsystem_id) { + case 0x1028020A: /* STAC 9228 */ + case 0x10280209: /* STAC 9228 */ + spec->dmic_nids = stac927x_dmic_nids; + spec->num_dmics = 2; + break; + default: + spec->num_dmics = 0; } spec->multiout.dac_nids = spec->dac_nids; @@ -2798,7 +2812,7 @@ static int patch_stac9205(struct hda_cod spec->mux_nids = stac9205_mux_nids; spec->num_muxes = ARRAY_SIZE(stac9205_mux_nids); spec->dmic_nids = stac9205_dmic_nids; - spec->num_dmics = ARRAY_SIZE(stac9205_dmic_nids); + spec->num_dmics = 2; spec->dmux_nid = 0x1d; spec->init = stac9205_core_init;

2 3

[alsa-devel] alsa-driver-1.0.15rc2 build issues on RHEL4/CentOS4
by James Pearson 18 Oct '07

18 Oct '07

alsa-driver-1.0.15rc2 won't build cleanly on RHEL4/CentOS4 (2.6.9 based kernel). I've included the relevant errors below after running: configure --with-redhat make -i The problem with misc/ac97_bus.c, I've already reported at: <http://mailman.alsa-project.org/pipermail/alsa-devel/2007-September/003119.…> James Pearson Build errors: CC [M] /tmp/alsa-driver-1.0.15rc2/misc/ac97_bus.o In file included from /tmp/alsa-driver-1.0.15rc2/misc/ac97_bus.c:3: /tmp/alsa-driver-1.0.15rc2/misc/../alsa-kernel/ac97_bus.c: In function `ac97_bus_suspend': /tmp/alsa-driver-1.0.15rc2/misc/../alsa-kernel/ac97_bus.c:35: error: too few arguments to function /tmp/alsa-driver-1.0.15rc2/misc/../alsa-kernel/ac97_bus.c: In function `ac97_bus_resume': /tmp/alsa-driver-1.0.15rc2/misc/../alsa-kernel/ac97_bus.c:45: error: too few arguments to function make[4]: [/tmp/alsa-driver-1.0.15rc2/misc/ac97_bus.o] Error 1 (ignored) CC [M] /tmp/alsa-driver-1.0.15rc2/pci/cs5535audio/cs5535audio_pm.o In file included from /tmp/alsa-driver-1.0.15rc2/pci/cs5535audio/cs5535audio_pm.c:2: /tmp/alsa-driver-1.0.15rc2/pci/cs5535audio/../../alsa-kernel/pci/cs5535audio/cs5535audio_pm.c: In function `snd_cs5535audio_suspend': /tmp/alsa-driver-1.0.15rc2/pci/cs5535audio/../../alsa-kernel/pci/cs5535audio/cs5535audio_pm.c:77: error: void value not ignored as it ought to be /tmp/alsa-driver-1.0.15rc2/pci/cs5535audio/../../alsa-kernel/pci/cs5535audio/cs5535audio_pm.c: In function `snd_cs5535audio_resume': /tmp/alsa-driver-1.0.15rc2/pci/cs5535audio/../../alsa-kernel/pci/cs5535audio/cs5535audio_pm.c:95: error: void value not ignored as it ought to be make[5]: [/tmp/alsa-driver-1.0.15rc2/pci/cs5535audio/cs5535audio_pm.o] Error 1 (ignored) LD [M] /tmp/alsa-driver-1.0.15rc2/pci/cs5535audio/snd-cs5535audio.o ld: /tmp/alsa-driver-1.0.15rc2/pci/cs5535audio/cs5535audio_pm.o: No such file: No such file or directory make[5]: [/tmp/alsa-driver-1.0.15rc2/pci/cs5535audio/snd-cs5535audio.o] Error 1 (ignored) Building modules, stage 2. MODPOST *** Warning: "class_device_destroy" [/tmp/alsa-driver-1.0.15rc2/pci/asihpi/snd-asihpi.ko] undefined! *** Warning: "ac97_bus_type" [/tmp/alsa-driver-1.0.15rc2/pci/ac97/snd-ac97-codec.ko] undefined! *** Warning: "platform_device_alloc" [/tmp/alsa-driver-1.0.15rc2/drivers/snd-portman2x4.ko] undefined! *** Warning: "platform_device_add" [/tmp/alsa-driver-1.0.15rc2/drivers/snd-portman2x4.ko] undefined! *** Warning: "platform_device_put" [/tmp/alsa-driver-1.0.15rc2/drivers/snd-portman2x4.ko] undefined! *** Warning: "platform_device_alloc" [/tmp/alsa-driver-1.0.15rc2/drivers/snd-mts64.ko] undefined! *** Warning: "platform_device_add" [/tmp/alsa-driver-1.0.15rc2/drivers/snd-mts64.ko] undefined! *** Warning: "platform_device_put" [/tmp/alsa-driver-1.0.15rc2/drivers/snd-mts64.ko] undefined!

2 9

[alsa-devel] [patch] snd_pcm_dmix_close: raise semaphore if unable to discard
by Mike Gorse 18 Oct '07

18 Oct '07

This patch causes snd_pcm_dmix_close() to up a semaphore after downing it if it is unable to discard it. It prevents some deadlock that I am getting when a couple of applications interact and one of them closes the device and later re-opens it. -- --- src/pcm/pcm_dmix.c.orig 2007-10-17 20:19:47.000000000 -0400 +++ src/pcm/pcm_dmix.c 2007-10-17 20:50:46.000000000 -0400 @@ -652,8 +652,11 @@ if (dmix->client) snd_pcm_direct_client_discard(dmix); shm_sum_discard(dmix); - if (snd_pcm_direct_shm_discard(dmix)) - snd_pcm_direct_semaphore_discard(dmix); + if (snd_pcm_direct_shm_discard(dmix)) { + if (snd_pcm_direct_semaphore_discard(dmix)) { + snd_pcm_direct_semaphore_up(dmix, DIRECT_IPC_SEM_CLIENT); + } + } else snd_pcm_direct_semaphore_up(dmix, DIRECT_IPC_SEM_CLIENT); free(dmix->bindings);

2 1