All of lore.kernel.org
 help / color / mirror / Atom feed
From: Liam Girdwood <lrg@slimlogic.co.uk>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCHv2 1/4] ASoC: tlv320aic3x: Move regulator management from i2c to soc domain
Date: Mon, 20 Sep 2010 18:41:42 +0100	[thread overview]
Message-ID: <1285004502.3048.83.camel@odin> (raw)
In-Reply-To: <20100920092637.GA31167@sirena.org.uk>

On Mon, 2010-09-20 at 10:26 +0100, Mark Brown wrote:
> On Mon, Sep 20, 2010 at 10:39:11AM +0300, Jarkko Nikula wrote:
> > It will be easier to keep regulator enable/disable calls in sync when dynamic
> > regulator management is added if regulator management is moved from
> > aic3x_i2c_probe/_remove to aic3x_probe/_remove.
> > 
> > Signed-off-by: Jarkko Nikula <jhnikula@gmail.com>
> 
> Acked-by: Mark Brown <broonie@opensource.wolfsonmicro.com>

All Applied.

Thanks

Liam
-- 
Freelance Developer, SlimLogic Ltd
ASoC and Voltage Regulator Maintainer.
http://www.slimlogic.co.uk

  reply	other threads:[~2010-09-20 17:41 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 [this message]
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
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=1285004502.3048.83.camel@odin \
    --to=lrg@slimlogic.co.uk \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.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.