From: khilman@deeprootsystems.com (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] OMAP SmartReflex/voltage core for 2.6.38
Date: Wed, 22 Dec 2010 12:24:53 -0800 [thread overview]
Message-ID: <878vzhsgh6.fsf@deeprootsystems.com> (raw)
In-Reply-To: <87fwtptyaf.fsf@deeprootsystems.com> (Kevin Hilman's message of "Wed, 22 Dec 2010 11:14:48 -0800")
Kevin Hilman <khilman@deeprootsystems.com> writes:
> Tony,
>
> The following pull request is for the SmartReflex/voltage core for
> 2.6.38.
>
> It is based on Paul's latest integration-2.6.38-for-tony branch, so
> should be pulled only after pulling from Paul.
>
Retracting this pull request. It actually breaks boot on 2430SDP.
More details in replies to the last posting of this series.
Kevin
>
>
> The following changes since commit f17f9726c27c3921e00a5750e85070e6dd7e1ff7:
>
> OMAP4: clock data: Add missing fixed divisors (2010-12-22 10:12:46 -0700)
>
> are available in the git repository at:
> ssh://master.kernel.org/pub/scm/linux/kernel/git/khilman/linux-omap-pm.git pm-sr
>
> Benoit Cousson (1):
> OMAP4: hwmod: Add inital data for smartreflex modules.
>
> Thara Gopinath (14):
> OMAP3: PM: Adding voltage driver support.
> OMAP: Introduce voltage domain information in the hwmod structures
> OMAP3: PM: Adding smartreflex driver support.
> OMAP3: PM: Adding smartreflex device file.
> OMAP3: PM: Adding smartreflex hwmod data
> OMAP3: PM: Adding smartreflex class3 driver
> OMAP3: PM: Adding T2 enabling of smartreflex support
> OMAP3: PM: Register TWL4030 pmic info with the voltage driver.
> OMAP3: PM: Adding debug support to Voltage and Smartreflex drivers
> OMAP3: PM: Program correct init voltages for VDD1 and VDD2
> OMAP4: Register voltage PMIC parameters with the voltage layer
> OMAP4: Adding voltage driver support
> OMAP4: PM: Program correct init voltages for scalable VDDs
> OMAP4: Smartreflex framework extensions
>
> arch/arm/mach-omap2/Makefile | 9 +-
> arch/arm/mach-omap2/control.h | 29 +
> arch/arm/mach-omap2/omap_hwmod_3xxx_data.c | 175 +++
> arch/arm/mach-omap2/omap_hwmod_44xx_data.c | 168 +++
> arch/arm/mach-omap2/omap_twl.c | 277 +++++
> arch/arm/mach-omap2/pm.c | 102 ++
> arch/arm/mach-omap2/pm.h | 28 +
> arch/arm/mach-omap2/smartreflex-class3.c | 59 +
> arch/arm/mach-omap2/smartreflex.c | 1029 ++++++++++++++++
> arch/arm/mach-omap2/sr_device.c | 146 +++
> arch/arm/mach-omap2/voltage.c | 1571 +++++++++++++++++++++++++
> arch/arm/plat-omap/Kconfig | 31 +
> arch/arm/plat-omap/include/plat/omap_hwmod.h | 5 +
> arch/arm/plat-omap/include/plat/smartreflex.h | 245 ++++
> arch/arm/plat-omap/include/plat/voltage.h | 146 +++
> drivers/mfd/twl-core.c | 13 +
> include/linux/i2c/twl.h | 11 +
> 17 files changed, 4042 insertions(+), 2 deletions(-)
> create mode 100644 arch/arm/mach-omap2/omap_twl.c
> create mode 100644 arch/arm/mach-omap2/smartreflex-class3.c
> create mode 100644 arch/arm/mach-omap2/smartreflex.c
> create mode 100644 arch/arm/mach-omap2/sr_device.c
> create mode 100644 arch/arm/mach-omap2/voltage.c
> create mode 100644 arch/arm/plat-omap/include/plat/smartreflex.h
> create mode 100644 arch/arm/plat-omap/include/plat/voltage.h
prev parent reply other threads:[~2010-12-22 20:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-22 19:14 [GIT PULL] OMAP SmartReflex/voltage core for 2.6.38 Kevin Hilman
2010-12-22 20:24 ` Kevin Hilman [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=878vzhsgh6.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=linux-arm-kernel@lists.infradead.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