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: [PATCH] compress: add support for gapless playback
Date: Thu, 14 Feb 2013 15:02:45 +0530 [thread overview]
Message-ID: <20130214093244.GA27887@intel.com> (raw)
In-Reply-To: <s5hip5vtfze.wl%tiwai@suse.de>
On Thu, Feb 14, 2013 at 10:13:57AM +0100, Takashi Iwai wrote:
> At Thu, 14 Feb 2013 14:12:51 +0530,
> Vinod Koul wrote:
> >
> > this add new API for sound compress to support gapless playback.
> > As noted in Documentation change, we add API to send metadata of encoder and
> > padding delay to DSP. Also add API for indicating EOF and switching to
> > subsequent track
> >
> > Also bump the compress API version
> >
> > Signed-off-by: Jeeja KP <jeeja.kp@intel.com>
> > Signed-off-by: Vinod Koul <vinod.koul@intel.com>
> > ---
> > v5:
> > - update metadata value with 8 words
>
> What's the reason behind this change? I can think of metadata like EQ
> parameters, but the magic number 8 is in question :)
Yes the concern was that there might be an issue with parameters which are not
single dwords, so 8 dwords was what came to my mind. 8 why, i picked the number
:). Seems decent enough and not too big. For even bigger pparameters I was
thinking to split..
If you think we should have 16/32 dwrods, am okay with it.
> I'm no enthusiastic over minimalism like Apple, so I don't mind this
> change, but just out of curiosity...
>
> Also, another spot:
>
> > @@ -145,6 +160,10 @@ struct snd_compr_codec_caps {
> > struct snd_compr_codec_caps)
> > #define SNDRV_COMPRESS_SET_PARAMS _IOW('C', 0x12, struct snd_compr_params)
> > #define SNDRV_COMPRESS_GET_PARAMS _IOR('C', 0x13, struct snd_codec)
> > +#define SNDRV_COMPRESS_SET_METADATA _IOW('C', 0x14,\
> > + struct snd_compr_metadata)
> > +#define SNDRV_COMPRESS_GET_METADATA _IOW('C', 0x15,\
> > + struct snd_compr_metadata)
Yes!
>
> Isn't it _IOWR()?
If this is only thing, let me send the update or you want a beverage :)
--
~Vinod
next prev parent reply other threads:[~2013-02-14 9:33 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-14 8:42 [PATCH] compress: add support for gapless playback Vinod Koul
2013-02-14 9:13 ` Takashi Iwai
2013-02-14 9:32 ` Vinod Koul [this message]
2013-02-14 9:45 ` Takashi Iwai
2013-02-14 11:06 ` Vinod Koul
-- strict thread matches above, loose matches on Subject: below --
2013-02-14 11:22 Vinod Koul
2013-02-14 11:31 ` Takashi Iwai
2013-02-14 13:37 ` Vinod Koul
2013-02-13 16:00 Vinod Koul
2013-02-13 16:40 ` Takashi Iwai
2013-02-13 17:03 ` Vinod Koul
2013-02-13 17:15 ` Takashi Iwai
2013-02-13 17:21 ` Vinod Koul
2013-02-12 18:31 Vinod Koul
2013-02-13 6:23 ` Takashi Iwai
2013-02-13 6:35 ` Vinod Koul
2013-02-13 7:37 ` Takashi Iwai
2013-02-13 11:34 ` Mark Brown
2013-02-13 13:39 ` Vinod Koul
2013-02-11 12:22 Vinod Koul
2013-02-11 13:41 ` Takashi Iwai
2013-02-11 13:41 ` Vinod Koul
2013-02-11 14:38 ` Takashi Iwai
2013-02-11 14:55 ` Vinod Koul
2013-02-11 15:30 ` Takashi Iwai
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=20130214093244.GA27887@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 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.