From: Nishanth Menon <nm@ti.com>
To: "linux-omap <linux-omap"@vger.kernel.org
Cc: Imberton Guilhem <guilhem.imberton@motorola.com>,
Mike Chan <mikechan@google.com>, Rajendra Nayak <rnayak@ti.com>,
Roger Quadros <ext-roger.quadros@nokia.com>,
Kalle Jokiniemi <ext-kalle.jokiniemi@nokia.com>,
Teerth Reddy <teerth@ti.com>,
Kevin Hilman <khilman@deeprootsystems.com>,
Paul Walmsley <paul@pwsan.com>,
Hogander Jouni <jouni.hogander@nokia.com>,
Nishanth Menon <nm@ti.com>
Subject: [PATCH 0/2 v3] OMAP3: PM: refactor Smart Reflex
Date: Sat, 24 Oct 2009 00:15:50 -0500 [thread overview]
Message-ID: <1256361352-9968-1-git-send-email-nm@ti.com> (raw)
In-Reply-To: <OMAP3:PM:SR: SmartReflex Refactor Rev3.0>
Hi,
Based on linux-omap PM branch(kevin's tree) commit
25c7b64bf80176463aa741407318e0e6b21cfd71
V4 - More changes:
* Guilhem's review comments for timeout return value
* Changes to make sr_list and OPP table dynamic selection
based on cpu_type
* vsel dbgfs entry added for folks who like to see voltage
decisions made by OMAP Voltage processor
(e.g. without a scope)
* nvalue_opp is a variable array
* omapsr_list introduced, initialized runtime based on type
of omap - currently omap3430 only- but makes 3630 possible
* all opp searches are isolated to opp accessor functions
V3 - Bunch of changes:
* Introduce debugfs entries for SR - since these
are variable updates, you can essentially do what we do
with test values, change things but without a rebuild!
* Removed the test values altogether
* srid is standardised to u8 and it is not a bit field
* Guilhem's changes for non-twl5030 PMIC incorporated
* uses ioremap
V2 - made possible to work with non twl5030 PMICs
V1 - original rewrite
Requesting as much testing as possible and all comments welcome.
Nishanth Menon (2):
OMAP3: PM: SR: prepare: remove old SR code
OMAP3: PM: SR: SmartReflex Refactor Rev4.0
arch/arm/mach-omap2/pm-debug.c | 3 +
arch/arm/mach-omap2/resource34xx.c | 8 +-
arch/arm/mach-omap2/smartreflex.c | 2180 +++++++++++++++++++++++-------------
arch/arm/mach-omap2/smartreflex.h | 280 +++---
arch/arm/plat-omap/Kconfig | 15 +-
5 files changed, 1544 insertions(+), 942 deletions(-)
Regards,
Nishanth Menon
next parent reply other threads:[~2009-10-24 5:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <OMAP3:PM:SR: SmartReflex Refactor Rev3.0>
2009-10-24 5:15 ` Nishanth Menon [this message]
2009-10-24 5:15 ` [PATCH 1/2 v3] OMAP3: PM: SR: prepare: remove old SR code Nishanth Menon
2009-10-24 5:15 ` [PATCH 2/2 v3] OMAP3: PM: SR: SmartReflex Refactor Rev4.0 Nishanth Menon
2009-10-25 22:12 ` Cousson, Benoit
2009-10-25 22:59 ` Nishanth Menon
2009-10-26 13:05 ` Cousson, Benoit
2009-10-26 13:19 ` Menon, Nishanth
2009-10-26 17:06 ` Cousson, Benoit
[not found] ` <E0D41E29EB0DAC4E9F3FF173962E9E940253EFE01B@dbde02.ent.ti.com>
2009-10-26 10:18 ` Menon, Nishanth
2009-10-26 15:09 ` G, Manjunath Kondaiah
2009-10-27 23:36 ` Paul Walmsley
2009-10-28 5:17 ` Menon, Nishanth
[not found] ` <74583B8642AB8841B30447520659FCA9DDDFCC3A@dnce01.ent.ti.com>
2009-10-27 11:46 ` Imberton Guilhem-gimb01
2009-10-27 15:13 ` Kalle Jokiniemi
2009-10-28 5:05 ` Menon, Nishanth
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=1256361352-9968-1-git-send-email-nm@ti.com \
--to=nm@ti.com \
--cc="linux-omap <linux-omap"@vger.kernel.org \
--cc=ext-kalle.jokiniemi@nokia.com \
--cc=ext-roger.quadros@nokia.com \
--cc=guilhem.imberton@motorola.com \
--cc=jouni.hogander@nokia.com \
--cc=khilman@deeprootsystems.com \
--cc=mikechan@google.com \
--cc=paul@pwsan.com \
--cc=rnayak@ti.com \
--cc=teerth@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