From: Nishanth Menon <nm@ti.com>
To: linux-omap <linux-omap@vger.kernel.org>
Cc: kevin <khilman@ti.com>, Nishanth Menon <nm@ti.com>
Subject: [pm-wip/voltdm_nm][PATCH 00/10] OMAP2+: voltage: fixes
Date: Mon, 6 Jun 2011 21:16:03 -0500 [thread overview]
Message-ID: <1307412972-25854-1-git-send-email-nm@ti.com> (raw)
Bunch of fixes for VC, VP incorporating previous comments
merges two series of PMIC and voltage cleanups I send previously.
Applies on:
git://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-omap-pm.git
voltdm_nm 3c217ab OMAP3+: PM: VC: handle mutant channel config for OMAP4 MPU channel
Original series:
http://marc.info/?l=linux-omap&m=130671118605896&w=2
http://marc.info/?l=linux-omap&m=130682723914928&w=2
Nishanth Menon (10):
OMAP3+: VC: fix mutant channel handling
OMAP4: PM: VC: allow channels use of default channel i2c_slaveaddr
OMAP4: PM: VC: allow channels to use cmdra reg
OMAP4: PM: VC: allow channels use of default channel volt_reg_addr
OMAP4: PM: VC: allow channels use of default channel cmd_reg_addr
OMAP3+: PM: VC: support configuring PMIC over I2C_SR
OMAP3+: PM: VP: use uV for max and min voltage limits
OMAP3+: PM: introduce a central pmic control
OMAP2+: PM: secure OPP access using rcu locks
OMAP2+: PM: init_voltages: handle non compliant bootloaders
arch/arm/mach-omap2/Makefile | 2 +-
arch/arm/mach-omap2/omap_pmic.c | 74 +++++++++++++++++++++
arch/arm/mach-omap2/omap_twl.c | 103 ++++++++++++++----------------
arch/arm/mach-omap2/pm.c | 61 ++++++++++++++----
arch/arm/mach-omap2/pm.h | 35 +++++++++--
arch/arm/mach-omap2/vc.c | 134 ++++++++++++++++++++++++++++++++-------
arch/arm/mach-omap2/vc.h | 8 ++-
arch/arm/mach-omap2/voltage.h | 37 +++++++++--
arch/arm/mach-omap2/vp.c | 4 +-
9 files changed, 351 insertions(+), 107 deletions(-)
create mode 100644 arch/arm/mach-omap2/omap_pmic.c
Regards,
Nishanth Menon
next reply other threads:[~2011-06-07 2:16 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-07 2:16 Nishanth Menon [this message]
2011-06-07 2:16 ` [pm-wip/voltdm_nm][PATCH 01/10] OMAP3+: VC: fix mutant channel handling Nishanth Menon
2011-06-09 17:21 ` Kevin Hilman
2011-06-07 2:16 ` [pm-wip/voltdm_nm][PATCH 02/10] OMAP4: PM: VC: allow channels use of default channel i2c_slaveaddr Nishanth Menon
2011-06-09 18:07 ` Kevin Hilman
2011-06-09 18:17 ` Kevin Hilman
2011-06-07 2:16 ` [pm-wip/voltdm_nm][PATCH 03/10] OMAP4: PM: VC: allow channels to use cmdra reg Nishanth Menon
2011-06-09 17:48 ` Kevin Hilman
2011-06-07 2:16 ` [pm-wip/voltdm_nm][PATCH 04/10] OMAP4: PM: VC: allow channels use of default channel volt_reg_addr Nishanth Menon
2011-06-09 18:32 ` Kevin Hilman
2011-06-07 2:16 ` [pm-wip/voltdm_nm][PATCH 05/10] OMAP4: PM: VC: allow channels use of default channel cmd_reg_addr Nishanth Menon
2011-06-07 2:16 ` [pm-wip/voltdm_nm][PATCH 06/10] OMAP3+: PM: VC: support configuring PMIC over I2C_SR Nishanth Menon
2011-06-07 2:16 ` [pm-wip/voltdm_nm][PATCH 07/10] OMAP3+: PM: VP: use uV for max and min voltage limits Nishanth Menon
2011-06-16 20:45 ` Kevin Hilman
2011-06-17 0:28 ` Menon, Nishanth
2011-06-17 15:48 ` Kevin Hilman
2011-06-07 2:16 ` [pm-wip/voltdm_nm][PATCH 08/10] OMAP3+: PM: introduce a central pmic control Nishanth Menon
2011-06-07 2:16 ` [pm-wip/voltdm_nm][PATCH 09/10] OMAP2+: PM: secure OPP access using rcu locks Nishanth Menon
2011-06-16 20:47 ` Kevin Hilman
2011-06-17 0:39 ` 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=1307412972-25854-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