From: Liam Girdwood <lrg@slimlogic.co.uk>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Sascha Hauer <s.hauer@pengutronix.de>, alsa-devel@alsa-project.org
Subject: Re: About the platform_name field in snd_soc_dai_link
Date: Tue, 10 Aug 2010 15:49:29 +0100 [thread overview]
Message-ID: <1281451769.3059.86.camel@odin> (raw)
In-Reply-To: <20100810144207.GD6416@rakim.wolfsonmicro.main>
On Tue, 2010-08-10 at 15:42 +0100, Mark Brown wrote:
> 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:
>
> > > 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.
>
> Yup, although I think for pretty much all hardware the decision about
> which DMA driver to use is going to be fixed by silicon consideratons
> (eg, in the i.MX case it'd be odd to want to use the FIQ driver when
> {S,}DMA support is available) so it probably does make sense for the
> DAIs to be able to provide at least a default DMA controller.
Yes, exactly - this was just an example showing two different DMA
controllers.
Liam
--
Freelance Developer, SlimLogic Ltd
ASoC and Voltage Regulator Maintainer.
http://www.slimlogic.co.uk
next prev parent reply other threads:[~2010-08-10 14:49 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 [this message]
2010-08-11 11:39 ` Sascha Hauer
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=1281451769.3059.86.camel@odin \
--to=lrg@slimlogic.co.uk \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=s.hauer@pengutronix.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 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).