From: Vinod Koul <vinod.koul@intel.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: Jeeja KP <jeeja.kp@intel.com>,
alsa-devel@alsa-project.org, broonie@opensource.wolfsonmicro.com,
liam.r.girdwood@intel.com
Subject: Re: [RFC] compress: add support for gapless playback
Date: Wed, 6 Feb 2013 06:31:18 -0800 [thread overview]
Message-ID: <20130206143118.GL3143@intel.com> (raw)
In-Reply-To: <s5ha9rh8pmt.wl%tiwai@suse.de>
On Wed, Feb 06, 2013 at 03:48:26PM +0100, Takashi Iwai wrote:
> > > How is the operation flow? Does it drain until which point?
> > Right, we want to move from one track to another. And while at this DSP needs to
> > exhaust the buffers from first track and then we should start writing second
> > track. When userspace has finsihed wirting first track it sends partial_drain
> > and DSP decods finsihed off and returns when it is ready to accept second track
> > data. The userland sends the metadata for this followed by data write.
>
> Hm, could you depict the flow? Will be like below?
>
> - Open
> - Get caps / codec caps
> - Set params
> - Set metadata of the first track
> - Fill data of the first track
> - Trigger START
> - User-space finished sending all, then trigger PARTIAL_DRAIN
PARTAIL_DRAIN is returned when DSP has finished most of data from first track
and is ready to accept second track data
> - Set metadata of the next track
> - Fill data of the next track
DSP switches to second track
Keep writing till we finish track, then trigger PARTIAL_DRAIN
Continue till you reach end of album
Then trigger DRAIN
Close
I will add this to documentation patch as well...
> OK, then PARTIAL_DRAIN doesn't sound intuitive.
> Something like CONTINUE_TO_NEXT?
Sure, anyone else with a better name :-)
>
> (I'm not particularly good at naming, so someone must have a better
> idea...)
Welcome to club, I wont mind naming after you :D
--
~Vinod
next prev parent reply other threads:[~2013-02-06 14:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-05 14:21 [RFC] compress: add support for gapless playback Vinod Koul
2013-02-06 2:44 ` Pierre-Louis Bossart
2013-02-06 7:54 ` Vinod Koul
2013-02-06 13:32 ` Mark Brown
2013-02-06 13:56 ` Vinod Koul
2013-02-06 13:59 ` Pierre-Louis Bossart
2013-02-06 14:00 ` Vinod Koul
2013-02-06 14:14 ` Takashi Iwai
2013-02-06 14:02 ` Vinod Koul
2013-02-06 14:33 ` Takashi Iwai
2013-02-06 14:11 ` Takashi Iwai
2013-02-06 14:09 ` Vinod Koul
2013-02-06 14:48 ` Takashi Iwai
2013-02-06 14:31 ` Vinod Koul [this message]
[not found] ` <37A133201056E44A80888420ECA881BF1093DC5F68@EXCMB2.wolfsonmicro.main>
[not found] ` <20130207011518.GA30348@opensource.wolfsonmicro.com>
2013-02-07 2:18 ` Vinod Koul
2013-02-07 8:49 ` Takashi Iwai
2013-02-07 16:34 ` Vinod Koul
[not found] ` <20130207113738.GA15824@opensource.wolfsonmicro.com>
2013-02-07 11:49 ` Takashi Iwai
2013-02-07 16:51 ` Vinod Koul
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=20130206143118.GL3143@intel.com \
--to=vinod.koul@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=jeeja.kp@intel.com \
--cc=liam.r.girdwood@intel.com \
--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).