From: Nishanth Menon <nm@ti.com>
To: "Gopinath, Thara" <thara@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"khilman@deeprootsystems.com" <khilman@deeprootsystems.com>,
"paul@pwsan.com" <paul@pwsan.com>,
"Cousson, Benoit" <b-cousson@ti.com>,
"Sripathy, Vishwanath" <vishwanath.bs@ti.com>,
"Sawant, Anand" <sawant@ti.com>
Subject: Re: [PATCH] OMAP3: PM: Adding T2 enabling of smartreflex
Date: Wed, 05 Jan 2011 07:37:22 -0600 [thread overview]
Message-ID: <4D247412.5070008@ti.com> (raw)
In-Reply-To: <5A47E75E594F054BAF48C5E4FC4B92AB0373D2F0E0@dbde02.ent.ti.com>
Gopinath, Thara wrote, on 01/05/2011 04:46 AM:
[..]
> Yes you are right. The SR I2C needs to be enabled for vp force update
> and vc bypass method of voltage scaling as well as for smartreflex
> feature. Are you telling that there are platforms out there using OMAP3
> and T2 and still using VMODE or VSEL. As far as I am aware our h/w folks themselves do not recommend these methods.
;) not every one likes to follow recommendations rt? but yeah, there are
folks who use vmode for 3430, vsel is possible even for 3630 - using
class2 implementation if desired or forced to if the SR lines are not
hooked up on the board.
--
Regards,
Nishanth Menon
next prev parent reply other threads:[~2011-01-05 13:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-31 8:07 [PATCH] OMAP3: PM: Adding T2 enabling of smartreflex Thara Gopinath
2011-01-03 15:51 ` Nishanth Menon
2011-01-05 10:46 ` Gopinath, Thara
2011-01-05 13:37 ` Nishanth Menon [this message]
2011-01-04 22:48 ` Kevin Hilman
2011-01-05 10:51 ` Gopinath, Thara
2011-01-05 17:15 ` Kevin Hilman
-- strict thread matches above, loose matches on Subject: below --
2011-01-19 9:07 shweta gulati
2011-01-19 9:24 ` Nishanth Menon
[not found] ` <AANLkTinRh+4eBf_Pu8DCAMyc+9D-bMVuV8kxwL5rOsXg@mail.gmail.com>
2011-01-19 12:24 ` Nishanth Menon
2011-01-20 13:14 ` Gulati, Shweta
2011-01-19 10:29 ` Premi, Sanjeev
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=4D247412.5070008@ti.com \
--to=nm@ti.com \
--cc=b-cousson@ti.com \
--cc=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
--cc=sawant@ti.com \
--cc=thara@ti.com \
--cc=vishwanath.bs@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