From: Sascha Hauer <s.hauer@pengutronix.de>
To: Liam Girdwood <lrg@slimlogic.co.uk>
Cc: alsa-devel@alsa-project.org,
Mark Brown <broonie@opensource.wolfsonmicro.com>
Subject: Re: About the platform_name field in snd_soc_dai_link
Date: Wed, 11 Aug 2010 13:39:30 +0200 [thread overview]
Message-ID: <20100811113930.GP27749@pengutronix.de> (raw)
In-Reply-To: <1281449769.3059.62.camel@odin>
On Tue, Aug 10, 2010 at 03:16:09PM +0100, Liam Girdwood wrote:
> On Tue, 2010-08-10 at 14:47 +0100, Mark Brown wrote:
> > On Tue, Aug 10, 2010 at 03:38:18PM +0200, Sascha Hauer wrote:
> >
> > > I'm wondering what exactly a snd_soc_platform is. Apparently the
> > > snd_pcm_ops/pcm_new/pcm_free are specific to a platform. For my
> > > understanding these operations are more specific to a cpu_dai. Looking
> > > at the tree it seems that each cpu_dai has exactly one possible
> > > platform, which seems logical to me because the cpu_dai knows how to
> > > transfer the data.
> >
> > They're for the DMA bit of the CPU. While most platforms have a single
> > DMA controller (though some have more than one) it's moderately common
> > to have more than one DAI (eg, dedicated I2S and DSP mode controllers
> > rather than a programmable serial port, or an AC'97 controller) so it's
> > useful to share the DMA code.
> >
> > > My problem on i.MX is that I currently have two possible cpu dais
> > > (imx-ssi.[01]) and each can be configured to use dma or fiq depending
> > > on the dma capabilities. So the cpu_dai knows which pcm_ops we have
> > > to use, but currently it's the soc glue code which has to decide in
> > > platform_name. Am I understanding something wrong here?
> >
> > This is mostly a holdover from the existing (current mainline) ASoC
> > structuring at the minute, that also has the DMA configured per machine.
> > This may change depending on future hardware requirements, though.
> > _______________________________________________
>
> With multi-component it's possible to register both FIQ and DMA platform
> together. i.e. ssi0 could use DMA and ssi1 FIQ.
Whether we have to use FIQ depends on the codec connected (given that
DMA is available, which is not yet the case). On the phyCORE board we
have a wm9712 codec. This codec sends us data gpio status data in slot
12. The i.MX hardware is silly enough to put this data into the rx fifo,
so the fiq handler has to sort out this data.
In the longer term we want to use DMA for everything, but first we have
to extend the pcm-dma to sort aout this data aswell.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
prev parent reply other threads:[~2010-08-11 11:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-10 13:38 About the platform_name field in snd_soc_dai_link Sascha Hauer
2010-08-10 13:47 ` Mark Brown
2010-08-10 14:09 ` Sascha Hauer
2010-08-10 14:16 ` Liam Girdwood
2010-08-10 14:42 ` Mark Brown
2010-08-10 14:49 ` Liam Girdwood
2010-08-11 11:39 ` Sascha Hauer [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=20100811113930.GP27749@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=lrg@slimlogic.co.uk \
/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).