From: Liam Girdwood <lg@opensource.wolfsonmicro.com>
To: Timur Tabi <timur@freescale.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: Question on snd_soc_dai_link
Date: Tue, 29 May 2007 15:51:48 +0100 [thread overview]
Message-ID: <1180450308.5816.155.camel@a10072.wolfsonmicro.main> (raw)
In-Reply-To: <465C3A53.10902@freescale.com>
On Tue, 2007-05-29 at 09:36 -0500, Timur Tabi wrote:
> Liam Girdwood wrote:
>
> >
> > Please let me know if I'm way off here. The device tree looks like an
> > elegant solution for machine initialisation/description.
>
> I'm going to study this and run it by others in my department (we handle all the Linux architectural issues for Freescale SOCs). I can tell you that you're very close, but it will require some tweaks. Off the top of my head, I see a few problems:
>
> 1) The I2C addresses are specified in a separate I2C node
> 2) I don't know much about the 5200, but on my part, the DMA operations are provided by the I2S device. We don't use the generic DMA engine.
Fwiw, ASoC splits out the audio DMA code from I2S, AC97 or PCM
controllers as there isn't too much difference between audio DMA code
for each interface. Any controller specific data is passed in at
hw_params time (by the I2S/AC97/PCM controller driver) to configure
addresses, width, etc
Liam
prev parent reply other threads:[~2007-05-29 14:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-25 21:55 Question on snd_soc_dai_link Timur Tabi
2007-05-28 12:19 ` Liam Girdwood
2007-05-29 1:36 ` Timur Tabi
2007-05-29 14:19 ` Liam Girdwood
2007-05-29 14:36 ` Timur Tabi
2007-05-29 14:51 ` Liam Girdwood [this message]
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=1180450308.5816.155.camel@a10072.wolfsonmicro.main \
--to=lg@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=timur@freescale.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;
as well as URLs for NNTP newsgroup(s).