From: ANISH KUMAR <anish.singh@samsung.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>,
Liam Girdwood <lrg@slimlogic.co.uk>
Cc: "liam.girdwood@wolfsonmicro.com" <liam.girdwood@wolfsonmicro.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: No shutdown code in soc-core.c
Date: Thu, 22 Apr 2010 08:10:31 +0000 (GMT) [thread overview]
Message-ID: <27549835.342171271923831455.JavaMail.weblogic@epml11> (raw)
Thanks everyone for the replies but i think for this trivial problem
i don't need to backport the kernel.Anyway now i know the answer
for my posted question.I have kept backporting as an excersie
as my assignment which i will do in due period of time.
------- Original Message-------
Sender: Mark Brown<broonie@opensource.wolfsonmicro.com>
Date: Apr 20, 2010 01:59 (GMT+09:00)
Title: Re: [alsa-devel] No shutdown code in soc-core.c
On Mon, Apr 19, 2010 at 03:10:55PM +0100, Liam Girdwood wrote:
> 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.
Actually, IME it's probably as easy to just backport current ASoC to
2.6.29 if you're doing anything non-trivial - the backport is very
straightforward for most platforms and the benefits of the enhancements
in ASoC are well worth the effort.
next reply other threads:[~2010-04-22 8:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-22 8:10 ANISH KUMAR [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-04-19 13:19 No shutdown code in soc-core.c ANISH KUMAR
2010-04-19 14:10 ` Liam Girdwood
2010-04-19 16:59 ` Mark Brown
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=27549835.342171271923831455.JavaMail.weblogic@epml11 \
--to=anish.singh@samsung.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=liam.girdwood@wolfsonmicro.com \
--cc=lrg@slimlogic.co.uk \
/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