From: Kevin Hilman <khilman@ti.com>
To: Tero Kristo <t-kristo@ti.com>
Cc: linux-omap@vger.kernel.org, Tony Lindgren <tony@atomide.com>,
Todd Poynor <toddpoynor@google.com>,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
Liam Girdwood <lrg@ti.com>, Graeme Gregory <gg@slimlogic.co.uk>
Subject: Re: [PATCHv5 1/4] regulator: omap smps regulator driver
Date: Tue, 27 Sep 2011 13:06:35 -0700 [thread overview]
Message-ID: <87bou5zr5g.fsf@ti.com> (raw)
In-Reply-To: <1314803478-15634-2-git-send-email-t-kristo@ti.com> (Tero Kristo's message of "Wed, 31 Aug 2011 18:11:15 +0300")
Tero Kristo <t-kristo@ti.com> writes:
> OMAP SMPS regulator driver provides access to OMAP voltage processor
> controlled regulators. These include VDD_MPU and VDD_CORE for OMAP3 and
> additionally VDD_IVA for OMAP4. SMPS regulators use the OMAP voltage
> layer for the actual voltage regulation operations.
>
> Signed-off-by: Tero Kristo <t-kristo@ti.com>
> Cc: Kevin Hilman <khilman@ti.com>
> Cc: Tony Lindgren <tony@atomide.com>
> Cc: Todd Poynor <toddpoynor@google.com>
> Cc: Mark Brown <broonie@opensource.wolfsonmicro.com>
> Cc: Liam Girdwood <lrg@ti.com>
> Cc: Graeme Gregory <gg@slimlogic.co.uk>
I believe this was already ack'd by Mark. Have there been any
significan changes since then?
Kevin
next prev parent reply other threads:[~2011-09-27 20:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-31 15:11 [PATCHv5 0/4] omap smps regulator driver Tero Kristo
2011-08-31 15:11 ` [PATCHv5 1/4] regulator: " Tero Kristo
2011-09-27 20:06 ` Kevin Hilman [this message]
2011-09-28 6:49 ` Tero Kristo
2011-08-31 15:11 ` [PATCHv5 2/4] omap: voltage: added mapping from voltagedomains to processor devices Tero Kristo
2011-08-31 15:11 ` [PATCHv5 3/4] omap: smps: add smps regulator init to voltage.c Tero Kristo
2011-08-31 15:11 ` [PATCHv5 4/4] TEMP: OMAP3: beagle rev-c4: enable OPP6 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=87bou5zr5g.fsf@ti.com \
--to=khilman@ti.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=gg@slimlogic.co.uk \
--cc=linux-omap@vger.kernel.org \
--cc=lrg@ti.com \
--cc=t-kristo@ti.com \
--cc=toddpoynor@google.com \
--cc=tony@atomide.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox