From: Liam Girdwood <liam.r.girdwood@linux.intel.com>
To: Jie Yang <yang.jie@intel.com>
Cc: alsa-devel@alsa-project.org, broonie@kernel.org
Subject: Re: [PATCH] ASoC: Intel: Fix the driver data not set issue
Date: Wed, 05 Nov 2014 07:41:37 +0000 [thread overview]
Message-ID: <1415173297.2646.5.camel@loki> (raw)
In-Reply-To: <1415116100.7168.30.camel@loki>
On Tue, 2014-11-04 at 15:48 +0000, Liam Girdwood wrote:
> On Tue, 2014-11-04 at 14:45 +0800, Jie Yang wrote:
> > The priv_data is allocated again here wrongly, and it
> > is not set to the driver data after assignment. This
> > make the pdata->dev is NULL and oops occurs on the first
> > call to hsw_volume_put.
> >
> > The resource has been allocated in driver probe callback
> > hsw_pcm_dev_probe, so here just remove this sencond
> > allocation is OK.
> >
> > Signed-off-by: Jie Yang <yang.jie@intel.com>
> > ---
> > sound/soc/intel/sst-haswell-pcm.c | 1 -
> > 1 file changed, 1 deletion(-)
> >
> > diff --git a/sound/soc/intel/sst-haswell-pcm.c b/sound/soc/intel/sst-haswell-pcm.c
> > index 21f1316..bc02a6e 100644
> > --- a/sound/soc/intel/sst-haswell-pcm.c
> > +++ b/sound/soc/intel/sst-haswell-pcm.c
> > @@ -866,7 +866,6 @@ static int hsw_pcm_probe(struct snd_soc_platform *platform)
> > dev = platform->dev;
> > dma_dev = pdata->dma_dev;
> >
> > - priv_data = devm_kzalloc(platform->dev, sizeof(*priv_data), GFP_KERNEL);
> > priv_data->hsw = pdata->dsp;
> > priv_data->dev = platform->dev;
> > priv_data->pm_state = HSW_PM_STATE_D0;
>
> Keyon, I've just updated git and it looks like this patch is probably
> missing some parts :-
>
> CC [M] sound/soc/intel/haswell.o
> sound/soc/intel/sst-haswell-pcm.c: In function ‘hsw_pcm_probe’:
> sound/soc/intel/sst-haswell-pcm.c:870:17: warning: ‘priv_data’ may be used uninitialized in this function [-Wmaybe-uninitialized]
> priv_data->hsw = pdata->dsp;
> ^
>
> Can you fix this and re-test.
>
It's actually a subsequent non upstream patch on top of this one that is
causing the warning. So nothing to be done except fixing the non
upstream patch.
Liam
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
prev parent reply other threads:[~2014-11-05 7:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-04 6:45 [PATCH] ASoC: Intel: Fix the driver data not set issue Jie Yang
2014-11-04 11:44 ` Mark Brown
2014-11-04 15:48 ` Liam Girdwood
2014-11-05 7:41 ` 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=1415173297.2646.5.camel@loki \
--to=liam.r.girdwood@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=yang.jie@intel.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