Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Lee Revell" <rlrevell@joe-job.com>
To: Harsha priya gupta <harshapriya@gmail.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: basic questions
Date: Fri, 14 Mar 2008 18:35:20 -0400	[thread overview]
Message-ID: <75b66ecd0803141535g66aae270v5c53fb67e973566f@mail.gmail.com> (raw)
In-Reply-To: <827ad74d0803132135i6c7c8ad8sa7ad5469cc677920@mail.gmail.com>

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.

>  2. What are the hwdep files in ALSA used for? Where do the concerned IOCTLS
>  land to?

Anything you want to do that doesn't fit into the ALSA framework.
Typically they're used for things like programming the card's DSP
engine.  I've also used them for testing/QA in embedded development,
using hwdep ioctls to provide an alternate playback path, so that any
issues can quickly be determined to be an ALSA issue, or a problem
with the way we were programming the HW.

See the emu10k1 driver for a good example of hwdep ioctl usage.  It's
used for things like loading DSP patches.

Lee

  reply	other threads:[~2008-03-14 22:35 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 [this message]
2008-03-14 22:57   ` Eliot Blennerhassett
2008-03-18  2:01     ` Lee Revell
2008-03-18 12:50       ` Harsha priya gupta
  -- 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=75b66ecd0803141535g66aae270v5c53fb67e973566f@mail.gmail.com \
    --to=rlrevell@joe-job.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=harshapriya@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox