From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Vinod Koul <vinod.koul@intel.com>, Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org, Qais Yousef <qais.yousef@imgtec.com>,
Pierre-Louis Bossart <pierre-louis.bossart@linux.jf.intel.com>,
Mark Brown <broonie@kernel.org>
Subject: Re: alsa-lib support for compress offload
Date: Thu, 22 Jan 2015 16:03:16 -0600 [thread overview]
Message-ID: <54C173A4.4060706@linux.intel.com> (raw)
In-Reply-To: <20150122215645.GF28763@intel.com>
On 1/22/15 3:56 PM, Vinod Koul wrote:
> Can we actually support compress with current alsa APIs? If yes then we can
> do rework and keep current tinycompress APIs for Andporid and let core lib
> be reused, if not then we can go with these new APIs
No. We need to be able to pass decoder/encoder parameters, and we need
the ability to deal with bytes, without any fixed mapping between bytes
and time. If we want any convergence we'd need ALSA to deal with bytes
only and not frames, in addition to the extra configuration steps, which
would be a complete API change.
-Pierre
next prev parent reply other threads:[~2015-01-22 22:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-16 9:52 alsa-lib support for compress offload Qais Yousef
2015-01-16 10:34 ` Takashi Iwai
2015-01-16 11:22 ` Qais Yousef
2015-01-16 16:50 ` Pierre-Louis Bossart
2015-01-16 18:46 ` Mark Brown
2015-01-19 17:23 ` Qais Yousef
2015-01-19 22:07 ` Pierre-Louis Bossart
2015-01-20 7:21 ` Arun Raghavan
2015-01-20 9:53 ` Qais Yousef
2015-01-21 7:10 ` Vinod Koul
2015-01-21 9:22 ` Qais Yousef
2015-01-21 11:59 ` Takashi Iwai
2015-01-21 14:16 ` Qais Yousef
2015-01-22 21:56 ` Vinod Koul
2015-01-22 22:03 ` Pierre-Louis Bossart [this message]
2015-01-23 6:41 ` Takashi Iwai
2015-01-21 15:01 ` Pierre-Louis Bossart
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=54C173A4.4060706@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=pierre-louis.bossart@linux.jf.intel.com \
--cc=qais.yousef@imgtec.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 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).