From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Vinod Koul <vinod.koul@linux.intel.com>
Cc: alsa-devel@alsa-project.org, namartax.kohli@intel.com,
lrg@ti.com, ramesh.babu@intel.com,
pierre-louis.bossart@linux.intel.com
Subject: Re: [RFC PATCH 2/2] ASoC: add compress stream support
Date: Mon, 6 Aug 2012 13:59:40 +0100 [thread overview]
Message-ID: <20120806125940.GH16861@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1344231121.1726.14448.camel@vkoul-udesk3>
On Mon, Aug 06, 2012 at 11:02:01AM +0530, Vinod Koul wrote:
> On Tue, 2012-07-31 at 12:11 +0530, Vinod Koul wrote:
> > -snd-soc-core-objs += soc-pcm.o soc-io.o
> > +snd-soc-core-objs += soc-pcm.o soc-compress.o soc-io.o
> I am planning to add a symbol, SND_SOC_COMPRESS_OFFLOAD and compile this
> file and other changes under this flag.
> This will select SND_COMPRESS_OFFLOAD and users should select this
> symbol when using compressed offload...
> Let me know if its fine and will send patch for this.
To be honest given the code for compressed stuff is so small in
comparison with the size of ASoC that I'm not sure it's worth bothering,
we should probably just enable it unconditionally with ASoC.
next prev parent reply other threads:[~2012-08-06 12:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-31 6:41 [RFC PATCH 0/2] ASoC: add compress stream support Vinod Koul
2012-07-31 6:41 ` [RFC PATCH 1/2] ASoC: add definitions for compressed operations Vinod Koul
2012-07-31 6:41 ` [RFC PATCH 2/2] ASoC: add compress stream support Vinod Koul
2012-08-02 18:09 ` Mark Brown
2012-08-02 19:31 ` Takashi Iwai
2012-08-03 10:20 ` Vinod Koul
2012-08-06 8:01 ` Takashi Iwai
2012-08-06 13:07 ` Mark Brown
2012-08-06 5:32 ` Vinod Koul
2012-08-06 12:59 ` Mark Brown [this message]
2012-08-06 16:46 ` Vinod Koul
2012-08-02 18:01 ` [RFC PATCH 0/2] " Mark Brown
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=20120806125940.GH16861@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=lrg@ti.com \
--cc=namartax.kohli@intel.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=ramesh.babu@intel.com \
--cc=vinod.koul@linux.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 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).