From: "Harsha priya gupta" <harshapriya@gmail.com>
To: Lee Revell <rlrevell@joe-job.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: basic questions
Date: Tue, 18 Mar 2008 18:20:46 +0530 [thread overview]
Message-ID: <827ad74d0803180550g5cf74fc2qf02f8ce81bd48193@mail.gmail.com> (raw)
In-Reply-To: <75b66ecd0803171901k17ed767dj30f6e4f79e25857e@mail.gmail.com>
Thanks a lot for the responses.
I see that there can be a way to implement a path for sending encoded
streams to sound card driver through ALSA for hardware decoding but it does
not explicitly exist today.
There are currently a lot of hardware that support decoding. If there is no
existing path in ALSA, what is the recommended way to do so? [ provide
different driver for encoded streams?]
As I am new to ALSA, it would be great if anyone could help me quantify the
effort and difficulty level involved and provide a direction for the same.
Would I be on the right path if;
1. Like PCM object, register a encoded stream object in ALSA framework
2. Provide IOCTLs from sound card driver for MMF to send encoded buffer
3. (is required??) implement API in ALSA driver and Libasound to route the
calls from MMF to sound card IOCTLs
Thanks a lot in advance,
-Harsha
On Tue, Mar 18, 2008 at 7:31 AM, Lee Revell <rlrevell@joe-job.com> wrote:
> On Fri, Mar 14, 2008 at 6:57 PM, Eliot Blennerhassett
> <linux@audioscience.com> wrote:
> > On Saturday 15 March 2008 11:35:20 Lee Revell wrote:
> > > On Fri, Mar 14, 2008 at 12:35 AM, Harsha priya gupta
> > >
> > > <harshapriya@gmail.com> wrote:
> > > > Hi,
> > > >
> > > > I am ramping up on ALSA architecture and framework. I have a
> couple of
> > > > basic questions. I apologize if these questions are very basic to
> be
> > > > raised in this mailing list. If anyone can help me find answers, it
> would
> > > > be great. Thanks in advance.
> > > >
> > > > 1. My assumption is that ALSA handles only PCM streams today. Does
> it
> > > > handle encoded streams from application to sound card (Which can do
> > > > hardware decoding)?
> > >
> > > Someone else could probably give a better answer, but I believe that
> > > currently ALSA has no API for cards that do HW decoding.
> >
> > Not AFAIK, and certainly the architecture assumes a constant data rate.
> I.e X
> > bytes consumed implies elapsed time of (X * constant) = the _period_
> >
> > Alsa headers do define some format constants for compressed audio.
> >
> > We would like to support compressed audio for our cards, which can do
> hardware
> > decoding. I did try to implement it early on, but got lost in the
> quagmire of
> > driver midlevel code and alsa-lib.
> >
> > A first step would be to allow CBR compressed formats to pass through
> to the
> > driver unaltered. For these there is a defined bits per sample, though
> it can
> > be non-integer which might be a problem.
>
> I would look at how ALSA implements AC3 passthrough.
>
> Lee
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
>
--
-Harsha
next prev parent reply other threads:[~2008-03-18 12:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-14 4:35 basic questions Harsha priya gupta
2008-03-14 22:35 ` Lee Revell
2008-03-14 22:57 ` Eliot Blennerhassett
2008-03-18 2:01 ` Lee Revell
2008-03-18 12:50 ` Harsha priya gupta [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-07-30 10:00 Basic questions tsepp2001
2017-07-30 14:24 ` Clemens Ladisch
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=827ad74d0803180550g5cf74fc2qf02f8ce81bd48193@mail.gmail.com \
--to=harshapriya@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=rlrevell@joe-job.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