From: Vinod Koul <vinod.koul@intel.com>
To: anish singh <anish198519851985@gmail.com>
Cc: maruthi.srinivas.b@gmail.com, alsa-devel@alsa-project.org
Subject: Re: compressed audio support (maruthi srinivas)
Date: Tue, 3 Dec 2013 10:28:34 +0530 [thread overview]
Message-ID: <20131203045834.GM8834@intel.com> (raw)
In-Reply-To: <CAK7N6vrkSZALp2z5wpve1Cw6GWzWX=u060yEq8iukK1Oeqe1-g@mail.gmail.com>
On Mon, Dec 02, 2013 at 03:24:51PM -0800, anish singh wrote:
> Both are compress framework driver files.
> compress_offload.c file is the one which interacts with userspace
> by using ioctl's, registers the compressed device with alsa
> framework(/dev/compress* gets created because of that), calls
> the corresponding functions such as trigger, pointer update, copy
> and others when userspace pauses, plays and stops the playback
> or recording.
>
> soc_compress.c file is the file which interacts with compress_offload.c
> file to create a 'dev' node for compress driver.Basically when you
> register your compress driver with compress framework,alsa core
> will come to know that your dai support compress operations and
> it will create the dev node by using soc_compress.c file.The functions
> in this file gets called by compress_offload.c functions and who
> inturn gets called by the userspace.
>
> userspace->compress_offload.c->soc_compress.c->your_compress_driver.
userspace->compress_offload.c->your_compress_driver.
this will work too, as i said you are not bound to asoc but to framework
like PCM. We can have PCM alsa driver like PCI or something else or ASoC
--
~Vinod
prev parent reply other threads:[~2013-12-03 5:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-02 23:24 compressed audio support (maruthi srinivas) anish singh
2013-12-03 4:58 ` Vinod Koul [this message]
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=20131203045834.GM8834@intel.com \
--to=vinod.koul@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=anish198519851985@gmail.com \
--cc=maruthi.srinivas.b@gmail.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.