All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sylvain Munaut <tnt@246tNt.com>
To: Lorenz Kolb <linuxppcemb@lkmail.de>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: [Fwd: [alsa-devel] embedded sound architecture question]
Date: Tue, 15 May 2007 09:09:40 +0200	[thread overview]
Message-ID: <46495CB4.8050809@246tNt.com> (raw)
In-Reply-To: <000101c795e5$0af92ce0$9602a8c0@lorenzulm>

Hi,

>> If I were you, I would chose one of sound cards which have ALSA
>> drivers implemented (the list can be found on ALSA site) and
>> mimicked their behavior in your VHDL.
>>     
>
> Actually a bunch of theses drivers rely on PCI or ISA.
> The few left do all require DMA, what is only an option, if it is some sort
> of faked DMA, so the CPU writes directly into the controller's memory as we
> intend to stay as independent as possible from Xilinx' IP Cores.
> The question was: is that a good (and practicable) idea?
>   

If you can spare the BRAM, that sounds good to me.

I'm not an alsa expert but I'm working on a driver right now. And alsa
provide you a hook so you can allocate your memory buffer your self.
So as long as your control maps it's memory somewhere in the
cpu address space you should be fine.

What you need is :
 - Be able to ask the hardware where is is "read pointer".
 - Be able to ask the hardware to generate an interrupt every 'n' samples.

And that should do it.

You also need to make the controller build the AC97 frames itself
(e.g. for the control slots, a separate set of registers), and also
preferrably
supporting multiple sample format so the CPU needs to do a minimum of
conversion.


        Sylvain

  reply	other threads:[~2007-05-15  7:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-14  5:02 [Fwd: [alsa-devel] embedded sound architecture question] Lorenz Kolb
2007-05-15  7:09 ` Sylvain Munaut [this message]
2007-05-15 16:28   ` Joachim Förster
2007-05-16  7:11     ` Sylvain Munaut
  -- strict thread matches above, loose matches on Subject: below --
2007-05-13 15:15 Joachim Förster
2007-05-14  0:50 ` Leonid

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=46495CB4.8050809@246tNt.com \
    --to=tnt@246tnt.com \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=linuxppcemb@lkmail.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.