From: Nishanth Menon <nm@ti.com>
To: linux-omap <linux-omap@vger.kernel.org>
Cc: Kevin Hilman <khilman@ti.com>, Nishanth Menon <nm@ti.com>
Subject: [pm_wip/voltdm_nm][PATCH 0/2] OMAP3+: PM: Support multiple PMICs
Date: Tue, 31 May 2011 02:33:50 -0500 [thread overview]
Message-ID: <1306827232-27728-1-git-send-email-nm@ti.com> (raw)
Hi,
This series is a precursor to OMAP4460 support which uses 2 PMICs hence
requiring a slight reorganization of our data. This subject has been brought
up previously in the list as well, this work hopefully will get wider set of
platforms to mainline with power management support.
The following patches are on top of:
git://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-omap-pm.git
branch: pm-wip/voltdm_nm
NOTE: This probably has a minor conflict with the following applied.
http://marc.info/?l=linux-omap&m=130672316613644&w=2
Nishanth Menon (2):
OMAP3+: PM: VP: use uV for max and min voltage limits
OMAP3+: PM: introduce a central pmic control
arch/arm/mach-omap2/Makefile | 2 +-
arch/arm/mach-omap2/omap_pmic.c | 74 +++++++++++++++++++++++++++
arch/arm/mach-omap2/omap_twl.c | 104 +++++++++++++++++----------------------
arch/arm/mach-omap2/pm.c | 5 +-
arch/arm/mach-omap2/pm.h | 35 +++++++++++--
arch/arm/mach-omap2/voltage.h | 27 +++++++++-
arch/arm/mach-omap2/vp.c | 4 +-
7 files changed, 178 insertions(+), 73 deletions(-)
create mode 100644 arch/arm/mach-omap2/omap_pmic.c
Regards,
Nishanth Menon
next reply other threads:[~2011-05-31 7:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-31 7:33 Nishanth Menon [this message]
2011-05-31 7:33 ` [pm_wip/voltdm_nm][PATCH 1/2] OMAP3+: PM: VP: use uV for max and min voltage limits Nishanth Menon
2011-06-03 16:51 ` Kevin Hilman
2011-05-31 7:33 ` [pm_wip/voltdm_nm][PATCH 2/2] OMAP3+: PM: introduce a central pmic control Nishanth Menon
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=1306827232-27728-1-git-send-email-nm@ti.com \
--to=nm@ti.com \
--cc=khilman@ti.com \
--cc=linux-omap@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).