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

[alsa-devel] Monotonic timestamps
by Lennart Poettering 21 Apr '08

21 Apr '08

Hey! I saw that ALSA 1.0.16 claims to support monotonic timestamps. I couldn't figure out however, how they are supposed to work. From the sources I only could figure out that they are enabled if a) the libc knows CLOCK_MONOTONIC a) the kernel supports CLOCK_MONOTONIC, b) the ALSA kernel code support timestamps this way. That's at least how I read this code from pcm_hw.c: <snip> #if defined(HAVE_CLOCK_GETTIME) && defined(CLOCK_MONOTONIC) if (SNDRV_PROTOCOL_VERSION(2, 0, 9) <= ver) { struct timespec timespec; if (clock_gettime(CLOCK_MONOTONIC, &timespec) == 0) { int on = SNDRV_PCM_TSTAMP_TYPE_MONOTONIC; if (ioctl(fd, SNDRV_PCM_IOCTL_TTSTAMP, &on) < 0) { ret = -errno; SNDMSG("TTSTAMP failed\n"); return ret; } monotonic = 1; } } #endif else if (SNDRV_PROTOCOL_VERSION(2, 0, 5) <= ver) { int on = 1; if (ioctl(fd, SNDRV_PCM_IOCTL_TSTAMP, &on) < 0) { ret = -errno; SNDMSG("TSTAMP failed\n"); return ret; } } </snip> The problem with this is that there seems to be no way to determine from an application if monotonic timestamps are enabled in an snd_pcm_t or not, ALSA just switches over to them, making the timestamps relatively useless, because we cannot reliable relate them to timestamps we query from the kernel ourselves -- because we just don't know if we need to use CLOCK_MONOTONIC or CLOCK_REALTIME. I find it very strange that ALSA just switches to monotonic timestamps just like that, anyway. Programs written for wallclack timestamps will break if they run on a system where ALSA uses monotonic timestamps! There's a function missing that enables monotonic timestamps explicitly, or at least one that can be used to query if they are monotonic or not. Could anybody please explain the difference between status->tstamp and status->trigger_tstamp for me, please? The doxygen docs are bit too terse on this, I fear. Oh, and the code I pasted above will not compile if the #ifdef check fails, because of the "else". The "else" should be moved inside of #ifddef block. Lennart -- Lennart Poettering Red Hat, Inc. lennart [at] poettering [dot] net ICQ# 11060553 http://0pointer.net/lennart/ GnuPG 0x1A015CC4

3 8

[alsa-devel] snd_hda_intel locking up on VIA CX700M2 with VT1708A codec
by Simon Farnsworth 21 Apr '08

21 Apr '08

Hello, I'm trying to work out what's going wrong with the HDA controller in our VIA CX700M2 board; there's a full bug report at https://bugtrack.alsa-project.org/alsa-bug/view.php?id=3910, but briefly, I'm seeing it lock up and refuse to DMA after long enough transferring audio data. Does anyone have any ideas that would help me track down this lockup and find a workaround? -- Thanks, Simon Farnsworth

1 2

[alsa-devel] [PATCH] asoc tlv320aic33: skip usage of PLL in some cases
by Daniel Mack 19 Apr '08

19 Apr '08

This patch makes the tlv320aic33 driver skip the initialisation of the PLL in case the sysclk is 256 * samplerate. Had to do some minor refactoring too - the check whether a sysclk set by set_sysclk() is valid is now done in set_hw_params(). Signed-off-by: Daniel Mack <daniel(a)caiaq.de>

3 13

[alsa-devel] Patchmix-style application for EMU cards
by Camilo Polymeris 18 Apr '08

18 Apr '08

Hello I am working on a graphical mixing/routing application for the Emu10k series of semi-pro soundcards, but I am having trouble figuring out the routing mechanism of the driver, specially the "Multichannel PCM" part. Is there any technical documentation on this card I could read (I haven't found any), or maybe the driver developer can help me out? Thanks, Camilo.

2 2

[alsa-devel] [PATCH] asoc tlv320aic3x: add GPIO support
by Daniel Mack 18 Apr '08

18 Apr '08

This patch adds support for AIC3x GPIO lines. They can be configured for many possible functions as well as be driven manually. I also introduced i2c read functionality since the GPIO state register has to be read from hardware every time and can not be served from cache. Signed-off-by: Daniel Mack <daniel(a)caiaq.de>

1 0

[alsa-devel] Alsa Driver on Coldfire
by Simon Dunn 18 Apr '08

18 Apr '08

Hi I've been given the job of writing a sound card driver using the alsa architecture for a development platform that uses a coldfire chip. The first thing I came across was a chunky 'if !M68K' in sound/Kconfig, which excludes all the alsa components. I can't find any reason for this in the mailing list archives or on the web in general, so I'm wondering if anybody knows why the M68K architecture is excluded? Cheers Simon -- Simon Dunn, Software Engineer MPC Data Limited e-mail: sdunn(a)mpc-data.co.uk web: www.mpc-data.co.uk tel: +44 (0) 1225 710600 fax: +44 (0) 1225 710601 ddi: +44 (0) 1225 710631 MPC Data Limited is a company registered in England and Wales with company number 05507446 Registered Address: County Gate, County Way, Trowbridge, Wiltshire, BA14 7FJ VAT no: 850625238 The information in this email and in the attached documents is confidential and may be legally privileged. Any unauthorized review, copying, disclosure or distribution is prohibited and may be unlawful. It is intended solely for the addressee. Access to this email by anyone else is unauthorized. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. When addressed to our clients any opinions or advice contained in this email is subject to the terms and conditions expressed in the governing contract.

3 4

[alsa-devel] [PATCH 001c/001] snd-powermac: more older kernel compatibility
by Risto Suominen 18 Apr '08

18 Apr '08

2008/4/17, Takashi Iwai <tiwai(a)suse.de>: > > The hack isn't definitely for the latest upstream, so if this is > needed, rather define in each *.c in alsa-driver/ppc please. > Now it's done in ppc/*.patch. Risto

2 1

[alsa-devel] [PATCH] SOC: fix tests in cs4270_hw_params()
by Roel Kluin 17 Apr '08

17 Apr '08

cs4270_hw_params does several times: ret = snd_soc_write() if (ret < 0) ... This only works when ret is signed. Signed-off-by: Roel Kluin <12o3l(a)tiscali.nl> --- diff --git a/sound/soc/codecs/cs4270.c b/sound/soc/codecs/cs4270.c index bf2ab72..e73fcfd 100644 --- a/sound/soc/codecs/cs4270.c +++ b/sound/soc/codecs/cs4270.c @@ -372,7 +372,7 @@ static int cs4270_hw_params(struct snd_pcm_substream *substream, struct snd_soc_device *socdev = rtd->socdev; struct snd_soc_codec *codec = socdev->codec; struct cs4270_private *cs4270 = codec->private_data; - unsigned int ret = 0; + int ret; unsigned int i; unsigned int rate; unsigned int ratio;

3 2

Re: [alsa-devel] alsa 1.0.16 on kernel 2.6.23.9
by Takashi Iwai 17 Apr '08

17 Apr '08

At Thu, 17 Apr 2008 12:42:16 +0000, Vitaly V. Ch wrote: > > On Thu, Apr 17, 2008 at 12:13 PM, Takashi Iwai <tiwai(a)suse.de> wrote: > > At Thu, 17 Apr 2008 12:06:12 +0000, > > > > Vitaly V. Ch wrote: > > > > > > On Thu, Apr 17, 2008 at 11:54 AM, Takashi Iwai <tiwai(a)suse.de> wrote: > > > > At Thu, 17 Apr 2008 11:14:36 +0000, > > > > > > > > Vitaly V. Ch wrote: > > > > > > > > > > On Thu, Apr 17, 2008 at 9:55 AM, Takashi Iwai <tiwai(a)suse.de> wrote: > > > > > > At Thu, 17 Apr 2008 07:26:25 +0000, > > > > > > > > > > > > Vitaly V. Ch wrote: > > > > > > > > > > > > > > Have anyone successfully run alsa 1.0.16 on kernel 2.6.23.9? > > > > > > > > > > > > > > after success configure and make with one warning: > > > > > > > > > > > > > > WARNING: /tmp/alsa-driver-1.0.16/misc/ac97_bus: 'ac97_bus_type' > > > > > > > exported twice. Previous export was in vmlinux > > > > > > > > > > > > Do you have CONFIG_AC97_BUS=y? This should be a module, too. > > > > > Yes, I have it. I can't find in menuconfig item to switch it. Can I > > > > > switch it manually by editing .config? > > > > > > > > Yes. But usually it's selected by other items. So you likely made > > > > dependent components all built-in (=y). They should be also modules. > > > where I can see which components require to be modules also? > > > > Read Kconfig files. > I grep all Kconfig files and found out nothing depended on CONFIG_AC97_BUS Others do "select" CONFIG_AC97_BUS. > > > I don't compile OSS at all and all alsa is modules. which component > > > can be depend on it? > > > > Don't know unless you expose your config. Just try to select m and > > rebuild. > .config is attached. > I try to select m and make - make revert m to y before begin compile. > > may be I must turn off support of sound in kernel at all? No, it won't work, at least the sound core must be enabled. Takashi

2 5

[alsa-devel] alsa 1.0.16 on kernel 2.6.23.9
by Vitaly V. Ch 17 Apr '08

17 Apr '08

Have anyone successfully run alsa 1.0.16 on kernel 2.6.23.9? after success configure and make with one warning: WARNING: /tmp/alsa-driver-1.0.16/misc/ac97_bus: 'ac97_bus_type' exported twice. Previous export was in vmlinux I receive non-working installation of alsa Any ideas? \\wbr Vitaly Chernookiy

2 5