Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel <alsa-devel@alsa-project.org>,
	Paul Mackerras <paulus@samba.org>,
	Benjamin Berg <benjamin@sipsolutions.net>
Subject: Re: delayed dma trigger
Date: Tue, 24 Oct 2006 17:13:04 +0200	[thread overview]
Message-ID: <1161702784.2840.33.camel@ux156> (raw)
In-Reply-To: <s5hbqo1pxaz.wl%tiwai@suse.de>

On Tue, 2006-10-24 at 17:07 +0200, Takashi Iwai wrote:

> It won't be called unless PCM_INFO_PAUSE bit flag is set.  It means
> that the driver doesn't support the hardware pause/resume function.
> The pseudo pause/resume is just like a stop -> reset -> start
> sequence.
> 
> In other words, once when you set SNDRV_PCM_INFO_PAUSE flag, the
> driver has to stop the stream by trigger(PAUSE_PUSH) and restart the
> stream by trigger(PAUSE_RELEASE) call without prepare callback.

Ok, then we can safely set that flag once we fix it as I outlined and if
someone does pause-release very quickly we won't pause at all. should be
fine.

Who wants to do the patch? :)

Many thanks,
Johannes

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642

      reply	other threads:[~2006-10-24 15:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-23  8:49 delayed dma trigger Johannes Berg
2006-10-23 13:23 ` Takashi Iwai
2006-10-23 13:46   ` Johannes Berg
2006-10-23 14:11     ` Takashi Iwai
2006-10-23 14:31       ` Johannes Berg
2006-10-24 15:07         ` Takashi Iwai
2006-10-24 15:13           ` Johannes Berg [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=1161702784.2840.33.camel@ux156 \
    --to=johannes@sipsolutions.net \
    --cc=alsa-devel@alsa-project.org \
    --cc=benjamin@sipsolutions.net \
    --cc=paulus@samba.org \
    --cc=tiwai@suse.de \
    /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