alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Qais Yousef <qais.yousef@imgtec.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: Vinod Koul <vinod.koul@intel.com>,
	alsa-devel@alsa-project.org, Mark Brown <broonie@kernel.org>
Subject: Re: alsa-lib support for compress offload
Date: Fri, 16 Jan 2015 11:22:45 +0000	[thread overview]
Message-ID: <54B8F485.7090603@imgtec.com> (raw)
In-Reply-To: <s5hbnlzt3o2.wl-tiwai@suse.de>

On 01/16/2015 10:34 AM, Takashi Iwai wrote:
> At Fri, 16 Jan 2015 09:52:58 +0000,
> Qais Yousef wrote:
>> Hi,
>>
>> As far as I understand I need to use something similar to tinycompress
>> to use alsa devices that supports compress offload. When I asked on
>> gstreamer list [1] about alsasink support for compress offload they said
>> yes. But I can see that gstalsasink.c [2] only uses the standard
>> alsa-lib api which AFAICT doesn't support compress offload.
>>
>> Did I misread the code and alsa-lib actually works with compress
>> offload? Gstreamer refers to the feature "passthrough" and associate it
>> with SPDIF[3], are they taking advantage of some other alsa feature that
>> looks like compress offload?
> It's a normal IEC958 passthrough, nothing to do with the compress
> offload.  And, no, we have no support for compress API in alsa-lib
> yet.  Just because no one submitted the patches.
>
>
> Takashi

Thanks. I haven't used alsa-lib before but I might be able to send the 
patches if I get guidance of what needs doing. Is the expected API 
similar/same to what provided by tinycompress[1]?

[1] 
http://git.alsa-project.org/?p=tinycompress.git;a=blob;f=include/tinycompress/tinycompress.h;h=03c396fccea5f2a176d24fd580ee6a447da657ec;hb=HEAD

  reply	other threads:[~2015-01-16 11:22 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 [this message]
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
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=54B8F485.7090603@imgtec.com \
    --to=qais.yousef@imgtec.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --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).