From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Tim Cussins <timcussins@eml.cc>,
Raymond Yau <superquad.vortex2@gmail.com>
Cc: nstoughton@aether.com, tiwai@suse.de, alsa-devel@alsa-project.org
Subject: Re: [PATCH v2 1/1] alsa-lib: Add snd_pcm_start_at.
Date: Tue, 06 Jan 2015 08:42:33 -0600 [thread overview]
Message-ID: <54ABF459.8000504@linux.intel.com> (raw)
In-Reply-To: <5492A7F9.8090602@eml.cc>
>> Do your implementation need to set specific start threshold to prevent
>> the driver automatically start when you fill the buffer ?
>
>
>> Do the driver allow to start when there is no data ?
>>
>
> It's the responsibility of the client to set the start threshold to a
> safe and responsible value.
>
> It might suit some applications to allow both threshold start _and_
> start_at: My implementation doesn't preclude this.
Now I am confused... My understanding was that this feature is similar
to SSYNC in HDAudio, where everything is ready, buffers filled, DMAs
armed, FIFOs filled and the start condition only opens the last gate at
a specific time - possibly with multiple streams starting at the same
time. If you add a condition on the start_threshold you really don't
need any hardware-driven start, do you?
Thanks,
-Pierre
next prev parent reply other threads:[~2015-01-06 14:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-17 17:27 [PATCH v2 1/1] alsa-lib: Add snd_pcm_start_at Tim Cussins
2014-12-18 1:05 ` Raymond Yau
2014-12-18 10:10 ` Tim Cussins
2015-01-06 14:42 ` Pierre-Louis Bossart [this message]
2015-01-06 15:13 ` Tim Cussins
2015-01-09 12:03 ` Raymond Yau
2015-01-19 11:16 ` Tim Cussins
2015-01-06 13:03 ` Tim Cussins
2015-01-06 14:27 ` Tim Cussins
2015-01-06 14:46 ` Pierre-Louis Bossart
2015-01-09 10:12 ` Tim Cussins
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=54ABF459.8000504@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=nstoughton@aether.com \
--cc=superquad.vortex2@gmail.com \
--cc=timcussins@eml.cc \
--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;
as well as URLs for NNTP newsgroup(s).