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

[alsa-devel] [PATCH] improved snd-aloop quality when using certain samplerates and kernel HZ
by Ahmet İnan 02 Jun '08

02 Jun '08

after using a HZ:=300 kernel for some time now and needing snd-aloop again i found out, that i either had to correct the hardcoded number, or fix the problem permanently, which couses stuttering and other problems. i also removed the SYNC on start code, not just because its more or less useless and brings problems, but ive got a nice idea how to fix this overrun/underrun problem in a much nicer way. so stay tuned for the next patch, until its implemented. this patch here is more or less experimental, id like to hear some feedback. http://www.mathematik.uni-freiburg.de/IAM/homepages/ainan/alsa-driver-1.0.1… Signed-off-by: Ahmet İnan <ainan <at> mathematik.uni-freiburg.de> please also include my email address when responding - i have no intention to enable recieving emails from the list. ahmet -- admin der abteilung für angewandte mathematik, tel. 0761-203-5626

3 16

[alsa-devel] 2.6.26-rc1 regression: ISA DMA broken (bisected)
by Rene Herman 31 May '08

31 May '08

Good day. commit 8779f2fc3b84ebb6c5181fb13d702e9944c16069 "x86: don't try to allocate from DMA zone at first" breaks all of ISA DMA. Or all of ALSA ISA DMA at least. All ISA soundcards are silent following that commit -- no error messages, everything appears fine, just silence. It won't just revert due to 32/64 merge. Rene.

7 32

[alsa-devel] FW: [Alsa-user] raw spdif frame capture
by Brett Andrews 31 May '08

31 May '08

Hi: Anyone have any ideas about the following? As a side note, when I saw raw I don't mean 61937 raw (just preambles and payload), I mean 60958 raw (block sync, payload, VUCP). Thanks, Brett -----Original Message----- From: stan [mailto:ghjeold_i_mwee@cox.net] Sent: Friday, May 30, 2008 18:31 To: Brett Andrews Cc: alsa-user(a)lists.sourceforge.net Subject: Re: [Alsa-user] raw spdif frame capture Brett Andrews wrote: > Hi: > > I would like to perform raw spdif frame capture (all 64-bits, in 2 > 32-bit subframes) using an EMU 1212M under ALSA. Can this be done? > If so, has anyone else already done it? If not, does anyone have any > idea how to do it? EMU has claimed that it is possible with the > hardware, but that the driver would need to support it (windows driver > does not, they didn't know about the ALSA driver). Does the current > emu10k1 driver support this? How would I enter this mode? > > Thanks, > > Brett Andrews > Software Engineer > BSE Reference Software > I haven't got a lot of help for you as I'm not knowledgeable about this but I can give you some suggestions. You could ask you question on alsa-devel mailing list as they know the internals and might be able to answer your question directly. You could look at the alsa driver code. Go to ftp://ftp.alsa-project.org/pub/driver/ and download File:alsa-driver-1.0.16.tar.bz2. <ftp://ftp.alsa-project.org/pub/driver/alsa-driver-1.0.16.tar.bz2> This is the latest official alsa version. Unpack it and then look in "top level"/alsa-kernel/pci/emu10k1. That has the C source.

1 0

[PATCH] ISA: set 24-bit dma_mask for ISA devices.
by Rene Herman 31 May '08

31 May '08

dma_alloc_coherent() on x86 currently takes a passed in NULL device pointer to mean that it should allocate an ISA compatible (24-bit) buffer which is a bit of a hack. The ALSA ISA drivers are the main consumers of this but have a struct device in fact readily available. For the legacy drivers, this sets the device dma_mask in preparation for using the actual device with the DMA API so as to eventually not need the NULL hack in dma_alloc_coherent(). This does not fix a current bug -- 2.6.26-rc1 stumbled over the NULL hack in dma_alloc_coherent() but this has already been fixed in commit 4a367f3a9dbf2e7ffcee4702203479809236ee6e by Takashi Iwai. Signed-off-by: Rene Herman <rene.herman(a)gmail.com> Cc: Bjorn Helgaas <bjorn.helgaas(a)hp.com> Cc: Takashi Iwai <tiwai(a)suse.de> Cc: Alan Cox <alan(a)lxorguk.ukuu.org.uk> --- drivers/base/isa.c | 4 ++++ 1 files changed, 4 insertions(+), 0 deletions(-) diff --git a/drivers/base/isa.c b/drivers/base/isa.c index d222239..efd5775 100644 --- a/drivers/base/isa.c +++ b/drivers/base/isa.c @@ -7,6 +7,7 @@ #include <linux/slab.h> #include <linux/module.h> #include <linux/init.h> +#include <linux/dma-mapping.h> #include <linux/isa.h> static struct device isa_bus = { @@ -141,6 +142,9 @@ int isa_register_driver(struct isa_driver *isa_driver, unsigned int ndev) isa_dev->dev.release = isa_dev_release; isa_dev->id = id; + isa_dev->dev.coherent_dma_mask = DMA_24BIT_MASK; + isa_dev->dev.dma_mask = &isa_dev->dev.coherent_dma_mask; + error = device_register(&isa_dev->dev); if (error) { put_device(&isa_dev->dev); -- 1.5.2.2

1 0

[PATCH] ISA: set 24-bit dma_mask for ISA devices.
by Rene Herman 31 May '08

31 May '08

Set the ISA device dma_mask in preparation for using the actual device with the DMA API. Signed-off-by: Rene Herman <rene.herman(a)gmail.com> --- drivers/base/isa.c | 4 ++++ 1 files changed, 4 insertions(+), 0 deletions(-) diff --git a/drivers/base/isa.c b/drivers/base/isa.c index d222239..efd5775 100644 --- a/drivers/base/isa.c +++ b/drivers/base/isa.c @@ -7,6 +7,7 @@ #include <linux/slab.h> #include <linux/module.h> #include <linux/init.h> +#include <linux/dma-mapping.h> #include <linux/isa.h> static struct device isa_bus = { @@ -141,6 +142,9 @@ int isa_register_driver(struct isa_driver *isa_driver, unsigned int ndev) isa_dev->dev.release = isa_dev_release; isa_dev->id = id; + isa_dev->dev.coherent_dma_mask = DMA_24BIT_MASK; + isa_dev->dev.dma_mask = &isa_dev->dev.coherent_dma_mask; + error = device_register(&isa_dev->dev); if (error) { put_device(&isa_dev->dev); -- 1.5.2.2 --------------050209050208090004020909--

1 0

[PATCH] PNP: set the pnp_card dma_mask for use by ISAPnP cards.
by Rene Herman 30 May '08

30 May '08

dma_alloc_coherent() on x86 currently takes a passed in NULL device pointer to mean that it should allocate an ISA compatible (24-bit) buffer which is a bit of a hack. The ALSA ISA drivers are the main consumers of this but have a struct device in fact readily available. For the PnP drivers, the specific pnp_dev->dev device pointer is not always available at the right time so for now we want to pass the pnp_card->dev instead which is always available. Set its dma_mask in preparation for doing so. This does not fix a current bug -- 2.6.26-rc1 stumbled over the NULL hack in dma_alloc_coherent() but this has already been fixed in commit 4a367f3a9dbf2e7ffcee4702203479809236ee6e by Takashi Iwai. Signed-off-by: Rene Herman <rene.herman(a)gmail.com> Acked-by: Bjorn Helgaas <bjorn.helgaas(a)hp.com> Cc: Takashi Iwai <tiwai(a)suse.de> Cc: Alan Cox <alan(a)lxorguk.ukuu.org.uk> --- drivers/pnp/card.c | 4 ++++ 1 files changed, 4 insertions(+), 0 deletions(-) diff --git a/drivers/pnp/card.c b/drivers/pnp/card.c index a762a41..b00ef10 100644 --- a/drivers/pnp/card.c +++ b/drivers/pnp/card.c @@ -8,6 +8,7 @@ #include <linux/ctype.h> #include <linux/slab.h> #include <linux/pnp.h> +#include <linux/dma-mapping.h> #include "base.h" LIST_HEAD(pnp_cards); @@ -167,6 +168,9 @@ struct pnp_card *pnp_alloc_card(struct pnp_protocol *protocol, int id, char *pnp sprintf(card->dev.bus_id, "%02x:%02x", card->protocol->number, card->number); + card->dev.coherent_dma_mask = DMA_24BIT_MASK; + card->dev.dma_mask = &card->dev.coherent_dma_mask; + dev_id = pnp_add_card_id(card, pnpid); if (!dev_id) { kfree(card); -- 1.5.2.2 --------------050004000406080804070800--

1 0

[PATCH] PNP: set the pnp_card dma_mask for use by ISAPnP cards.
by Rene Herman 30 May '08

30 May '08

This makes the pnp_card->dev available as a DMAable device same as the pnp_dev->dev. Signed-off-by: Rene Herman <rene.herman(a)gmail.com> --- drivers/pnp/card.c | 4 ++++ 1 files changed, 4 insertions(+), 0 deletions(-) diff --git a/drivers/pnp/card.c b/drivers/pnp/card.c index a762a41..b00ef10 100644 --- a/drivers/pnp/card.c +++ b/drivers/pnp/card.c @@ -8,6 +8,7 @@ #include <linux/ctype.h> #include <linux/slab.h> #include <linux/pnp.h> +#include <linux/dma-mapping.h> #include "base.h" LIST_HEAD(pnp_cards); @@ -167,6 +168,9 @@ struct pnp_card *pnp_alloc_card(struct pnp_protocol *protocol, int id, char *pnp sprintf(card->dev.bus_id, "%02x:%02x", card->protocol->number, card->number); + card->dev.coherent_dma_mask = DMA_24BIT_MASK; + card->dev.dma_mask = &card->dev.coherent_dma_mask; + dev_id = pnp_add_card_id(card, pnpid); if (!dev_id) { kfree(card); -- 1.5.2.2 --------------030605020307000902060404--

1 0

Re: [alsa-devel] hdsp rpm support
by Martin Tufnel 30 May '08

30 May '08

Hi Flo That's great news! Unfortunately, I don't have the unit yet so I'm unable to test it for you. However, I'm sure Roman would be very happy to give it a go. Roman? Just to clarify, given the driver is finished but the user tools are still under development, this means that the unit will basically work but not have its full functionality - is this correct? Also, did you use the new patched version of the firmware that Karl worked on? And, when do you think the driver will be incorporated into the main Alsa code branch? Thanks for your work! Regards, Martin On Tue, May 27, 2008 at 1:30 AM, <faber(a)faberman.de> wrote: > Martin, > > > Nice to hear from you. I saw your other posts and had wondered if you > had > > chucked in the towel. I would really like to see the RPM supported as it > > suits my needs exactly. > > RPM support is finished, I just need more time for the new userspace tools > (new totalmix etc.). > > If you want to test the new driver, drop me a note. > > > Flo >

4 9

[alsa-devel] Digital Audio Multiplexer of the i.MX27 processor
by Juergen Beisert 30 May '08

30 May '08

Hi, does anybody understand the DAM unit in the i.MX27 processor? This routing device drivers me crazy, as I do not understand how to route clocks, syncs and the data signals of my internal i2s unit to the processor's pins. All I can see is, when I enable the internal SSI unit in i2s mode, the DMA unit transfers some data into it, but the SSI unit does not shift it out. So everything stops, the DMA timeouts and I cannot hear anything. I can see the external device generates clock and frame signals, but it seems they do not reach the internal SSI unit. Has anybody a working DAM configuration which uses the internal SSI#1 as an i2s slave, an external i2s device connected to the SSI#1 pin group of this processor which acts as a master (I did not find anything in the manual, how the relation between the internal so called port-1 to port-6 at the DAM unit and the 4 external SSI1...SSI4 pin groups are). Means the external i2s device generates the clock and frame signal and the internal SSI#1 unit in i2s mode should use it to send serial sound data to the external device. Juergen -- Dipl.-Ing. Juergen Beisert | http://www.pengutronix.de Pengutronix - Linux Solutions for Science and Industry Handelsregister: Amtsgericht Hildesheim, HRA 2686 Vertretung Sued/Muenchen, Germany Phone: +49-8766-939 228 | Fax: +49-5121-206917-9

3 4

[alsa-devel] ASOC, SPDIF and AC97
by Jon Smirl 29 May '08

29 May '08

I'm back to working on an ASOC driver for the STAC9766 used in the MPC5200 based Efika. I'm having trouble with SPDIF. I can make two devices like this in the codec file. But how do I get the SPDIF device hooked up to the right AC97 slot, 10/11? Are any of the ASOC codecs implementing SPDIF? I also see that the STAC9766 is missing an ac97_patch. From my reading of the datasheet it needs somethings fixed up. Does the ac97 support belong in the PCI directory? It took me a while to locate it while working on ASOC. With a model more like ASOC codecs, the AC97 patches could be pushed into the codec files. static struct snd_soc_dai stac9766_dai[] = { { .name = "STAC9766-Analog", .id = 0, /* stream cababilities */ .playback = { .stream_name = "STAC9766 Analog", .channels_min = 1, .channels_max = 6, .rates = STAC9766_RATES, .formats = SNDRV_PCM_FMTBIT_S16, }, .capture = { .stream_name = "STAC9766 Analog", .channels_min = 1, .channels_max = 2, .rates = STAC9766_RATES, .formats = SNDRV_PCM_FMTBIT_S16, }, /* alsa ops */ .prepare = ac97_analog_prepare, }, { .name = "stac9766-S/PDIF", .id = 1, /* stream cababilities */ .playback = { .stream_name = "STAC9766 Digital", .channels_min = 1, .channels_max = 2, .rates = STAC9766_RATES, .formats = SNDRV_PCM_FMTBIT_S16, }, /* alsa ops */ .prepare = ac97_digital_prepare, }}; -- Jon Smirl jonsmirl(a)gmail.com

2 5