From: Liam Girdwood <lrg@slimlogic.co.uk>
To: anish.singh@samsung.com
Cc: "liam.girdwood@wolfsonmicro.com" <liam.girdwood@wolfsonmicro.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"broonie@opensource.wolfsonmicro.com"
<broonie@opensource.wolfsonmicro.com>
Subject: Re: No shutdown code in soc-core.c
Date: Mon, 19 Apr 2010 15:10:55 +0100 [thread overview]
Message-ID: <1271686255.3208.309.camel@odin> (raw)
In-Reply-To: <11864963.186471271683156859.JavaMail.weblogic@epml11>
On Mon, 2010-04-19 at 13:19 +0000, ANISH KUMAR wrote:
> >Did you see Mark's reply on dev_pm_ops ?
>
> >i.e.
>
> >static const struct dev_pm_ops soc_pm_ops = {
> > .suspend = soc_suspend,
> > .resume = soc_resume,
> > .poweroff = soc_poweroff,
> >};
>
> I missed out Mark reply.However i checked now this structure is
> not there in my code base.As i mentioned in my previous mail
> the flow of events when restart takes place.
> Anyway i thought something is amiss in this struct platform_driver soc_driver
> that is why i am mailing to the experts here otherwise my
> problem is fixed by having the code as mentioned in my previous
> mail.
> I just wanted to know the reason?Or Am i missing something probably the concept
> of turning off the audio driver??
> Kerenl version used: 2.6.29
>
Ah, your kernel is very old. I would just do what you are currently
doing with shutdown and use the dev_pm_ops when you upgrade your kernel.
Thanks
Liam
--
Freelance Developer, SlimLogic Ltd
ASoC and Voltage Regulator Maintainer.
http://www.slimlogic.co.uk
next prev parent reply other threads:[~2010-04-19 14:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-19 13:19 No shutdown code in soc-core.c ANISH KUMAR
2010-04-19 14:10 ` Liam Girdwood [this message]
2010-04-19 16:59 ` Mark Brown
-- strict thread matches above, loose matches on Subject: below --
2010-04-22 8:10 ANISH KUMAR
2010-04-17 7:02 ANISH KUMAR
2010-04-19 12:15 ` Liam Girdwood
2010-04-16 16:44 ANISH KUMAR
2010-04-16 17:21 ` Liam Girdwood
2010-04-16 2:29 ANISH KUMAR
2010-04-16 16:03 ` Liam Girdwood
2010-04-16 18:47 ` Mark Brown
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=1271686255.3208.309.camel@odin \
--to=lrg@slimlogic.co.uk \
--cc=alsa-devel@alsa-project.org \
--cc=anish.singh@samsung.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=liam.girdwood@wolfsonmicro.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 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.