From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Jarkko Nikula <jhnikula@gmail.com>
Cc: alsa-devel@alsa-project.org, Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: [PATCHv2 3/4] ASoC: tlv320aic3x: Use regulator notifiers for optimizing the cache sync
Date: Mon, 20 Sep 2010 11:38:43 +0100 [thread overview]
Message-ID: <20100920103842.GE3414@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <1284968354-12536-4-git-send-email-jhnikula@gmail.com>
On Mon, Sep 20, 2010 at 10:39:13AM +0300, Jarkko Nikula wrote:
> There is no need to reset the codec and perform cache sync if none of the
> supply regulators were not disabled. Patch registers a notifier callback for
> each supply and callback then sets a flag to indicate when cache sync is
> required.
>
> HW writes are also needless when codec bias is off so cache_only flag is set
> independently of actual supply regulators state.
>
> Signed-off-by: Jarkko Nikula <jhnikula@gmail.com>
Acked-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
next prev parent reply other threads:[~2010-09-20 10:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-20 7:39 [PATCHv2 0/4] ASoC: tlv320aic3x: Add dynamic regulator control Jarkko Nikula
2010-09-20 7:39 ` [PATCHv2 1/4] ASoC: tlv320aic3x: Move regulator management from i2c to soc domain Jarkko Nikula
2010-09-20 9:26 ` Mark Brown
2010-09-20 17:41 ` Liam Girdwood
2010-09-20 7:39 ` [PATCHv2 2/4] ASoC: tlv320aic3x: Add runtime regulator control to aic3x_set_bias_level Jarkko Nikula
2010-09-20 9:36 ` Mark Brown
2010-09-20 7:39 ` [PATCHv2 3/4] ASoC: tlv320aic3x: Use regulator notifiers for optimizing the cache sync Jarkko Nikula
2010-09-20 10:38 ` Mark Brown [this message]
2010-09-20 7:39 ` [PATCHv2 4/4] ASoC: tlv320aic3x: Let the codec hit SND_SOC_BIAS_OFF when idle Jarkko Nikula
2010-09-20 10:39 ` 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=20100920103842.GE3414@rakim.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=jhnikula@gmail.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 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.