Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: James Courtier-Dutton <James@superbug.co.uk>
To: Assaf Hoffman <hoffman@marvell.com>
Cc: Rita Shtern <rita@marvell.com>, alsa-devel@lists.sourceforge.net
Subject: Re: ALSA snd_xferi_t buffer arrangment
Date: Wed, 11 Oct 2006 16:00:54 +0100	[thread overview]
Message-ID: <452D0726.9090604@superbug.co.uk> (raw)
In-Reply-To: <B9FFC3F97441D04093A504CEA31B7C41E4E041@msilexch01.marvell.com>

Assaf Hoffman wrote:
> Hi,
> Thanks again for clear answers.
> In case the HW strip the IEC958 frames, where the ALSA stack expect to
> find the various frame data fields such as perr, valid bit, audio
> sample, user data and channel status? Is there a data structure the HW
> should follow when DMAing the striped data to the DRAM buffer?
> What do you think of such acceleration? Does this saves a significant
> CPU time processing the ICE958 frames?
> Many thanks.
> P.S.
> I was looking into the ASLA stack and I could find
> SNDRV_PCM_FMTBIT_IEC958_SUBFRAME_XX only in snd_pcm_hardware structure
> initialization. I could not see where it is used to tell the ALSA to
> process the data as IEC958 frames.
> 

A majority of sound cards strip the frame, and only put the audio
samples in the DMA buffer. The sound card then stores the valid bits,
non-audio bit, user data etc. in a separate register on the sound card.

The processing of the IEC958 frames is done in alsa-lib.
ALSA has two parts, and kernel part, and a user space lib.
The kernel part does as little as possible, with the user space part
doing all the format conversion etc.

I have not looked closely, but I don't know if the alsa-lib decodes the
IEC958 frames or not yet.

James




-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642

  reply	other threads:[~2006-10-11 15:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-11 14:52 ALSA snd_xferi_t buffer arrangment Assaf Hoffman
2006-10-11 15:00 ` James Courtier-Dutton [this message]
2006-10-11 15:17   ` Takashi Iwai
2006-10-11 15:19     ` James Courtier-Dutton
2006-10-11 15:22       ` Takashi Iwai
  -- strict thread matches above, loose matches on Subject: below --
2006-10-18  6:31 Assaf Hoffman
2006-10-11 15:40 Assaf Hoffman
2006-10-11 14:08 Assaf Hoffman
2006-10-11 14:22 ` James Courtier-Dutton
2006-10-11 13:07 Assaf Hoffman
2006-10-11 13:53 ` James Courtier-Dutton

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=452D0726.9090604@superbug.co.uk \
    --to=james@superbug.co.uk \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=hoffman@marvell.com \
    --cc=rita@marvell.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