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 10:56:48 +0300 [thread overview]
Message-ID: <1314604609.3699.5.camel@sokoban> (raw)
In-Reply-To: <8762mbph0f.fsf@ti.com>
Hi Kevin,
Sorry for bit late reply, I've been on holiday during last 3 weeks.
On Sat, 2011-08-06 at 01:37 +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>
>
> With the creation of this "dummy" platform device, I'm a bit confused
> about how is the mapping from device to regulator meant to work here.
>
> e.g., for MPU DVFS, if I want to also scale voltage in the CPUfreq
> driver, I would do something like
>
> dev = omap2_get_mpuss_device()
>
> and then want to somehow get the regulator associated with the MPU
> device so I can do a regulator_set_voltage(). What would I use for the
> id argument of regulator_get()?
Hmm right, I haven't been thinking about this part in too much detail.
However, the regulator names are built in following way:
- take voltdm name (e.g. mpu_iva)
- add "VDD_" in the beginning
- capitalize whole thing (results in VDD_MPU_IVA)
> What's missing (at least in my mind) is the mapping of devices to
> regulators.
True, should I think of something for this?
>
> Specifically, this part doesn't seem right:
>
> > + supply->supply = "vcc";
> > + supply->dev_name = voltdm->name;
>
> becase voltdm->name is not a device name.
>
> Kevin
Texas Instruments Oy, Tekniikantie 12, 02150 Espoo. Y-tunnus: 0115040-6. Kotipaikka: Helsinki
next prev parent reply other threads:[~2011-08-29 7:56 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
2011-08-05 23:37 ` Kevin Hilman
2011-08-29 7:56 ` Tero Kristo [this message]
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=1314604609.3699.5.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).