From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Peter Ujfalusi <peter.ujfalusi@nokia.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"lrg@slimlogic.co.uk" <lrg@slimlogic.co.uk>
Subject: Re: [RFC 0/2] soc-dapm or TWL4030: Runtime DAPM ordering problem
Date: Tue, 3 Aug 2010 16:02:54 +0100 [thread overview]
Message-ID: <20100803150254.GF25306@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <201008031209.25585.peter.ujfalusi@nokia.com>
On Tue, Aug 03, 2010 at 12:09:10PM +0300, Peter Ujfalusi wrote:
> On Tuesday 03 August 2010 11:39:44 ext Mark Brown wrote:
> > I think there's something useful we can do with DAPM here (independantly
> > of anything in TWL4030), probably involving splitting up the routing
> > change walk to run power down first and then power up but the current
> > patch feels like it's going to cause at least as many problems as it
> > solves.
> I tend to agree. The patch for the core is quite dramatic change, and it can
> introduce other types of problems.
> But... It would make the actual register write sequence consistent in all cases.
The power and route configuration settings aren't really part of the
same sequence, though - other widgets can also trigger power changes,
and obviously a route change need not imply a power change.
prev parent reply other threads:[~2010-08-03 15:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-02 7:08 [RFC 0/2] soc-dapm or TWL4030: Runtime DAPM ordering problem Peter Ujfalusi
2010-08-02 7:08 ` [RFC 1/2] ASoC: soc-dapm: Reorder DAPM register write sequence Peter Ujfalusi
2010-08-02 7:08 ` [RFC 2/2] ASoC: TWL4030: Capture route runtime DAPM ordering fix Peter Ujfalusi
2010-08-02 10:27 ` [RFC 0/2] soc-dapm or TWL4030: Runtime DAPM ordering problem Mark Brown
2010-08-02 10:59 ` Peter Ujfalusi
2010-08-03 2:56 ` Mark Brown
2010-08-03 6:15 ` Peter Ujfalusi
2010-08-03 8:39 ` Mark Brown
2010-08-03 9:09 ` Peter Ujfalusi
2010-08-03 15:02 ` Mark Brown [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=20100803150254.GF25306@rakim.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=lrg@slimlogic.co.uk \
--cc=peter.ujfalusi@nokia.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.