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: Jonathan Cameron <jic23@cam.ac.uk>,
	Jean Delvare <khali@linux-fr.org>,
	lm-sensors <lm-sensors@lm-sensors.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [lm-sensors] regulator: regulator_get behaviour without
Date: Wed, 07 Apr 2010 09:50:23 +0000	[thread overview]
Message-ID: <1270633823.3248.38.camel@odin> (raw)
In-Reply-To: <1F9C625F-0467-4C6D-B57F-2E4FCAC76031@opensource.wolfsonmicro.com>

On Tue, 2010-04-06 at 19:19 +0100, Mark Brown wrote:
> On 6 Apr 2010, at 17:25, Jonathan Cameron <jic23@cam.ac.uk> wrote:
> 
> > On 04/06/10 16:27, Liam Girdwood wrote:
> >>>
> >>>
> >>>
> >>
> >> I suppose this is something we may look into more when we have more
> >> clients.
> > Makes sense.  There will probably be quite a few IIO drivers over  
> > the next
> > few months doing much the same as sht15, where the voltage ref for  
> > devices
> > may well be fed by a regulator.  In that case, we may only offer the  
> > option
> > of using an external v_ref if the regulator is available.  Many  
> > devices have
> > an internal regulator to provide it so typically we'll start them up  
> > using that
> > and provide an interface to switch to external regulator if one is  
> > available.
> > I haven't thought through exactly how this will work as yet. I'll cc  
> > people in
> > when this comes up.
> 
> TBH this seems like a very vanilla use case - there may be some small  
> advantage to representing the internal regulator via the regulator API  
> but that's about the only thing I can think might be a bit odd.
> --

Although may be quite useful here for any mfd devices where the core has
regulators that only supply the other on chip functions.

Liam 

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


_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

WARNING: multiple messages have this Message-ID (diff)
From: Liam Girdwood <lrg@slimlogic.co.uk>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Jonathan Cameron <jic23@cam.ac.uk>,
	Jean Delvare <khali@linux-fr.org>,
	lm-sensors <lm-sensors@lm-sensors.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [lm-sensors] regulator: regulator_get behaviour without CONFIG_REGULATOR set
Date: Wed, 07 Apr 2010 10:50:23 +0100	[thread overview]
Message-ID: <1270633823.3248.38.camel@odin> (raw)
In-Reply-To: <1F9C625F-0467-4C6D-B57F-2E4FCAC76031@opensource.wolfsonmicro.com>

On Tue, 2010-04-06 at 19:19 +0100, Mark Brown wrote:
> On 6 Apr 2010, at 17:25, Jonathan Cameron <jic23@cam.ac.uk> wrote:
> 
> > On 04/06/10 16:27, Liam Girdwood wrote:
> >>>
> >>>
> >>>
> >>
> >> I suppose this is something we may look into more when we have more
> >> clients.
> > Makes sense.  There will probably be quite a few IIO drivers over  
> > the next
> > few months doing much the same as sht15, where the voltage ref for  
> > devices
> > may well be fed by a regulator.  In that case, we may only offer the  
> > option
> > of using an external v_ref if the regulator is available.  Many  
> > devices have
> > an internal regulator to provide it so typically we'll start them up  
> > using that
> > and provide an interface to switch to external regulator if one is  
> > available.
> > I haven't thought through exactly how this will work as yet. I'll cc  
> > people in
> > when this comes up.
> 
> TBH this seems like a very vanilla use case - there may be some small  
> advantage to representing the internal regulator via the regulator API  
> but that's about the only thing I can think might be a bit odd.
> --

Although may be quite useful here for any mfd devices where the core has
regulators that only supply the other on chip functions.

Liam 

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


  reply	other threads:[~2010-04-07  9:50 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <2122967437.461270223106350.JavaMail.root@mail.savoirfairelinux.com>
2010-04-02 15:47 ` [lm-sensors] regulator: regulator_get behaviour without Jerome Oufella
2010-04-02 15:47   ` regulator: regulator_get behaviour without CONFIG_REGULATOR set Jerome Oufella
2010-04-02 16:00   ` [lm-sensors] regulator: regulator_get behaviour without Mark Brown
2010-04-02 16:00     ` regulator: regulator_get behaviour without CONFIG_REGULATOR set Mark Brown
2010-04-02 16:44     ` [lm-sensors] regulator: regulator_get behaviour without Jean Delvare
2010-04-02 16:44       ` [lm-sensors] regulator: regulator_get behaviour without CONFIG_REGULATOR set Jean Delvare
2010-04-02 18:51       ` [lm-sensors] regulator: regulator_get behaviour Mark Brown
2010-04-02 18:51         ` [lm-sensors] regulator: regulator_get behaviour without CONFIG_REGULATOR set Mark Brown
2010-04-02 19:30         ` [lm-sensors] regulator: regulator_get behaviour without Jean Delvare
2010-04-02 19:30           ` [lm-sensors] regulator: regulator_get behaviour without CONFIG_REGULATOR set Jean Delvare
2010-04-02 20:45           ` [lm-sensors] regulator: regulator_get behaviour Mark Brown
2010-04-02 20:45             ` [lm-sensors] regulator: regulator_get behaviour without CONFIG_REGULATOR set Mark Brown
2010-04-03 15:37             ` [lm-sensors] regulator: regulator_get behaviour without Jean Delvare
2010-04-03 15:37               ` [lm-sensors] regulator: regulator_get behaviour without CONFIG_REGULATOR set Jean Delvare
2010-04-05 13:23               ` [lm-sensors] regulator: regulator_get behaviour without Mark Brown
2010-04-05 13:23                 ` [lm-sensors] regulator: regulator_get behaviour without CONFIG_REGULATOR set Mark Brown
2010-04-06 12:04                 ` [lm-sensors] regulator: regulator_get behaviour without Jonathan Cameron
2010-04-06 12:04                   ` [lm-sensors] regulator: regulator_get behaviour without CONFIG_REGULATOR set Jonathan Cameron
2010-04-06 15:27                 ` [lm-sensors] regulator: regulator_get behaviour without Liam Girdwood
2010-04-06 15:27                   ` [lm-sensors] regulator: regulator_get behaviour without CONFIG_REGULATOR set Liam Girdwood
2010-04-06 16:25                   ` [lm-sensors] regulator: regulator_get behaviour without Jonathan Cameron
2010-04-06 16:25                     ` [lm-sensors] regulator: regulator_get behaviour without CONFIG_REGULATOR set Jonathan Cameron
2010-04-06 18:19                     ` [lm-sensors] regulator: regulator_get behaviour without Mark Brown
2010-04-06 18:19                       ` [lm-sensors] regulator: regulator_get behaviour without CONFIG_REGULATOR set Mark Brown
2010-04-07  9:50                       ` Liam Girdwood [this message]
2010-04-07  9:50                         ` Liam Girdwood
2010-04-07 11:24                       ` [lm-sensors] regulator: regulator_get behaviour without Jonathan Cameron
2010-04-07 11:24                         ` [lm-sensors] regulator: regulator_get behaviour without CONFIG_REGULATOR set Jonathan Cameron
2010-04-07 11:57                         ` [lm-sensors] regulator: regulator_get behaviour without Mark Brown
2010-04-07 11:57                           ` [lm-sensors] regulator: regulator_get behaviour without CONFIG_REGULATOR set 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=1270633823.3248.38.camel@odin \
    --to=lrg@slimlogic.co.uk \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=jic23@cam.ac.uk \
    --cc=khali@linux-fr.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm-sensors@lm-sensors.org \
    /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.