Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Ujfalusi <peter.ujfalusi@nokia.com>
To: ext Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: "alsa-devel@alsa-project.org" <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: Tue, 7 Dec 2010 11:29:15 +0200	[thread overview]
Message-ID: <201012071129.15475.peter.ujfalusi@nokia.com> (raw)
In-Reply-To: <20101206224008.GA2862@opensource.wolfsonmicro.com>

On Tuesday 07 December 2010 00:40:08 ext Mark Brown wrote:
> 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.

Fair enough.
I did taken a look at the possibility to do the register update between DAPM 
power down and up, but I thought it is a bit big change (the place, where the 
DAPM power down and up happens is quite deep, and I was not sure how to inject 
things between those).

I'm no longer sure, when the register update should happen.
It might be worth doing the update at around the power enable for the widget.
IN that way at least we are going to filter the power updates before the 
switch:
DAC -> PGA1 -> widget -> switch -> PGA2 -> out

If we update the register for the switch before the DAPM power up, than we can 
expose the switching from DAC, PGA1, widget.
If we do the update at the same time (or around), when the power for the 
switch would have been enabled, than we are filtering the switching for the 
DAPM widgets before the switch.

-- 
Péter

  reply	other threads:[~2010-12-07  9:29 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 ` [RFC v2 0/3] ASoC: Option to reorder widget power sequence Mark Brown
2010-12-07  9:29   ` Peter Ujfalusi [this message]
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=201012071129.15475.peter.ujfalusi@nokia.com \
    --to=peter.ujfalusi@nokia.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.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