All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: Laxman Dewangan <ldewangan@nvidia.com>,
	lrg@ti.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] regulator: max8973: add regulator driver support
Date: Tue, 20 Nov 2012 09:43:58 +0900	[thread overview]
Message-ID: <20121120004356.GC4483@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1211190900110.11024@axis700.grange>

[-- Attachment #1: Type: text/plain, Size: 1413 bytes --]

On Mon, Nov 19, 2012 at 11:52:42AM +0100, Guennadi Liakhovetski wrote:

> Thanks for submitting this driver! The notion of DVS regulators was new to 
> me, so, I checked http://www.ti.com/lit/an/sbva020/sbva020.pdf for a short 
> description. After that I had a look at a couple of existing DVS regulator 

Do you just mean regulators that have a quick voltage change ability/

> drivers in the tree. Well, I came to two conclusions so far: (1) The 
> current regulator API is not very well suitable for such regulators. I 
> would imagine, one would need two methods: for setting the "normal" and 
> the DVS voltage. Instead of this drivers are trying to be smart at 
> guessing, which voltage the user is trying to set now... (2) Drivers do 
> this in different ways and at least out of the 2 drivers I looked at both 
> have bugs and different ones at that. I'll send a separate email, 
> describing what I found suspicious in them.

The thing I'd like to see factored out here is the LRU mechanism,
otherwise I think the situation is pretty good.  Some of the older
devices should use a different scheme to modern ones as the hardware
they have to interoperate is different.

> Of course, all the above was just my DVS-newbie impression, which can very 
> well be absolutely wrong.
> 
> > 
> > Add regulator driver for this device.

*ALWAYS* delete irrelevant text when replying.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2012-11-20  0:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-19  1:28 [PATCH] regulator: max8973: add regulator driver support Laxman Dewangan
2012-11-19  8:03 ` Mark Brown
2012-11-19 10:52 ` Guennadi Liakhovetski
2012-11-20  0:43   ` Mark Brown [this message]
2012-11-20  7:55     ` Guennadi Liakhovetski
2012-11-20  8:08       ` Mark Brown
2012-11-20  8:23         ` Guennadi Liakhovetski
2012-11-20  8:32           ` Mark Brown
2012-11-20  1:54   ` Laxman Dewangan
2012-11-20  9:42     ` Guennadi Liakhovetski
2012-11-23  0:29       ` Laxman Dewangan

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=20121120004356.GC4483@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=g.liakhovetski@gmx.de \
    --cc=ldewangan@nvidia.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 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.