alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: "Joachim Förster" <mls.JOFT@gmx.de>
To: alsa-devel@alsa-project.org
Subject: Reasonable sound hardware parameters?
Date: Sat, 26 May 2007 08:50:29 +0200	[thread overview]
Message-ID: <1180162229.5468.21.camel@localhost> (raw)

Hi ALSA devs,

as I already described in one of my last posts on the list, I'm going to
write a ALSA driver for a sound controller which will also be "written"
at the same time (VHDL for FPGA) - on top of an embedded system (Xilinx
ML403 EvalBoard, PowerPC 405). We will do playback feature only.

The point is, that we will have _no_ real DMA and we don't want to use
the copy/silence or ack/workqueue (with intermediate buffer). So we
decided to move the ring buffer, which usually exists in RAM into the
sound controller and handle it as some kind of device IO memory, which
should be mmap'able (kernel function io_remap_pfn_range()). So, the
important goal is, to have mmap feature in the ALSA driver.

First question: To implement mmap on such kind of device IO memory, I
have to use snd_pcm_lib_mmap_iomem() as mmap() callback - like it is
used in the rme32 driver, right?

Second question: Do the following parameters make sense regarding the
size of the HW ring buffer and period sizes:

.buffer_bytes_max=16*1024;
.period_bytes_max=8*1024;
.period_bytes_min=?? resonable value ??
.periods_min=2;
.periods_max=?? resonable value ??

Furthermore, the sound controller will fire an interrupt after one
period is played.
Are there any arguments against these values? Any comments?

Thanks,
 Joachim

             reply	other threads:[~2007-05-26  6:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-26  6:50 Joachim Förster [this message]
2007-05-28  8:52 ` Reasonable sound hardware parameters? Jaroslav Kysela
  -- strict thread matches above, loose matches on Subject: below --
2007-05-28  9:56 Lorenz Kolb
2007-05-28 12:30 ` Jaroslav Kysela
2007-05-29  9:54   ` Lorenz Kolb
2007-05-29 18:17     ` Jaroslav Kysela
2007-05-29 19:15       ` Lorenz Kolb

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=1180162229.5468.21.camel@localhost \
    --to=mls.joft@gmx.de \
    --cc=alsa-devel@alsa-project.org \
    /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;
as well as URLs for NNTP newsgroup(s).