From: Kevin Hilman <khilman@ti.com>
To: Tero Kristo <t-kristo@ti.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCHv4 3/4] omap: smps: add smps regulator init to voltage.c
Date: Fri, 05 Aug 2011 16:37:04 -0700 [thread overview]
Message-ID: <8762mbph0f.fsf@ti.com> (raw)
In-Reply-To: <1311853739-18984-4-git-send-email-t-kristo@ti.com> (Tero Kristo's message of "Thu, 28 Jul 2011 14:48:58 +0300")
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()?
What's missing (at least in my mind) is the mapping of devices to
regulators.
Specifically, this part doesn't seem right:
> + supply->supply = "vcc";
> + supply->dev_name = voltdm->name;
becase voltdm->name is not a device name.
Kevin
next prev parent reply other threads:[~2011-08-05 23:37 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 [this message]
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=8762mbph0f.fsf@ti.com \
--to=khilman@ti.com \
--cc=linux-omap@vger.kernel.org \
--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.