From: Vinod Koul <vinod.koul@intel.com>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.jf.intel.com>
Cc: tiwai@suse.de, 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: Tue, 5 Feb 2013 23:54:19 -0800 [thread overview]
Message-ID: <20130206075419.GF3143@intel.com> (raw)
In-Reply-To: <5111C39A.6020805@linux.intel.com>
On Tue, Feb 05, 2013 at 08:44:42PM -0600, Pierre-Louis Bossart wrote:
> > /**
> >+ * struct snd_compr_metadata: compressed stream metadata
> >+ * @encoder_delay: no of samples inserted by the encoder at the beginning
> >+ * of the track
> >+ * @encoder_padding: no of samples appended by the encoder at the end
> >+ * of the track
> >+ */
> >+struct snd_compr_metadata {
> >+ __u32 encoder_delay;
> >+ __u32 encoder_padding;
> >+};
>
> You need to pad this structure with reserved bytes for future
> evolutions. Things like ReplayGain, etc, might be of interest for
> some implementations. Let's not be cheap here
Ok, makes sense, will update this and documentation.
> >+static int
> >+snd_compr_set_metadata(struct snd_compr_stream *stream, unsigned long arg)
> >+{
> >+ struct snd_compr_metadata *metadata;
> >+ int retval;
> >+
> >+ if (!stream->ops->set_metadata)
> >+ return -ENXIO;
>
> Is this really a fatal error? Or do we want to mandate that gapless
> be supported by all implementations?
Fatal err? if DSP doesnt support metadata callback then we are reporting error
ENXIO to userpsace. No we shouldnt mandate, its upto DSP folks to see what they
should and can support.
--
~Vinod
next prev parent reply other threads:[~2013-02-06 8:19 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 [this message]
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
[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=20130206075419.GF3143@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=pierre-louis.bossart@linux.jf.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).