alsa-devel.alsa-project.org archive mirror
 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 11:24:08 +0100	[thread overview]
Message-ID: <1281522248.3080.40.camel@odin> (raw)
In-Reply-To: <20100811084430.GO27749@pengutronix.de>

On Wed, 2010-08-11 at 10:44 +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 ?
> > 
> 
> Besides the patch that I just sent I get a null pointer deref without
> the following patch. I couldn't find who should set
> codec->ac97->bus->card, but it's null when I get here. Is this an i.MX
> fault or is there something else missing here?
> 

That is set in the AC97 core and did work at the time of the RFC (when I
could test on my now non working Zylonite). Although since the RFC there
had been changes to use the dev_name for component binding and a little
re-reordering on the bind (and would have affected this piece of code
too). 

> Sascha
> 
> diff --git a/sound/soc/soc-core.c b/sound/soc/soc-core.c
> index 81a77e0..eddb26e 100644
> --- a/sound/soc/soc-core.c
> +++ b/sound/soc/soc-core.c
> @@ -312,7 +312,7 @@ static int soc_ac97_dev_register(struct snd_soc_codec *codec)
>  	codec->ac97->dev.release = soc_ac97_device_release;
>  
>  	dev_set_name(&codec->ac97->dev, "%d-%d:%s",
> -		     codec->ac97->bus->card->number, 0, codec->name);
> +		     codec->snd_card->number, 0, codec->name);
>  	err = device_register(&codec->ac97->dev);
>  	if (err < 0) {
>  		snd_printk(KERN_ERR "Can't register ac97 bus\n");

This looks good to me, as card will be set after the device_register.

Thanks

Liam

-- 
Freelance Developer, SlimLogic Ltd
ASoC and Voltage Regulator Maintainer.
http://www.slimlogic.co.uk

      reply	other threads:[~2010-08-11 10:24 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
2010-08-11 13:43             ` Liam Girdwood
2010-08-11  8:44           ` Sascha Hauer
2010-08-11 10:24             ` 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=1281522248.3080.40.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).