From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Barry Song <21cnbao@gmail.com>
Cc: uclinux-dist-devel@blackfin.uclinux.org, alsa-devel@alsa-project.org
Subject: Re: [PATCH] add support to reorder CPU and Codec DAI suspend/resume
Date: Wed, 11 Nov 2009 11:24:31 +0000 [thread overview]
Message-ID: <20091111112431.GA18005@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1257923457-31470-1-git-send-email-21cnbao@gmail.com>
On Wed, Nov 11, 2009 at 03:10:57PM +0800, Barry Song wrote:
> Due to some hardware dependence issues, some devices maybe require
> different suspend/resume execution order for CPU and Codec DAI to
> make sure the hardware can work normally after executing sleep and
> wakeup.
Are there any actual systems that this solves problems for - if so, what
are the problems? I don't think this solution is general enough to be
scalable, it'll work for one particular use case but if we get further
reorderings needed it'll become difficult to manage.
If we're going to be doing anything with this I think it would be much
better to use the pm_link infrastructure which will be appearing in
2.6.34. This should allow us to provide arbatrary ordering of device
level suspend and resume.
next prev parent reply other threads:[~2009-11-11 11:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-11 7:10 [PATCH] add support to reorder CPU and Codec DAI suspend/resume Barry Song
2009-11-11 11:24 ` Mark Brown [this message]
2009-11-11 12:48 ` Barry Song
2009-11-11 14:20 ` Mark Brown
2009-11-11 14:34 ` Barry Song
2009-11-11 14:42 ` Mark Brown
2009-11-12 5:47 ` Barry Song
2009-11-12 10:46 ` 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=20091111112431.GA18005@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=21cnbao@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=uclinux-dist-devel@blackfin.uclinux.org \
/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.