public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Heiko Stübner" <heiko@sntech.de>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Liam Girdwood <lrg@ti.com>,
	linux-kernel@vger.kernel.org, Axel Lin <axel.lin@gmail.com>
Subject: Re: regulator: Policy for setting current limits
Date: Tue, 7 Aug 2012 01:19:34 +0200	[thread overview]
Message-ID: <201208070119.35129.heiko@sntech.de> (raw)
In-Reply-To: <20120806115632.GB16861@opensource.wolfsonmicro.com>

Am Montag, 6. August 2012, 13:56:33 schrieb Mark Brown:
> On Mon, Aug 06, 2012 at 01:27:56AM +0200, Heiko Stübner wrote:
> > 500). Therefore if 500mA are the upper limit but the regulator also
> > supports lower values, these lower values always get selected (100mA in
> > my case). In contrast pda_power sets the target current as both lower
> > and upper limit.
> 
> This isn't good, it means that the regulator has to be able to deliver
> exactly the limit requested.
> 
> > (a) let the gpio-regulator select the max current (in contrast to the
> > minimum voltage)
> > (b) change gpio-vbus to also use the target current as min and max value
> > (c) something else
> 
> Regulators should be tending to the maximum in the available range and
> consumers should specify the widest range possible so both a and b.

Is this true for all regulators (i.e. voltage and currency regulators)?

Because 4dbd8f63f07a (regulator: gpio-regulator: Set the smallest 
voltage/current in the specified range) implemented the exact oposite.

Thanks
Heiko

  reply	other threads:[~2012-08-06 23:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-05 23:27 regulator: Policy for setting current limits Heiko Stübner
2012-08-06 11:56 ` Mark Brown
2012-08-06 23:19   ` Heiko Stübner [this message]
2012-08-07 17:06     ` 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=201208070119.35129.heiko@sntech.de \
    --to=heiko@sntech.de \
    --cc=axel.lin@gmail.com \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lrg@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox