All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@ti.com>
To: t-kristo@ti.com
Cc: Mark Brown <broonie@opensource.wolfsonmicro.com>,
	Benoit Cousson <b-cousson@ti.com>,
	linux-omap@vger.kernel.org, Liam Girdwood <lrg@ti.com>,
	Samuel Ortiz <sameo@linux.intel.com>
Subject: Re: [PATCHv8 4/5] twl4030: add support for external voltage get/set
Date: Tue, 14 Feb 2012 11:16:23 -0800	[thread overview]
Message-ID: <87fwed6xa0.fsf@ti.com> (raw)
In-Reply-To: <1329223666.4102.319.camel@sokoban> (Tero Kristo's message of "Tue, 14 Feb 2012 14:47:46 +0200")

Tero Kristo <t-kristo@ti.com> writes:

> On Tue, 2012-01-10 at 19:10 +0000, Mark Brown wrote:
>> On Tue, Jan 10, 2012 at 07:19:18AM -0800, Kevin Hilman wrote:
>> 
>> > Yes, some of the control still goes via the normal path (although I
>> > forget which, maybe Benoit can remind us), so I think it's best to add
>> > the HW control part to each regulator that might uses it.
>> 
>> > Ideally this could be facilitated by adding the extentions to the
>> > regulator core so the amount of code needed for each regulator driver
>> > would be minimal.
>> 
>> I think the original version of the patch was something along those
>> lines but it was just a general facility which ignored the regulator
>> driver entirely which didn't feel well integrated.  The discussion
>> suggested that this wasn't something that'd work with other regulators
>> so a per-driver solution seemed OK.
>
> Coming back to this patch now as I have time to look at it, what is the
> general opinion, is it acceptable to patch the regulator core to add
> support for the external controller or should I just resend the latest
> version with changes Mark suggested? This will probably mean that once
> we add new regulator drivers (e.g. pmics) we may need to duplicate the
> external controller support here.

How about you keep it in the regulator driver for now, and when we need
to abstract it out, we make the case for it then.

Kevin

  reply	other threads:[~2012-02-14 19:16 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-09 15:29 [PATCHv8 0/5] SMPS regulator driver Tero Kristo
2011-12-09 15:29 ` [PATCHv8 1/5] TEMP: OMAP3: beagle rev-c4: enable OPP6 Tero Kristo
2011-12-09 15:29 ` [PATCHv8 2/5] omap3: voltage: fix channel configuration Tero Kristo
2011-12-10  0:21   ` Kevin Hilman
2011-12-12  9:34     ` Tero Kristo
2011-12-12 15:02       ` Kevin Hilman
2011-12-09 15:29 ` [PATCHv8 3/5] omap3: add common twl configurations for vdd1 and vdd2 Tero Kristo
2011-12-09 15:29 ` [PATCHv8 4/5] twl4030: add support for external voltage get/set Tero Kristo
2011-12-19  8:33   ` Samuel Ortiz
2011-12-19  9:56     ` Girdwood, Liam
2011-12-20  0:31       ` Mark Brown
     [not found]         ` <87hb04wesx.fsf@ti.com>
2012-01-10  8:05           ` Tero Kristo
2012-01-10  1:11   ` Kevin Hilman
2012-01-10  3:30     ` Mark Brown
2012-01-10 15:19       ` Kevin Hilman
2012-01-10 19:10         ` Mark Brown
2012-02-14 12:47           ` Tero Kristo
2012-02-14 19:16             ` Kevin Hilman [this message]
2012-02-15  8:38               ` Tero Kristo
2011-12-09 15:29 ` [PATCHv8 5/5] omap3: twl: add external controllers for core voltage regulators Tero Kristo

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=87fwed6xa0.fsf@ti.com \
    --to=khilman@ti.com \
    --cc=b-cousson@ti.com \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=lrg@ti.com \
    --cc=sameo@linux.intel.com \
    --cc=t-kristo@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.