From: Nishanth Menon <nm@ti.com>
To: Kevin Hilman <khilman@ti.com>
Cc: Shweta Gulati <shweta.gulati@ti.com>,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH V2 0/3]: OMAP4: Update OPP Table and Voltage Rail Values
Date: Tue, 08 Mar 2011 08:19:31 +0530 [thread overview]
Message-ID: <4D75993B.1090606@ti.com> (raw)
In-Reply-To: <87vczuzhqj.fsf@ti.com>
Kevin Hilman wrote, on 03/08/2011 04:00 AM:
> Shweta Gulati<shweta.gulati@ti.com> writes:
>
>> The Series Updates OPP Table for MPU, add OPP enteries
>> for IVA and update Voltage Rail values for MPU/IVA.
>>
>> It is based on the Patch which replaces
>> Voltage values with Macros, Submitted by
>> Nishanth Menon
>> https://patchwork.kernel.org/patch/607541/
>>
>> Branch: pm-core
>>
>> Tested on OMAP4430 SDP.
>>
>> V2:
>> Rebased on pm-core and incorporated
>> comments from Nishanth Menon.
>
> This version looks OK to me.
>
> Will queue for 2.6.39 after I see an Ack from Nishanth.
I have Acked the series.
unrelated to this series, as commented in:
http://marc.info/?l=linux-omap&m=129955003611548&w=2
I had initially considered the option of rounding the DM values to
TWL6030 step size, then realized that there are TPS chips with 25mV and
custom PMICs with step sizes of 10mV. we probably need a solution for
.40 merge window where the PMIC variances (as brought out by Sanjeev as
well in http://marc.info/?t=129848405600010&r=1&w=2 and elsewhere), are
handled transparently. This ofcourse is not related to the current series.
--
Regards,
Nishanth Menon
prev parent reply other threads:[~2011-03-08 2:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-05 9:50 [PATCH V2 0/3]: OMAP4: Update OPP Table and Voltage Rail Values Shweta Gulati
2011-03-07 22:30 ` Kevin Hilman
2011-03-08 2:49 ` Nishanth Menon [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=4D75993B.1090606@ti.com \
--to=nm@ti.com \
--cc=khilman@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--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