All of lore.kernel.org
 help / color / mirror / Atom feed
From: Clemens Ladisch <clemens@ladisch.de>
To: Jon Smirl <jonsmirl@gmail.com>
Cc: alsa-devel mailing list <alsa-devel@alsa-project.org>,
	Mark Brown <broonie@opensource.wolfsonmicro.com>
Subject: Re: Implementing sync start
Date: Mon, 10 Aug 2009 15:30:35 +0200	[thread overview]
Message-ID: <4A8020FB.7080302@ladisch.de> (raw)
In-Reply-To: <9e4733910908100546r5fa2e189s12ff72c3217c271a@mail.gmail.com>

Jon Smirl wrote:
> Does this link them?
> snd_pcm_set_sync(substream); in open()

No; this sets the substream's sync ID which tells userspace applications
that the driver actually supports sync start together with other
substreams with the same ID.

Linking is done by an application with snd_pcm_link().  The driver does
not get a notification of this; it notices this only in the trigger
callback, where the loop goes over more than one substream.

> and then remove this loop in trigger?
> snd_pcm_group_for_each_entry(substream, sub) {
> 			snd_pcm_trigger_done(substream, sub);

Why would you want to remove this loop?

The snd_pcm_group_for_each_entry() iterates over all substreams that are
linked.  The ALSA code that calls the trigger callback has a similar
loop and calls .trigger for any streams for which snd_pcm_trigger_done()
has not yet been called.


HTH
Clemens

      reply	other threads:[~2009-08-10 13:30 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-08 18:16 Implementing sync start Jon Smirl
2009-08-09  3:07 ` Jon Smirl
2009-08-10  2:13   ` Jon Smirl
2009-08-10  2:19     ` Jon Smirl
2009-08-10  7:40       ` Clemens Ladisch
2009-08-10 11:45         ` Jon Smirl
2009-08-10 11:57           ` Clemens Ladisch
2009-08-10 12:24             ` Jon Smirl
2009-08-10 12:29               ` Clemens Ladisch
2009-08-10 12:41                 ` Jon Smirl
2009-08-10 12:43                   ` Mark Brown
2009-08-10 12:46                     ` Jon Smirl
2009-08-10 13:30                       ` Clemens Ladisch [this message]

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=4A8020FB.7080302@ladisch.de \
    --to=clemens@ladisch.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=jonsmirl@gmail.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.