From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Peter Ujfalusi <peter.ujfalusi@nokia.com>
Cc: alsa-devel@alsa-project.org, Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: [RFC v2 0/3] ASoC: Option to reorder widget power sequence
Date: Mon, 6 Dec 2010 22:40:08 +0000 [thread overview]
Message-ID: <20101206224008.GA2862@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1291383073-16048-1-git-send-email-peter.ujfalusi@nokia.com>
On Fri, Dec 03, 2010 at 03:31:10PM +0200, Peter Ujfalusi wrote:
> Quite some time ago I have faced similar issue with the sequence of the
> DAPM register writes [1]
> For that issue, I used a workaround within the twl4030 codec driver.
> Now I have again issue with the register write sequence.
Sorry I've not got back to you yet - I want to implement the thing I was
talking about with inserting the register update into the DAPM sequence.
I think that is going to be easier and more generally useful, and it
doesn't rely on drivers knowing what's going on with the DAPM sequncing
code which is much cleaner from an abstraction point of view.
next prev parent reply other threads:[~2010-12-06 22:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-03 13:31 [RFC v2 0/3] ASoC: Option to reorder widget power sequence Peter Ujfalusi
2010-12-03 13:31 ` [RFC v2 1/3] ASoC: core: DAPM widget flag for reversed power up sequence Peter Ujfalusi
2010-12-03 13:31 ` [RFC v2 2/3] ASoC: core: Helper function to request reversed widget power up Peter Ujfalusi
2010-12-03 13:31 ` [RFC v2 3/3] ASoC: tlv320dac33: Reverse the power up sequence for bypass switches Peter Ujfalusi
2010-12-06 22:40 ` Mark Brown [this message]
2010-12-07 9:29 ` [RFC v2 0/3] ASoC: Option to reorder widget power sequence Peter Ujfalusi
2010-12-07 10:51 ` 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=20101206224008.GA2862@opensource.wolfsonmicro.com \
--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.