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 13:15:14 +0100 [thread overview]
Message-ID: <1271679314.3208.100.camel@odin> (raw)
In-Reply-To: <21125077.117201271487763642.JavaMail.weblogic@epml11>
On Sat, 2010-04-17 at 07:02 +0000, ANISH KUMAR wrote:
> Why this shutdown filed is not there in the struct shown below:
> static struct platform_driver soc_driver
> {
> .shutdown = soc_shutdown, //soc-core.c
> }
> This shutdown call this codec_dev->shutdown function
> In my case i am turning off the amplifier using this call.Which
> solved my problem of "TAK" sound during reset.
>
> I agree that soc_codec_close() is calling the shutdown function
> but in my case there is a call to set the path after this which is
> turning on the amplifier and suddenly if we reset the phone it is
> causing "TAK" sound.Probably because AMPLIFIER was on.
>
> Anyway why this function call soc_shutdown() is there in
> soc-core.c if no one is calling it???
> I know there will be a redundancy if we have shutdown field
> in the struct shown above as soc_codec_close call also calls
> codec shutdown code.
> But in my case it is solving my problem.
>
>
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,
};
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 12:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-17 7:02 No shutdown code in soc-core.c ANISH KUMAR
2010-04-19 12:15 ` Liam Girdwood [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-04-22 8:10 ANISH KUMAR
2010-04-19 13:19 ANISH KUMAR
2010-04-19 14:10 ` Liam Girdwood
2010-04-19 16:59 ` Mark Brown
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=1271679314.3208.100.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox