From: Carlos Munoz <carlos@kenati.com>
To: boku <boku0712@gmail.com>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Fwd: memory allocate for substream->runtime->dma_area
Date: Thu, 16 Mar 2006 16:45:24 -0800 [thread overview]
Message-ID: <441A06A4.7030100@kenati.com> (raw)
In-Reply-To: <715d90900603152121t40c2c5ddg4e6bce9df9f6e5a9@mail.gmail.com>
boku wrote:
>
> Dear all,
> Could you please tell me what the "frame" and "period" mean in alsa?
> I saw snd_pcm_hardware_t struct has period_min,max,
> period_bytes_min,max etc but quite confused of their meaning. So is
> the fifo size.
> And btw, which data struct has the info of how many bits per
> channel for the wav bitstream from alsa application aplay etc? Such as
> 16-bits, 24 or 32-bits.
> Thanks for your great help~
>
>
> On 3/16/06, *Lee Revell* <rlrevell@joe-job.com
> <mailto:rlrevell@joe-job.com> > wrote:
>
> On Wed, 2006-03-15 at 12:03 +0800, boku wrote:
>> Hi, Lee,
>> Thanks for quick response. Currently I'm designing the sound
>> driver for an ARM integrator/ap-like platform. But in the platform,
>> the audio controller is designated to move data only from a specific
>> address space. Therefore, doesn't it mean that i need to
> constrain the
>> runtime->dma_area to the specified address so that the AIC can start
>> to do DMA access?
>> Sorry about the code still not done and thanks in advance.
>
> Sorry I'm not really an ARM expert, but this has come up in the list
> archive before. You should look at some of the other ARM drivers
> in the
> tree...
>
> Lee
>
>
>
Hi Boku,
I'm not an expert but I recently looked into this.
Frame: From the macro bytes_to_frames() I gather that a frame is a
sample. For example, if the sample size is 16 bits, the frame is also 16
bits. That means that for every 2 bytes sent, one frame is sent.
Period: It is driver dependent. It's the dma interrupt interval. It is
used to calculate latencies. For example, if a driver can only dma 1024
bytes at a time, the period will be 1024. That means during capture at
least 1024 bytes will be received before the first byte is passed to the
alsa middle layer.
I hope this helps,
Carlos
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
next prev parent reply other threads:[~2006-03-17 0:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-15 3:42 memory allocate for substream->runtime->dma_area boku
2006-03-15 3:43 ` boku
2006-03-15 3:54 ` Lee Revell
[not found] ` <715d90900603142003jd1b1d00he8daf7331cc72237@mail.gmail.com>
[not found] ` <1142454177.1671.38.camel@mindpipe>
[not found] ` <715d90900603151909o6bb834efv401392e5239a0435@mail.gmail.com>
[not found] ` <715d90900603152107q30b76a85l4b428167d515ee8c@mail.gmail.com>
2006-03-16 5:21 ` Fwd: " boku
2006-03-17 0:45 ` Carlos Munoz [this message]
2006-03-17 1:17 ` Lee Revell
2006-03-17 3:26 ` boku
2006-03-20 14:54 ` Takashi Iwai
2006-03-15 10:09 ` Takashi Iwai
2006-03-16 12:51 ` boku
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=441A06A4.7030100@kenati.com \
--to=carlos@kenati.com \
--cc=alsa-devel@lists.sourceforge.net \
--cc=boku0712@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