All of lore.kernel.org
 help / color / mirror / Atom feed
From: Clemens Ladisch <clemens@ladisch.de>
To: Raymond Toy <rtoy@google.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: Alsa timing question
Date: Thu, 25 Aug 2011 09:15:46 +0200	[thread overview]
Message-ID: <4E55F6A2.3040307@ladisch.de> (raw)
In-Reply-To: <CAE3TgXE3g9n92Xru_6Znk00rfDdF5OSMXaTiquU=ne5NLrOkOg@mail.gmail.com>

Raymond Toy wrote:
> I'm working on an application where I'd like to have relatively fixed timing
> between calls to snd_pcm_writei.

Why?

> [...] I see is that most calls to snd_pcm_writei are spaced about 50 ms
> apart.  This makes some sense, but I was expecting the calls to be about
> 42.67 ms apart.  However, about every 6th call, the time is just 200 us
> or so.  Why is that?

In theory, when the device is configured for a specific period size, its
interrupts (and therefore the application wakeups) will arrive spaced at
this interval (modulo any scheduling delays).

However, if you're using the dmix plugin, the period size of your
application's device will not necessarily be identical with the period
size of the hardware device.  To see the actual period size, look into
/proc/asound/card?/pcm0p/sub0/hw_params.


Regards,
Clemens

  reply	other threads:[~2011-08-25  7:15 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-25  0:10 Alsa timing question Raymond Toy
2011-08-25  7:15 ` Clemens Ladisch [this message]
2011-08-25 15:52   ` Raymond Toy
2011-08-26  8:02     ` Clemens Ladisch
2011-08-26  8:29     ` Olivier Guillion - Myriad
2011-08-26 15:56       ` Raymond Toy
2011-08-27  8:08         ` Olivier Guillion - Myriad
2011-08-27  9:15           ` Jassi Brar
2011-08-29 18:41           ` Raymond Toy
2011-08-29 20:24   ` Raymond Toy
2011-08-30  7:49     ` Clemens Ladisch
2011-08-30 19:04       ` Raymond Toy
2011-08-31 20:07         ` Clemens Ladisch

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=4E55F6A2.3040307@ladisch.de \
    --to=clemens@ladisch.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=rtoy@google.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.