From: Kevin Hilman <khilman@ti.com>
To: Shweta Gulati <shweta.gulati@ti.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCH 0/3]: Update OPP Table and Voltage Rail Values
Date: Tue, 01 Mar 2011 12:52:39 -0800 [thread overview]
Message-ID: <87aahek1go.fsf@ti.com> (raw)
In-Reply-To: <1297836995-8747-1-git-send-email-shweta.gulati@ti.com> (Shweta Gulati's message of "Wed, 16 Feb 2011 11:46:35 +0530")
Shweta Gulati <shweta.gulati@ti.com> writes:
> The series mainly does below:
>
> OMAP4 only
> - Update MPU VOltage rail values for all OPPs
> - Enable OPP-Nitro and OPP-Turbo for all boards
> OMAP2PLUS
> -Replace hardcoded Voltage values in OPP Table
> with Voltage Macros.
>
> Baseline:
> git://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-omap-pm.git
> Branch: pm
What is the dependency on the PM branch?
> Tested on OMAP4430 SDP, OMAP3630 SDP and OMAP3430 SDP.
Tested in what way?
This series looks OK to me, but would like to see an ack/reviewed-by
from Nishanth before merging.
Also, please Cc linux-arm-kernel on patches intended for mainline merge.
Kevin
> Shweta Gulati (2):
> OMAP4: Revise MPU Voltage rail values.
> OMAP4: Enable Turbo and Nitro OPP for OMAP4
>
> Vishwanath BS (1):
> OMAP2+: Replace Voltage values with Macros.
>
> arch/arm/mach-omap2/opp3xxx_data.c | 47 +++++++++++++++--------------
> arch/arm/mach-omap2/opp4xxx_data.c | 13 ++++----
> arch/arm/plat-omap/include/plat/voltage.h | 8 ++--
> 3 files changed, 35 insertions(+), 33 deletions(-)
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2011-03-01 20:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-16 6:16 [PATCH 0/3]: Update OPP Table and Voltage Rail Values Shweta Gulati
2011-03-01 5:32 ` Gulati, Shweta
2011-03-01 20:52 ` Kevin Hilman [this message]
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=87aahek1go.fsf@ti.com \
--to=khilman@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=shweta.gulati@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox