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

[alsa-devel] Altec Lansing FX5051 mixer
by Jeremy Nickurak 04 Apr '08

04 Apr '08

I recently purchased an Altec Lansing USB Surround speaker set. (It's a set of 5.1 speakers, with a built-in USB sound card). I've got about a week before the return policy expires and I'd have to return it. The mixer doesn't work at all w/linux kernel 2.6.22, everything is locked at 100% volume, which is pretty unhelpful, as it's the only way to adjust the volume. (no analog controls). Also, the digital control panel locks up when the speakers power up, further preventing any access to the volume controls. The device works out-of-the-box without any drivers under XP, so I have to so-far assume that alsa's usb-audio is missing something. Any thoughts as to what could be wrong? I'm more than happy to prod the device and submit any information I can extract about it, or even potentially opening the device up for remote access if a reputable developer is interested in examining it. -- Jeremy Nickurak -= Email/Jabber: atrus(a)rifetech.com =-

3 4

Re: [alsa-devel] + es1968-fix-jitter-on-some-maestro-cards.patch added to -mm tree
by Rene Herman 03 Apr '08

03 Apr '08

On 03-04-08 20:54, akpm(a)linux-foundation.org wrote: > The patch titled > es1968: fix jitter on some maestro cards > has been added to the -mm tree. Its filename is > es1968-fix-jitter-on-some-maestro-cards.patch [ ... ] > Subject: es1968: fix jitter on some maestro cards > From: Andreas Mueller <andreas(a)stapelspeicher.org> > > This patch suppresses jitter on several Maestro cards in stereo mode (ALSA of > course). > > The patch is also incorporated in the *BSD drivers where I "ported" it from. > > Without this patch most of the stereo audio gets out of sync and really > distorted (oss-emulation with mplayer at 48000khz worked somehow). > > Cc: Rene Herman <rene.herman(a)keyaccess.nl> > Cc: Jaroslav Kysela <perex(a)suse.cz> > Cc: Takashi Iwai <tiwai(a)suse.de> > Signed-off-by: Andrew Morton <akpm(a)linux-foundation.org> > --- Tested-By: Rene Herman <rene.herman(a)gmail.com> on a TerraTec DMX (ESS Canyon3D, ES1970MS-3D) which doesn't need this but doesn't seem to be suffering from it either. No idea about this otherwise. > sound/pci/es1968.c | 22 +++++++++++++++++++++- > 1 file changed, 21 insertions(+), 1 deletion(-) > > diff -puN sound/pci/es1968.c~es1968-fix-jitter-on-some-maestro-cards sound/pci/es1968.c > --- a/sound/pci/es1968.c~es1968-fix-jitter-on-some-maestro-cards > +++ a/sound/pci/es1968.c > @@ -1815,6 +1815,23 @@ snd_es1968_pcm(struct es1968 *chip, int > > return 0; > } > +/* > + * suppress jitter on some maestros when playing stereo > + */ > +static void snd_es1968_suppress_jitter(struct es1968 *chip, struct esschan *es) > +{ > + unsigned int cp1; > + unsigned int cp2; > + unsigned int diff; > + > + cp1 = __apu_get_register(chip, 0, 5); > + cp2 = __apu_get_register(chip, 1, 5); > + diff = (cp1 > cp2 ? cp1 - cp2 : cp2 - cp1); > + > + if (diff > 1) { > + __maestro_write(chip, IDR0_DATA_PORT, cp1); > + } > +} > > /* > * update pointer > @@ -1936,8 +1953,11 @@ static irqreturn_t snd_es1968_interrupt( > struct esschan *es; > spin_lock(&chip->substream_lock); > list_for_each_entry(es, &chip->substream_list, list) { > - if (es->running) > + if (es->running) { > snd_es1968_update_pcm(chip, es); > + if (es->fmt & ESS_FMT_STEREO) > + snd_es1968_suppress_jitter(chip, es); > + } > } > spin_unlock(&chip->substream_lock); > if (chip->in_measurement) { Rene.

1 0

[alsa-devel] HDA-Intel ALC880, fujitsu siemens amilo PI1536 and flavours
by Luca Bonora 03 Apr '08

03 Apr '08

Hello developers. I've got a problem with my laptop, I've asked help on alsa-user and now I have a request for you (if it's possible). For a year I tried to use my microphone unsuccessfully. Now I've found a solution, that is to use the flavour "6stack"/"6stack-digout" in place of the flavour "fujitsu". I've read the ALSA-configuration.txt and fujitsu is properly the flavour for _my_ laptop but with 6stack-digout the microphone works and the volume control does not work. Is it possible to 'merge' the two flavours to have both microphone and volume control working? Can I ask it to you? Thank you for your help! Luca

1 0

[alsa-devel] [PATCH] snd_usb_caiaq: fix potential lockups locking
by Daniel Mack 03 Apr '08

03 Apr '08

Hi, attached is a patch for snd_usb_caiaq which fixes system potential lockups when stoping and restarting the stream very quickly multiple times in a row which is what some players do when the user drags the song position slider. Also, it seems that snd_pcm_period_elapsed() must not be called when holding a spinlock? The documentation[*], however, doesn't state that. As this fixes an annoying bug, I would appreciate seeing that one being pushed into 2.6.25. Still possible? Thanks and best regards, Daniel [*] http://www.alsa-project.org/~tiwai/writing-an-alsa-driver/x773.htm#PCM-INTE… ---- Subject: [PATCH] snd_usb_caiaq: fix potential lockups This patch fixes potential lockups in snd_usb_caiaq by refining the locking mechanims and by using usb_kill_urb() in favor to usb_unlink_urb(). Signed-off-by: Daniel Mack <daniel(a)caiaq.de>

1 0

[alsa-devel] Problems in writing test apps
by haoshun 03 Apr '08

03 Apr '08

Hi: sorry,forget to add the subject right now... I'm confused by a problem when i modify a test application "alsa-lib-1.0.13/test/control.c". I wanna use the structure "snd_ctl_elem_value_t",but when i write like this: snd_ctl_elem_value_t aaa; there will be an error: storage size of 'aaa' isn't known while snd_ctl_elem_value_t *aaa; makes no errors. But i can't change it directly such as: aaa->id=test_id ; //test_id is defined before cause it will bring an error: dereferencing pointer to incomplete type I think i should use the function like "snd_ctl_elem_info_set_id",but i just want to know why,i don't think it disobeys the C syntax.Is there something different in the ALSA making procedure?or Makefile? haoshun 2008-04-03

2 1

[alsa-devel] (no subject)
by 郝舜 03 Apr '08

03 Apr '08

Hi: I'm confused by a problem when i modify a test application "alsa-lib-1.0.13/test/control.c". I wanna use the structure "snd_ctl_elem_value_t",but when i write like this: snd_ctl_elem_value_t aaa; there will be an error: storage size of 'aaa' isn't known while snd_ctl_elem_value_t *aaa; makes no errors. But i can't change it directly such as: aaa->id=test_id ; //test_id is defined before cause it will bring an error: dereferencing pointer to incomplete type I think i should use the function like "snd_ctl_elem_info_set_id",but i just want to know why,i don't think it disobeys the C syntax.Is there something different in the ALSA making procedure?or Makefile? haoshun 2008-04-03

2 1

[alsa-devel] ASoC for TI OMAP - Multiformat ASoC DAI link driver?
by Jarkko Nikula 03 Apr '08

03 Apr '08

Currently in ASoC v1 we have one DAI driver per one format? E.g. separate drivers for I2S, AC97, etc and type field in cpu_dai structure is not a bit field or at least not used such way in soc-core.c and DAI link drivers. struct snd_soc_cpu_dai pxa_i2s_dai = { ... .type = SND_SOC_DAI_I2S, ... I looked shortly asoc-v2-dev branch and now this type field is gone. Does it mean that there you can have DAI link driver which supports multiple formats in set_fmt callback? I'm asking this since McBSP (Multichannel Buffered Serial Port) found in OMAP processors can be configured to almost any imaginable format and IMO it doesn't make a sense to have separate drivers for each of them if there is a difference only in few configuration bits. -- Jarkko

2 2

[alsa-devel] ASoC for TI OMAP - alsa-devel submission?
by Jarkko Nikula 03 Apr '08

03 Apr '08

I've been doing generic ASoC drivers for Texas Instruments OMAP processors and I recently released the first version on linux-omap mailing list: http://marc.info/?l=linux-omap&m=120643770810683&w=2 http://marc.info/?l=linux-omap&m=120643766610623&w=2 Currently patch tries to cover OMAPs from 1x10 to 2420 and is tested on Nokia N810 having OMAP2420 and TLV320AIC33 codec. I'm going to release it here also but there are few issues I would like to discuss before it: - McBSP used in OMAP2430 and OMAP3430 are bit different than other 1510-2420 OMAPs and that support we have currently missing in linux-omap either. However, changes to my drivers should be quite minimal in order to support them. E.g. base address definitions and different DMA data type. - Solving the channel synchronization problem might require API change to linux-omap McBSP driver. - ASoC v2 considerations? Like multiformat DAI. - Multiformat McBSP DAI link driver (I'll send an another mail on that). So what I mean that should I post the patch like as it now, rebased to dev branch of linux-2.6-asoc tree and with some minor changes, or wait a bit when all linux-omap and ASoC v2 evolve? What you think? -- Jarkko

2 2

[alsa-devel] DMIX and Alsa Drivers
by Barclay, Bruce 03 Apr '08

03 Apr '08

I wrote an Alsa driver with copy callbacks and it worked. Later read that you can use copy callbacks if you want to use dmix so I rewrote it to not use copy callbacks. I don't see much documentation on dmix (/etc/asound.conf). When I put dmix in there, I can run two versions but the framework never updates the application pointer so I get no data. I take the dmix out and it works fine. No clue on what to do. Bruce

1 0

Re: [alsa-devel] PXA2xx/3xx AC97 Driver(s)
by Mark Brown 02 Apr '08

02 Apr '08

On Mon, Mar 24, 2008 at 12:38:00PM +0000, Oliver Ford wrote: > Is there any work currently under way on an AC97 driver for the PXA3xx? There is PXA3xx AC97 support present in the ASoC tree: git://opensource.wolfsonmicro.com/linux-2.6-asoc It's under the asoc-v2-dev branch at the minute and is probably only done for the ASoC AC97 driver, I'd need to check. The main reason it's only there is that it depends on the ARM architecture changes that you identified (which are also applied on the asoc-v2-dev branch) and it makes life easier to manage the cross-tree changes in only one tree. All the ARM architecture changes have been submitted and marked as applied in the patch system so should hopefully appear in Linus' kernel early in the 2.6.26 cycle. Once this has happened I will submit the AC97 driver PXA3xx support. > I want to get the touch screen working on my iPAQ 214, which uses the > PXA310. It's a WM97xx chip on the AC97 interface. I'm not really too I know that there are a number of users currently using the tree for that use case so the asoc-v2-dev branch should hopefully work for you. If you run into trouble please let me know. > include/asm-arm/arch-pxa/pxa3xx-regs.h). Does the pxa310 require > anything special like this or should just setting the cold-reset in > the AC97 GCR work? It also doesn't support the use of interrupts during reset operations, requiring another special case, but I think that's about it. > The Wolfson Microelectronics open-source page indicates that work is on > going with the 3xx driver but there doesn't seem to be anything more > than the pxa2xx driver in their source tree. Does anyone know how active > / close to producing anything this is? Like I say, it's there. The changes are fairly straightforward and should be easy to backport to whatever kernel you need - if you need help identifying what needs merging over please just ask. > More generally, I'm a little confused as to why there is both the > standard (sound/arm/pxa2xx-ac97.c) and SoC (sound/soc/pxa/pxa2xx-ac97) > driver. Is one of these obsolete now or are they both still in > development? If guessing, I'd say the SoC driver is now the one to use The SoC driver is generally preferable, though it requires a bit more work to use (since you have to write a platform driver to use it). Both are still maintained. SoC offers better power management and support for a wider range of board configurations, especially those that also have non-AC97 interfaces (such as the I2S interface on the WM97xx parts). > but am not sure. Compiling either gives the warning "'pxa_set_cken' is > deprecated". I suspect calling this won't work for the pxa310 since it's This is also fixed in the patches currently queued in the ARM tree - the drivers have been converted to use the clk_() API. > clocks are different, but given that I'm booting linux from windows > (which will leave the clock on) and don't particularly care about > suspend/resume, should not being able to switch it off be a problem? The cken calls should actually work fine.

2 3