From: Vinod Koul <vinod.koul@linux.intel.com>
To: alsa-devel@alsa-project.org
Cc: Vinod Koul <vinod.koul@linux.intel.com>,
broonie@opensource.wolfsonmicro.com,
pierre-louis.bossart@linux.intel.com, ramesh.babu@intel.com,
namartax.kohli@intel.com, lrg@ti.com
Subject: [RFC PATCH 0/2] ASoC: add compress stream support
Date: Tue, 31 Jul 2012 12:11:38 +0530 [thread overview]
Message-ID: <1343716900-23491-1-git-send-email-vinod.koul@linux.intel.com> (raw)
Here is the much delayed support for compress audio streams in ASoC.
This patch series is in RFC form, once we have agreed on this I will send
the patches supporting Intel driver as well.
Mainly we indicate if the dai is of compressed nature and based on that
register a new compressed device. Also the platform driver adds the compress
stream operations.
Since the codecs handles PCM only, the assumption is that they will not have
anything to do here and machine needs to set codec appropriately for compressed
streams. In future if codec with such support are available then we can simply
add compressed operations into codec as well
Comments, criticism welcome...
--
Namarta Kohli (1):
ASoC: add compress stream support
Vinod Koul (1):
ASoC: add definations for compressed operations
include/sound/compress_driver.h | 1 +
include/sound/soc-dai.h | 2 +
include/sound/soc.h | 17 ++-
sound/soc/Makefile | 2 +-
sound/soc/soc-compress.c | 297 +++++++++++++++++++++++++++++++++++++++
sound/soc/soc-core.c | 10 ++-
6 files changed, 326 insertions(+), 3 deletions(-)
create mode 100644 sound/soc/soc-compress.c
next reply other threads:[~2012-07-31 6:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-31 6:41 Vinod Koul [this message]
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
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=1343716900-23491-1-git-send-email-vinod.koul@linux.intel.com \
--to=vinod.koul@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=lrg@ti.com \
--cc=namartax.kohli@intel.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=ramesh.babu@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).