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

[alsa-devel] ASoC: Merging at91 and avr32 dirs - test report
by ext-jukka.hynninen＠vaisala.com 27 Oct '08

27 Oct '08

I tested the patches and got everything working with minor changes. However, there seems to be some problem with PM, occasionally ASoC is stuck with Standby mode (looking at dapm_widgets) when I start the playback. Restarting the player brings the sound back. I'll carry out some further investigation and get back to this. My kernel is 2.6.27-rc3, and machine driver is adapted from playpaq_wm8510.c to run on at91rm9200 board. The SSC peripheral clock was disabled more often than it was enabled, and that catched the bug trap in arch/arm/mach-at91/clock.c. I'm not sure if this was the real problem, but it's the way I managed to solve it. -Jukka diff -uprN a/sound/soc/atmel/atmel_ssc_dai.c b/sound/soc/atmel/atmel_ssc_dai.c --- a/sound/soc/atmel/atmel_ssc_dai.c 2008-10-10 17:23:46.000000000 +0300 +++ b/sound/soc/atmel/atmel_ssc_dai.c 2008-10-10 17:26:06.000000000 +0300 @@ -261,11 +261,11 @@ static void atmel_ssc_shutdown(struct sn spin_lock_irq(&ssc_p->lock); ssc_p->dir_mask &= ~dir_mask; if (!ssc_p->dir_mask) { - /* Shutdown the SSC clock. */ - pr_debug("atmel_ssc_dau: Stopping clock\n"); - clk_disable(ssc_p->ssc->clk); - if (ssc_p->initialized) { + /* Shutdown the SSC clock. */ + pr_debug("atmel_ssc_dai: Stopping clock\n"); + clk_disable(ssc_p->ssc->clk); + free_irq(ssc_p->ssc->irq, ssc_p); ssc_p->initialized = 0; }

3 12

[alsa-devel] [PATCH 1/1] ASoC: Blackfin: update SPORT0 port selector (v2)
by Bryan Wu 27 Oct '08

27 Oct '08

From: Cliff Cai <cliff.cai(a)analog.com> - Setting the TFS pin selector for SPORT 0 based on whether the selected port id F or G. If the port is F then no conflict should exist for the TFS. When Port G is selected and EMAC then there is a conflict between the PHY interrupt line and TFS. Current settings prevent the conflict by ignoring the TFS pin when Port G is selected. This allows both ssm2602 using Port G and EMAC concurrently. - some code cleanup Signed-off-by: Cliff Cai <cliff.cai(a)analog.com> Signed-off-by: Bryan Wu <cooloney(a)kernel.org> --- sound/soc/blackfin/bf5xx-i2s.c | 34 ++++++++++++++++++++++------------ 1 files changed, 22 insertions(+), 12 deletions(-) diff --git a/sound/soc/blackfin/bf5xx-i2s.c b/sound/soc/blackfin/bf5xx-i2s.c index 827587f..e020c16 100644 --- a/sound/soc/blackfin/bf5xx-i2s.c +++ b/sound/soc/blackfin/bf5xx-i2s.c @@ -70,12 +70,24 @@ static struct sport_param sport_params[2] = { } }; -static u16 sport_req[][7] = { - { P_SPORT0_DTPRI, P_SPORT0_TSCLK, P_SPORT0_RFS, - P_SPORT0_DRPRI, P_SPORT0_RSCLK, 0}, - { P_SPORT1_DTPRI, P_SPORT1_TSCLK, P_SPORT1_RFS, - P_SPORT1_DRPRI, P_SPORT1_RSCLK, 0}, -}; +/* + * Setting the TFS pin selector for SPORT 0 based on whether the selected + * port id F or G. If the port is F then no conflict should exist for the + * TFS. When Port G is selected and EMAC then there is a conflict between + * the PHY interrupt line and TFS. Current settings prevent the conflict + * by ignoring the TFS pin when Port G is selected. This allows both + * ssm2602 using Port G and EMAC concurrently. + */ +#ifdef CONFIG_BF527_SPORT0_PORTF +#define LOCAL_SPORT0_TFS (P_SPORT0_TFS) +#else +#define LOCAL_SPORT0_TFS (0) +#endif + +static u16 sport_req[][7] = { {P_SPORT0_DTPRI, P_SPORT0_TSCLK, P_SPORT0_RFS, + P_SPORT0_DRPRI, P_SPORT0_RSCLK, LOCAL_SPORT0_TFS, 0}, + {P_SPORT1_DTPRI, P_SPORT1_TSCLK, P_SPORT1_RFS, P_SPORT1_DRPRI, + P_SPORT1_RSCLK, P_SPORT1_TFS, 0} }; static int bf5xx_i2s_set_dai_fmt(struct snd_soc_dai *cpu_dai, unsigned int fmt) @@ -98,23 +110,21 @@ static int bf5xx_i2s_set_dai_fmt(struct snd_soc_dai *cpu_dai, ret = -EINVAL; break; default: + printk(KERN_ERR "%s: Unknown DAI format type\n", __func__); ret = -EINVAL; break; } switch (fmt & SND_SOC_DAIFMT_MASTER_MASK) { - case SND_SOC_DAIFMT_CBS_CFS: - ret = -EINVAL; - break; - case SND_SOC_DAIFMT_CBM_CFS: - ret = -EINVAL; - break; case SND_SOC_DAIFMT_CBM_CFM: break; + case SND_SOC_DAIFMT_CBS_CFS: + case SND_SOC_DAIFMT_CBM_CFS: case SND_SOC_DAIFMT_CBS_CFM: ret = -EINVAL; break; default: + printk(KERN_ERR "%s: Unknown DAI master type\n", __func__); ret = -EINVAL; break; } -- 1.5.6

3 2

[alsa-devel] Only one element for multichannel mixer controls please!
by Lennart Poettering 27 Oct '08

27 Oct '08

Heya! It seems that quite a few ALSA drivers for multichannel sound cards export three seperate stereo mixer controls to control front, rear and center/lfe independantly. That sucks because a client (such as PulseAudio) cannot make use of this. Instead they should export a single 6ch mixer control! The "amixer scontents" output looks very strange for these drivers since it lists a "Rear" control that as a "Front Left" and a "Front Right" channel. So, what is it now: front or rear? Is there any reason for this current driver behaviour? I mean, the mixer knows channel ids like SND_MIXER_SCHN_REAR_LEFT perfectly well. Or is it that those devices have some devices joined and this cannot be expressd with a single boolean "joined" for each control? Please enlighten me! Lennart -- Lennart Poettering Red Hat, Inc. lennart [at] poettering [dot] net ICQ# 11060553 http://0pointer.net/lennart/ GnuPG 0x1A015CC4

3 7

[alsa-devel] patch for alsa-info.sh to quote [ -d $SYSFS ]
by Luis Yanes 27 Oct '08

27 Oct '08

Found a couple of bugs in http://www.alsa-project.org/alsa-info.sh while running it in my system. * old uname <= 2.0.11 doesn't accept -o argument * $SYSFS is not quoted while checking if directory exist and fails if empty Attached is a small patch for the first of them, but think that all variables also should be quoted to avoid future problems. Regards. --- alsa-info.sh.orig Sat Oct 25 14:16:43 2008 +++ alsa-info.sh Sat Oct 25 14:18:44 2008 @@ -373,7 +373,7 @@ echo "" >> $FILE fi -if [ -d $SYSFS ] +if [ -d "$SYSFS" ] then echo "!!Loaded sound module options" >> $FILE echo "!!--------------------------" >> $FILE

2 1

[alsa-devel] using dshare plugin to create multiple independent audio outputs for multiseat out of 7.1 internal audio card
by Jelle de Jong 27 Oct '08

27 Oct '08

Hello everybody, I am looking for ways to get good cheap audio outputs per user for multiseat systems. A nice good way would be to be able to use the available resources of motherboards than now come often with 8-channel audio cards with 6 or more audio outputs ... (6 users) I have seen something about dshare plugin that might be able to do this, but I have no idea how this works or how and if it is possible to configure this for multiple users? Would somebody be able to do some experimenting and maybe make some examples with some .asoundrc quotes? Chipset integrated by Realtekr ALC888/ALC888T - Flexible 8-channel audio with jack sensing - Compliant with Azalia 1.0 Spec Any ideas, solutions? Thanks in advance, Jelle

1 0

[alsa-devel] [PATCH1/4] jack: lineout support to jack abstraction layer
by Matthew Ranostay 27 Oct '08

27 Oct '08

This patch introduces support for reporting SW_LINEOUT_INSERT detection events via the jack abstraction layer. Also adds a SND_JACK_LINEOUT define to the input system header. Signed-off-by: Matthew Ranostay <mranostay(a)embeddedalley.com> --- diff --git a/include/linux/input.h b/include/linux/input.h index b86fb55..fa9127d 100644 --- a/include/linux/input.h +++ b/include/linux/input.h @@ -657,6 +657,7 @@ struct input_absinfo { #define SW_RADIO SW_RFKILL_ALL /* deprecated */ #define SW_MICROPHONE_INSERT 0x04 /* set = inserted */ #define SW_DOCK 0x05 /* set = plugged into dock */ +#define SW_LINEOUT_INSERT 0x06 /* set = inserted */ #define SW_MAX 0x0f #define SW_CNT (SW_MAX+1) diff --git a/include/sound/jack.h b/include/sound/jack.h index b1b2b8b..7cb25f4 100644 --- a/include/sound/jack.h +++ b/include/sound/jack.h @@ -35,6 +35,7 @@ enum snd_jack_types { SND_JACK_HEADPHONE = 0x0001, SND_JACK_MICROPHONE = 0x0002, SND_JACK_HEADSET = SND_JACK_HEADPHONE | SND_JACK_MICROPHONE, + SND_JACK_LINEOUT = 0x0004, }; struct snd_jack { diff --git a/sound/core/jack.c b/sound/core/jack.c index bd2d9e6..4978db1 100644 --- a/sound/core/jack.c +++ b/sound/core/jack.c @@ -102,6 +102,9 @@ int snd_jack_new(struct snd_card *card, const char *id, int type, if (type & SND_JACK_HEADPHONE) input_set_capability(jack->input_dev, EV_SW, SW_HEADPHONE_INSERT); + if (type & SND_JACK_LINEOUT) + input_set_capability(jack->input_dev, EV_SW, + SW_LINEOUT_INSERT); if (type & SND_JACK_MICROPHONE) input_set_capability(jack->input_dev, EV_SW, SW_MICROPHONE_INSERT); @@ -153,6 +156,9 @@ void snd_jack_report(struct snd_jack *jack, int status) if (jack->type & SND_JACK_HEADPHONE) input_report_switch(jack->input_dev, SW_HEADPHONE_INSERT, status & SND_JACK_HEADPHONE); + if (jack->type & SND_JACK_LINEOUT) + input_report_switch(jack->input_dev, SW_LINEOUT_INSERT, + status & SND_JACK_LINEOUT); if (jack->type & SND_JACK_MICROPHONE) input_report_switch(jack->input_dev, SW_MICROPHONE_INSERT, status & SND_JACK_MICROPHONE);

2 1

[alsa-devel] When running aplay, reported:ALSA lib pcm.c:2202:(snd_pcm_open_noupdate) Unknown PCM plughw:0, 0
by zhangal 26 Oct '08

26 Oct '08

Hi, everybody I am dealing with OMAP730 alsa driver based on kernel 2.6.25. The alsa core drivers are coming from linux-2.6.25/sound and I wrote my own alsa driver for OMAP730. Now I can insmod my driver correctly and the modules I installed are: Module Size Used by Not taintedsnd_omap_alsa_pers2 15868 0snd_pcm 66660 1 snd_omap_alsa_pers2snd_timer 19492 1 snd_pcmsnd 45972 3 snd_omap_alsa_pers2,snd_pcm,snd_timersnd_page_alloc 6152 1 snd_pcmsoundcore 6020 1 sndAnd device nodes are made automatically [root@/mnt/temp]#ls -l /dev/snd/crw-rw-r-- 1 root root 116, 5 Jan 1 00:16 controlC0crw-rw-r-- 1 root root 116, 4 Jan 1 00:16 pcmC0D0ccrw-rw-r-- 1 root root 116, 3 Jan 1 00:16 pcmC0D0pcrw-rw-r-- 1 root root 116, 2 Jan 1 00:16 timerIt seems the necessary nodes are all there, but after I set the ALSA_CONFIG_PATH=/mnt/temp and then run aplay I got errosrs: [root(a)/mnt/temp]#./aplay -D plughw:0,0 test.wavALSA lib pcm.c:2202:(snd_pcm_open_noupdate) Unknown PCM plughw:0,0aplay: main:583: audio open error: No such file or directory The PCM device can not be recognized. What's happening here? Did anyboady meet this problem before? NOTE: The aplay is compiled from alsa-utils-1.0.18rc3.tar.bz2 and alsa-lib-1.0.18rc3.tar.bz2 Thanks a lot for any help! Another question, why can not I see this email I post? 用MSN有问题？客服机器人小美帮你忙！立刻和小美聊天！ _________________________________________________________________ 一边聊天一边快速搜索，并把结果共享给好友，立刻试试！ http://im.live.cn/Share/18.htm

1 0

[alsa-devel] When running aplay, reported:ALSA lib pcm.c:2202:(snd_pcm_open_noupdate) Unknown PCM plughw:0, 0
by zhangal 26 Oct '08

26 Oct '08

Hi, everybody I am dealing with OMAP730 alsa driver based on kernel 2.6.25. The alsa core drivers are coming from linux-2.6.25/sound and I wrote my own alsa driver for OMAP730. Now I can insmod my driver correctly and the modules I installed are: Module Size Used by Not taintedsnd_omap_alsa_pers2 15868 0snd_pcm 66660 1 snd_omap_alsa_pers2snd_timer 19492 1 snd_pcmsnd 45972 3 snd_omap_alsa_pers2,snd_pcm,snd_timersnd_page_alloc 6152 1 snd_pcmsoundcore 6020 1 snd And device nodes are made automatically [root@/mnt/temp]#ls -l /dev/snd/crw-rw-r-- 1 root root 116, 5 Jan 1 00:16 controlC0crw-rw-r-- 1 root root 116, 4 Jan 1 00:16 pcmC0D0ccrw-rw-r-- 1 root root 116, 3 Jan 1 00:16 pcmC0D0pcrw-rw-r-- 1 root root 116, 2 Jan 1 00:16 timer It seems the necessary nodes are all there, but after I set the ALSA_CONFIG_PATH=/mnt/temp and then run aplay I got errosrs: [root(a)/mnt/temp]#./aplay -D plughw:0,0 test.wavALSA lib pcm.c:2202:(snd_pcm_open_noupdate) Unknown PCM plughw:0,0aplay: main:583: audio open error: No such file or directory The PCM device can not be recognized. What's happening here? Did anyboady meet this problem before? NOTE: The aplay is compiled from alsa-utils-1.0.18rc3.tar.bz2 and alsa-lib-1.0.18rc3.tar.bz2. _________________________________________________________________ MSN 中文网，最新时尚生活资讯，白领聚集门户。 http://cn.msn.com

1 0

[alsa-devel] volume scaling of usb audio class headset
by Jelle de Jong 25 Oct '08

25 Oct '08

Hello everybody, I got a question, I got a few usb headsets that seem to apply to the usb audio class and the volume scale is way to big with alsa. with the control on 10 of the 100 you are almost getting deaf. So my question is how does alsa make an scaling for such devices and how to fix it so that the full range can be used in a normal volume spectrum. Thank in advance, Jelle

2 4

Re: [alsa-devel] multiseat and alsa audio systems (usb headsets and usb audio adapters)
by Jelle de Jong 25 Oct '08

25 Oct '08

Sean McNamara wrote: > On Wed, Oct 22, 2008 at 1:48 PM, Jelle de Jong > <jelledejong(a)powercraft.nl> wrote: >> Hello everybody, >> >> I have a four to eighth muliseat debian linux system here and it is >> missing sound for the users. I was hoping the alsa team can help me with >> this issue. > > All sound issues on Linux are extremely application-specific. Getting > sound to work without any specific application in mind is asking for > trouble, because there is no single configuration of the sound stack > (which, if you expand into historical sound APIs and servers, contains > about 20 different ways to play sound) that will satisfy any > application without further configuration. > > Since this is not a really well-formed question, I will proceed with > the assumption that you want to be able to run, for example, > > aplay /usr/share/sounds/pop.wav > > in the console, and have it produce sound in the "appropriate" > headset. Here's how you proceed: > > 1. Each person on the multiseat box must have their own UNIX user account. > 2. Each user account must have an ~/.asoundrc file. > 3. Each ~/.asoundrc file must redefine the "default" device. How you > redefine it depends on a lot of things: > (a) Do you want _direct_ hardware access to the sound card, i.e. one > application at a time? > (b) Do you want to use ALSA's built-in software mixing, i.e. dmix? > (c) How many channels? > (d) Do you want to use PulseAudio? > (e) Do you want to use JACK? > (f) For each USB headset, what is its corresponding "raw device > string"? This will be something like hw:n, where n is a number > starting from 0, depending on the order in which the USB drivers > initialize each USB controller. > > All of the above questions, and others, will determine exactly how > each user configures their ~/.asoundrc file. > > The *extremely naive* (not recommended) example of an ~/.asoundrc is like: > > pcm.!default { > card 3 > } > > to have ALSA clients play sound, by default, to the fourth sound > device that happened to be initialized. > >> I have usb headsets and usb audio devices and all users have there own >> usb hub. There are no internal audio cards in the multiseat server. >> >> How can we configure an system that the user can listen to audio only to >> the devices connected to his usb hub. > > Well, this is guaranteed by design, isn't it? Without physical access > to someone else's headset, how would I get access to the audio streams > being played to that headset? I don't think this really expresses what > your problem is. > > If we flip your question around, it might be a little more > interesting: "How can we configure a system so that each user's > applications will only play audio to that user's corresponding > headset?" > > You can interpret this question in two ways: > 1. "How can we _prevent_ users from playing sound to each other's > sound cards?" [mutually untrust[ed/ing] users] > or > 2. "How can we configure the default settings so that, if untampered > with, a user's applications will play sound to that user's own headset > and not anyone else's?" [mutually trust[ed/ing] users] > > The lack of hardware mixing actually comes back to being a security > benefit to user space control in this kind of situation. Recall that > if I run > > aplay --device=hw:0 /usr/share/sounds/pop.wav > > then as long as the aplay program is playing sound to hw:0, it is > *impossible* (short of some really devious hacking in alsa-lib or the > kernel) for another application -- from this user, or another -- to > also play sound to hw:0 at the same time. I'll call this claim "No > Native SW Mixing". > > Now, let's look at what is required to satisfy the question in each of > the two above cases. > > Trusted: > 1. We know that users aren't going to maliciously try and hurt one > another's ears by setting someone else's mixer really loud and playing > static to them. > 2. We know that users won't try to tamper with eachother's processes > or configuration files; once things are configured correctly, it'll > stay that way. > 3. By 'No Native SW Mixing', we know that users can *theoretically* > hog another user's sound device whenever that user has zero > applications currently using it. > 4. Since users trust each other, they won't do this. > 5. We can use something like dmix, or just use hw:0 if users don't > need simultaneous app output, and things will be fine. > 6. dmix is a viable option to implement software mixing. > 7. PulseAudio is also a viable option to implement software mixing. > > Untrusted: > 1. Users may want to maliciously try and hurt one another's ears by > setting someone else's mixer really loud and playing static to them. > 2. Users may try to tamper with eachother's processes or configuration > files; once things are configured correctly, it could get messed up > again. [There's not much you can do to prevent this ... at least not > based on existing open source tools.] > 3. By 'No Native SW Mixing', we know that users can *theoretically* > hog another user's sound device whenever that user has zero > applications currently using it. > 4. Since users do not trust each other, there is potential for 3 to happen. > 5. We must use 'No Native SW Mixing' to our advantage, to create a > walled garden around each user's sound experience. We need a process > that, once started by a user, will permanently "hog" the sound card > that user wants to use. This process should, ideally, allow other > processes run by that user (and by that user only) to access their USB > headset for output or input. We need a "gatekeeper" that is sensitive > to the context in which an app is being run. > 6. dmix is a NOT viable option to implement software mixing, because: > (a) Once all dmix applications close their streams, the audio device > hw:n is available, and some malicious user can decide to acquire it, > abuse it, and prevent its rightful user from accessing it with his own > applications. > (b) dmix does not restrict users from outputting sound based on their > UID or session. It is NOT a gatekeeper, just an open gate. > 7. PulseAudio is [perhaps the best] viable solution to implement > software mixing for each respective user. It is also a viable solution > to preventing users from taking control of one another's sound > devices. > > Configuring pulseaudio for a multi-soundcard multi-user system is out > of the scope of this mailing list, but suffice it to say that it can > be done. You will want to run one PulseAudio daemon per user, and each > daemon will hold exclusive control over exactly one USB headset. Each > daemon will only accept clients' requests for audio I/O from the user > who started the daemon. Do make sure that you disable > module-suspend-on-idle, or PulseAudio will actually give up the sound > device after a period of inactivity, making it insecure in an > untrusted environment. > > BTW, if this project is for a commercial interest, you usually pay > someone for this kind of in-depth analysis. If you're that someone, > you might want to read up on some of the underlying technologies so > that you can develop this sort of reasoning on your own. I can > envision a very real situation for both the trusted and the untrusted > environment, so there is definitely a demand for this kind of > specialist. Trusted environments are popular at workplaces, and > untrusted multi-seat boxes are popular at computer labs, public > libraries, etc. > >> Any help is really appreciated. > > Please let me know if this information was helpful -- it will help me > gauge, in turn, whether I should spend my time writing up these sorts > of answers on the ML. FWIW, I searched around for existing articles > touching this subject, but I couldn't find anyone who addresses this > specific issue accurately or in enough detail. > > Sean > > P.S. - I once spoke to a user on IRC who was having intermittent > problems with multiple USB headsets. It turns out that the USB > controllers in the computer didn't have enough bandwidth, or power (or > both) to allow all of the headsets to play at once. If, after > configuring, you run into issues where only so many users can play > sound at once, then you should invest in additional PCI or > (preferably) PCI-Express USB controllers. Note that adding hubs > upstream of a USB controller does absolutely nothing to lessen the > load on the USB controllers that are integrated into your motherboard. > >> Thank in advance, >> >> Jelle Thank you Sean, this is by far the most extensive response i received in months with an "open" question on an mailinglist, this really is a good character, that I will reward if you sent an paypal address :-p. I have extensive experience configuring alsa and usb headset, little new info was delivered for me but i think others will really like your response too. My main issue is how to start alsa when there are no audio cards on the system using debian sid? so i can use bluetooth or hotplug usb audio devices...anybody? Then I think it will become an udev issue to regulate a fixed group and permissions for usb audio devices. I was kind of hoping somebody had done this kind of udev ruling for usb audio devices and can provide some examples this will save me time...anybody? PS. I have also noticed usb audio problems (also posted them to irc maybe 1 year ago) in the past with usb hubs and other kinds of things, these things can brake an design or make it:-p So thank you very much for this great response, and keep up doing this kind of work. Kind regards, Jelle

3 5