alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
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: Tue, 12 Feb 2013 22:35:47 -0800	[thread overview]
Message-ID: <20130213063547.GD17659@intel.com> (raw)
In-Reply-To: <s5hobfovijf.wl%tiwai@suse.de>

On Wed, Feb 13, 2013 at 07:23:32AM +0100, Takashi Iwai wrote:
> At Tue, 12 Feb 2013 10:31:55 -0800,
> Vinod Koul wrote:
> > 
> > From: Jeeja KP <jeeja.kp@intel.com>
> > 
> > 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>
> > ---
> >  v3:
> > - Change back to ioctl struct with padding
> 
> But this makes difficult to know which parameter is unavailable in
> this kernel, as already mentioned in the thread.  You need to add
> another ioctl or add a mask in the struct.  Or, take back to single
> key/value pairs, so user can see the -ENOENT or such error for
> non-existing parameters.
Right, but we have the API version. Wouldnt it be okay to use API version to
find what kernel supports, of course it doesnt scale well as many more params
are added.

--
~Vinod

  reply	other threads:[~2013-02-13  7:00 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-12 18:31 [PATCH] compress: add support for gapless playback Vinod Koul
2013-02-13  6:23 ` Takashi Iwai
2013-02-13  6:35   ` Vinod Koul [this message]
2013-02-13  7:37     ` Takashi Iwai
2013-02-13 11:34       ` Mark Brown
2013-02-13 13:39       ` 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-14  8:42 Vinod Koul
2013-02-14  9:13 ` Takashi Iwai
2013-02-14  9:32   ` Vinod Koul
2013-02-14  9:45     ` Takashi Iwai
2013-02-14 11:06       ` 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-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=20130213063547.GD17659@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).