From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: Vinod Koul <vinod.koul@intel.com>, Jeeja KP <jeeja.kp@intel.com>,
alsa-devel@alsa-project.org, liam.r.girdwood@intel.com
Subject: Re: [PATCH] compress: add support for gapless playback
Date: Wed, 13 Feb 2013 11:34:32 +0000 [thread overview]
Message-ID: <20130213113431.GA5062@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <s5hhalgvf4k.wl%tiwai@suse.de>
[-- Attachment #1.1: Type: text/plain, Size: 797 bytes --]
On Wed, Feb 13, 2013 at 08:37:15AM +0100, Takashi Iwai wrote:
> Vinod Koul wrote:
> > On Wed, Feb 13, 2013 at 07:23:32AM +0100, Takashi Iwai wrote:
> > > 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.
> But what if a driver doesn't support a particular metadata?
> Or would you mandate for every driver to support all metadata?
I tend to agree with Takashi here, it seems better if we can have
drivers able to implement only a subset of features especially if the
API does get extended.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2013-02-13 11:34 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
2013-02-13 7:37 ` Takashi Iwai
2013-02-13 11:34 ` Mark Brown [this message]
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=20130213113431.GA5062@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=jeeja.kp@intel.com \
--cc=liam.r.girdwood@intel.com \
--cc=tiwai@suse.de \
--cc=vinod.koul@intel.com \
/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.