All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kishon Vijay Abraham I <kishon@ti.com>
To: Mark Brown <broonie@kernel.org>
Cc: Laxman Dewangan <ldewangan@nvidia.com>,
	"lgirdwood@gmail.com" <lgirdwood@gmail.com>,
	"sameo@linux.intel.com" <sameo@linux.intel.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"gg@slimlogic.co.uk" <gg@slimlogic.co.uk>,
	"ian@slimlogic.co.uk" <ian@slimlogic.co.uk>,
	"balbi@ti.com" <balbi@ti.com>
Subject: Re: [RFC PATCH] regulator: palmas: enable all modes for SMPS10
Date: Tue, 4 Jun 2013 14:38:08 +0530	[thread overview]
Message-ID: <51ADAE78.4050900@ti.com> (raw)
In-Reply-To: <20130601210511.GT16790@sirena.org.uk>

Hi,

On Sunday 02 June 2013 02:35 AM, Mark Brown wrote:
> On Sun, Jun 02, 2013 at 12:33:10AM +0530, Laxman Dewangan wrote:
>> On Sunday 02 June 2013 12:15 AM, Mark Brown wrote:
>
>>> No, that makes no sense at all to me.  Why do you think this maps onto
>>> the set mode API?  Modes are all about accuracy of regulation.
>
>> I mapped this to the regulation under different load, Fast mode is
>> in heavy load and so boost enable, normal/idle mode for normal load
>> and so bypass.
>
> This is still not making any sense.  The quality of regulation and
> output voltage are essentially orthogonal, and obviously there's a
> specific API for bypass which is something different again to both
> mode and output voltage selection.

Do you recommend adding API's (similar to bypass) for BOOST and SWITCH?

Thanks
Kishon

  reply	other threads:[~2013-06-04  9:08 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-30 10:56 [RFC PATCH] regulator: palmas: enable all modes for SMPS10 Kishon Vijay Abraham I
2013-05-30 11:32 ` Mark Brown
2013-05-30 12:54   ` Kishon Vijay Abraham I
2013-06-01 18:42     ` Mark Brown
2013-05-30 13:00   ` Laxman Dewangan
2013-06-01 18:45     ` Mark Brown
2013-06-01 19:03       ` Laxman Dewangan
2013-06-01 21:05         ` Mark Brown
2013-06-04  9:08           ` Kishon Vijay Abraham I [this message]
2013-06-04  9:38             ` Mark Brown
2013-06-04  9:43               ` Kishon Vijay Abraham I
2013-06-04 10:05                 ` Mark Brown
2013-06-10  9:50                   ` Kishon Vijay Abraham I
2013-06-10 10:03                     ` Mark Brown
2013-06-10 11:03                       ` Kishon Vijay Abraham I
2013-06-10 12:49                         ` Mark Brown
2013-06-12  8:42                           ` Laxman Dewangan
2013-06-12 14:14                             ` Mark Brown
2013-06-12 14:31                               ` gg
2013-06-12 14:51                                 ` Mark Brown
2013-06-12 15:23                                   ` gg
2013-06-14 12:34                                     ` Laxman Dewangan
2013-06-18  8:27                                       ` Kishon Vijay Abraham I

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=51ADAE78.4050900@ti.com \
    --to=kishon@ti.com \
    --cc=balbi@ti.com \
    --cc=broonie@kernel.org \
    --cc=gg@slimlogic.co.uk \
    --cc=ian@slimlogic.co.uk \
    --cc=ldewangan@nvidia.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sameo@linux.intel.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.