Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Lars Heineken <Lars.Heineken@gmx.de>
To: alsa-devel@lists.sourceforge.net
Subject: Re: Opening dev/dsp takes very long
Date: Sat, 20 Mar 2004 17:59:56 +0100	[thread overview]
Message-ID: <405C788C.7000000@gmx.de> (raw)
In-Reply-To: <Pine.LNX.4.58.0403201708340.1816@pnote.perex-int.cz>

> It affects both, but ALSA API does the setup of stream parameters once, 
> but OSS API does this multiple times because there is no way to distict 
> the configuration phase and the working phase, thus we must reconfigure
> after settings of all parameters.
> 
> If you strace aplay then you'll see that one ALSA ioctl has exactly same 
> 0.5 sec peek.

Thanks a lot for your help, I would have never found that by myself.

To test it, i modified these lines (an ugly hack, for sure)

snd_cs8427_reg_write(cs8427, CS8427_REG_CLOCKSOURCE, 
chip->regmap[CS8427_REG_CLOCKSOURCE]);
         //udelay(200);
         chip->regmap[CS8427_REG_CLOCKSOURCE] |= CS8427_RUN | 
CS8427_RXDILRCK;
         snd_cs8427_reg_write(cs8427, CS8427_REG_CLOCKSOURCE, 
chip->regmap[CS8427_REG_CLOCKSOURCE]);
         //udelay(200);
         snd_i2c_unlock(cs8427->bus);
         end_time = 0; //jiffies + HZ / 2;

..and it works like a charm on my Terratec EWX24/96. After the next 
release I'll test the module option.

Thanks again,

Lars.




-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click

  reply	other threads:[~2004-03-20 16:59 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-13 20:01 Opening dev/dsp takes very long Lars Heineken
2004-03-13 20:24 ` Additional info: " Lars Heineken
2004-03-15 10:35 ` Takashi Iwai
2004-03-15 20:22   ` Lars Heineken
2004-03-16  8:19     ` Clemens Ladisch
2004-03-16  8:49       ` Lars Heineken
2004-03-16 19:04         ` Lars Heineken
2004-03-19 12:29         ` Lars Heineken
2004-03-19 21:58           ` Lars Heineken
2004-03-19 23:56             ` James Courtier-Dutton
2004-03-20  8:20               ` Lars Heineken
2004-03-20 13:24                 ` Jaroslav Kysela
2004-03-20 16:09                   ` Lars Heineken
2004-03-20 16:11                     ` Jaroslav Kysela
2004-03-20 16:59                       ` Lars Heineken [this message]
2004-03-20 17:13                   ` Tommi Sakari Uimonen
2004-03-20 17:12                     ` Jaroslav Kysela

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=405C788C.7000000@gmx.de \
    --to=lars.heineken@gmx.de \
    --cc=alsa-devel@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox