All of lore.kernel.org
 help / color / mirror / Atom feed
From: Liam Girdwood <lrg@ti.com>
To: "Kristo, Tero" <t-kristo@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	"broonie@opensource.wolfsonmicro.com"
	<broonie@opensource.wolfsonmicro.com>,
	"Petazzoni-XID, Thomas" <t-petazzoni@ti.com>,
	Graeme Gregory <gg@slimlogic.co.uk>
Subject: Re: [RFC 1/4] twl-regulator: extend for SMPS regulators and external controllers
Date: Fri, 8 Jul 2011 19:26:46 +0100	[thread overview]
Message-ID: <1310149606.3534.35.camel@CNA0741383> (raw)
In-Reply-To: <1310140588-26078-2-git-send-email-t-kristo@ti.com>

On Fri, 2011-07-08 at 17:56 +0200, Kristo, Tero wrote:
> This commit adds two things to the TWL regulator driver code :
> 
>  * It extends the twl4030_set_voltage() and twl4030_get_voltage()
>    functions to understand that VDD1 and VDD2 are different regulators
>    from all the other regulators: they don't support a fixed set of
>    voltages, but a wide range of voltages between two minimum and
>    maximum limits.
> 
>  * It creates a twlreg_ext_ctrl structure, which allows code outside
>    of the TWL regulator driver to implement a regulator
>    controller. Such a controller is attached using the new
>    twlreg_attach_external_controller() function of the driver. When
>    such a controller is attached to a regulator, the ->set_voltage()
>    and ->get_voltage() calls made on the regulator will be forwarded
>    to the external controller. This facility will later be used to
>    integrate the Voltage Controller and SmartReflex features of the
>    OMAP CPU with this regulator driver.

This just looks like it should just be another regulator to me. The
board will be responsible for setting up the client mapping (i.e.
whether it should use the "extended" or normal regulator).

Fwiw, Graeme has already done a lot of work on supporting Smartreflex
with TWL6025, it may be best to contact him to align your work.

Liam


  reply	other threads:[~2011-07-08 18:26 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-08 15:56 [RFC 0/4] TWL external controller support Tero Kristo
2011-07-08 15:56 ` [RFC 1/4] twl-regulator: extend for SMPS regulators and external controllers Tero Kristo
2011-07-08 18:26   ` Liam Girdwood [this message]
2011-07-09  1:21   ` Mark Brown
2011-07-08 15:56 ` [RFC 2/4] omap3beagle: Instantiate VDD1 and VDD2 regulators Tero Kristo
2011-07-08 16:22   ` Felipe Balbi
2011-07-08 15:56 ` [RFC 3/4] omap: attach external controller to VDD1/VDD2 Tero Kristo
2011-07-08 16:23   ` Felipe Balbi
2011-07-08 15:56 ` [RFC 4/4] OMAP3: beagle rev-c4: enable OPP6 Tero Kristo
2011-07-08 16:23   ` Koen Kooi
2011-07-08 16:25 ` [RFC 0/4] TWL external controller support Felipe Balbi
2011-07-09  1:24   ` Mark Brown
2011-07-09 10:40     ` Felipe Balbi
2011-07-09 10:56       ` Mark Brown
2011-07-11  8:23         ` Tero Kristo
2011-07-11 10:05           ` Mark Brown
2011-07-11 10:48             ` Tero Kristo
2011-07-11 12:11               ` Mark Brown
2011-07-11 13:06                 ` 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=1310149606.3534.35.camel@CNA0741383 \
    --to=lrg@ti.com \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=gg@slimlogic.co.uk \
    --cc=linux-omap@vger.kernel.org \
    --cc=t-kristo@ti.com \
    --cc=t-petazzoni@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.