linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tero Kristo <t-kristo@ti.com>
To: "Hilman, Kevin" <khilman@ti.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCHv4 3/4] omap: smps: add smps regulator init to voltage.c
Date: Mon, 29 Aug 2011 11:06:49 +0300	[thread overview]
Message-ID: <1314605209.3699.7.camel@sokoban> (raw)
In-Reply-To: <87k4arr0bi.fsf@ti.com>

On Fri, 2011-08-05 at 23:54 +0200, Hilman, Kevin wrote:
> Tero Kristo <t-kristo@ti.com> writes:
> 
> > All voltagedomains that have support for vc and vp are now automatically
> > registered with SMPS regulator driver. Voltage.c builds a platform device
> > structure for this purpose during late init.
> >
> > Signed-off-by: Tero Kristo <t-kristo@ti.com>
> 
> [...]
> 
> > +static void smps_add_regulator(struct platform_device *smps_dev,
> > +			       struct voltagedomain *voltdm)
> > +{
> > +	struct omap_smps_platform_data *info;
> > +	struct regulator_init_data *init_data;
> > +	struct regulator_consumer_supply *supply;
> > +
> > +	if (!smps_dev || !voltdm)
> > +		return;
> > +
> > +	info = smps_dev->dev.platform_data;
> > +
> > +	init_data = kzalloc(sizeof(struct regulator_init_data), GFP_KERNEL);
> > +	supply = kzalloc(sizeof(struct regulator_consumer_supply), GFP_KERNEL);
> > +
> > +	if (!init_data || !supply) {
> > +		kfree(init_data);
> > +		kfree(supply);
> > +		return;
> > +	}
> > +	supply->supply = "vcc";
> > +	supply->dev_name = voltdm->name;
> > +	init_data->constraints.min_uV = 600000;
> > +	init_data->constraints.max_uV = 1450000;
> 
> These values should come from the OMAP/PMIC limitations, not from hard
> coded values.

True. Should this wait until the work is finished with the PMIC
parameter work or should I try to figure out a way to do this already
now?

> 
> Kevin



Texas Instruments Oy, Tekniikantie 12, 02150 Espoo. Y-tunnus: 0115040-6. Kotipaikka: Helsinki
 


  reply	other threads:[~2011-08-29  8:06 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-28 11:48 [PATCHv4 0/4] OMAP SMPS regulator driver Tero Kristo
2011-07-28 11:48 ` [PATCHv4 1/4] omap: voltage: add a stub header file Tero Kristo
2011-08-05 19:35   ` Kevin Hilman
2011-07-28 11:48 ` [PATCHv4 2/4] regulator: omap smps regulator driver Tero Kristo
2011-07-29  9:48   ` Mark Brown
2011-08-05 19:33     ` Kevin Hilman
2011-08-08  8:28       ` Liam Girdwood
2011-08-22 22:39         ` Kevin Hilman
2011-08-23  7:28           ` Liam Girdwood
2011-08-05 23:48   ` Kevin Hilman
2011-07-28 11:48 ` [PATCHv4 3/4] omap: smps: add smps regulator init to voltage.c Tero Kristo
2011-08-05 21:52   ` Kevin Hilman
2011-08-29  8:21     ` Tero Kristo
2011-08-05 21:54   ` Kevin Hilman
2011-08-29  8:06     ` Tero Kristo [this message]
2011-08-05 23:37   ` Kevin Hilman
2011-08-29  7:56     ` Tero Kristo
2011-07-28 11:48 ` [PATCHv4 4/4] TEMP: OMAP3: beagle rev-c4: enable OPP6 Tero Kristo
2011-08-05 19:41   ` Kevin Hilman

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=1314605209.3699.7.camel@sokoban \
    --to=t-kristo@ti.com \
    --cc=khilman@ti.com \
    --cc=linux-omap@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).