All of lore.kernel.org
 help / color / mirror / Atom feed
From: Liam Girdwood <lrg@slimlogic.co.uk>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	Mark Brown <broonie@opensource.wolfsonmicro.com>
Subject: Re: i.MX SDMA support
Date: Wed, 11 Aug 2010 13:32:29 +0100	[thread overview]
Message-ID: <1281529949.3080.94.camel@odin> (raw)
In-Reply-To: <20100811115936.GQ27749@pengutronix.de>

On Wed, 2010-08-11 at 13:59 +0200, Sascha Hauer wrote:
> On Wed, Aug 11, 2010 at 11:09:54AM +0100, Liam Girdwood wrote:
> > On Wed, 2010-08-11 at 10:42 +0200, Sascha Hauer wrote:
> > > On Tue, Aug 10, 2010 at 03:07:43PM +0100, Liam Girdwood wrote:
> > > > On Tue, 2010-08-10 at 15:15 +0200, Sascha Hauer wrote:
> > > > 
> > > > > I just looked at the i.MX part in the multi-component update and this
> > > > > is currently far from being in a working state, so there's still some
> > > > > work to do before thinking about possible conflicts...
> > > > 
> > > > Ok, I don't think it's that far off. Everything builds for i.MX and all
> > > > components should register. The part I can't test is the component
> > > > probe() and playback/capture.
> > > > 
> > > > Have you seen an oops ?
> > > 
> > > Many of them, yes ;)
> > > 
> > > The following patch puts i.MX (nearly) back into business.
> > > 
> > 
> > Thanks for this.
> 
> There are probably some bits for the DMA part missing, I haven't tested
> it yet, but will do soon.
> 
> > 
> > >  	if (ssi->flags & IMX_SSI_USE_AC97)
> > > @@ -706,7 +731,7 @@ static struct platform_driver imx_ssi_driver = {
> > >  	.remove = __devexit_p(imx_ssi_remove),
> > >  
> > >  	.driver = {
> > > -		.name = "imx-ssi-dai",
> > > +		.name = "imx-ssi",
> > 
> > The reason that the DAI driver name was changed on all platforms to
> > include a "-dai" suffix was to distinguish the ASoC SSI driver from a
> > generic SSI serial IO driver (i.e. SSI for non audio users). This is
> > mainly due to the fact that most audio interfaces on SoC CPUs exist
> > within a generic serial interface and are also often used for non audio
> > purposes.
> > 
> > So if this suffix is ok, I guess I would need to update the the
> > following too ?
> 
> Yes, they have to be updated too. I have some more occurences in my
> tree, but a wcgrep imx-ssi should catch them all.
> 
> > 
> > arch/arm/mach-mx2/devices.c:418:		.name = "imx-ssi",		\
> > arch/arm/mach-mx2/clock_imx27.c:656:	_REGISTER_CLOCK("imx-ssi.0", NULL, ssi1_clk)
> > arch/arm/mach-mx2/clock_imx27.c:657:	_REGISTER_CLOCK("imx-ssi.1", NULL, ssi2_clk)
> > arch/arm/mach-mx3/clock-imx31.c:561:	_REGISTER_CLOCK("imx-ssi.0", NULL, ssi1_clk)
> > arch/arm/mach-mx3/clock-imx31.c:562:	_REGISTER_CLOCK("imx-ssi.1", NULL, ssi2_clk)
> > arch/arm/mach-mx3/clock-imx35.c:467:	_REGISTER_CLOCK("imx-ssi.0", NULL, ssi1_clk)
> > arch/arm/mach-mx3/clock-imx35.c:468:	_REGISTER_CLOCK("imx-ssi.1", NULL, ssi2_clk)
> > arch/arm/mach-mx3/devices.c:565:	.name = "imx-ssi",
> > arch/arm/mach-mx3/devices.c:572:	.name = "imx-ssi",
> > arch/arm/plat-mxc/audmux-v2.c:52:		return "imx-ssi.0";
> > arch/arm/plat-mxc/audmux-v2.c:54:		return "imx-ssi.1";
> > 
> > 

Ok, I'll apply and fix these up too.

Thanks

Liam

  reply	other threads:[~2010-08-11 12:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-09  9:11 i.MX SDMA support Sascha Hauer
2010-08-09 10:47 ` Liam Girdwood
2010-08-09 12:19   ` Sascha Hauer
2010-08-09 14:09     ` Mark Brown
2010-08-10 13:15       ` Sascha Hauer
2010-08-10 13:39         ` Mark Brown
2010-08-10 14:07         ` Liam Girdwood
2010-08-11  8:42           ` Sascha Hauer
2010-08-11 10:09             ` Liam Girdwood
2010-08-11 11:59               ` Sascha Hauer
2010-08-11 12:32                 ` Liam Girdwood [this message]
2010-08-11 13:43             ` Liam Girdwood
2010-08-11  8:44           ` Sascha Hauer
2010-08-11 10:24             ` Liam Girdwood

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=1281529949.3080.94.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 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.