public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@deeprootsystems.com>
To: Thara Gopinath <thara@ti.com>
Cc: linux-omap@vger.kernel.org, paul@pwsan.com, nm@ti.com,
	vishwanath.bs@ti.com, sawant@ti.com, b-cousson@ti.com
Subject: Re: [PATCH 0/3] OMAP3: PM: OMAP3630 support for smartreflex driver
Date: Mon, 08 Mar 2010 09:36:26 -0800	[thread overview]
Message-ID: <87eijuvhph.fsf@deeprootsystems.com> (raw)
In-Reply-To: <1268068851-30022-1-git-send-email-thara@ti.com> (Thara Gopinath's message of "Mon\,  8 Mar 2010 22\:50\:48 +0530")

Thara Gopinath <thara@ti.com> writes:

> This patch series adds support for the updated 45nm smrtrelfex IP
> supported in OMAP3630 and OMAP4 in the smartreflex driver and
> adds support to enable smartreflex autocompensation for OMAP3630
> using test nvalues.
>
> This patch series is based on the following patch series/patches
> for proper functionality.
> 	http://marc.info/?l=linux-omap&m=126700378625593&w=2
> 	http://patchwork.kernel.org/patch/77739/
>
> This patch series has been tested on OMAP3630 SDP board with
> CONFIG_OMAP_SMARTREFLEX_TESTING option enabled in the menuconfig.
>
> This patch series has been based on Kevin's PM tree
> origin/pm-wip-opp branch 

It appears to also depend on the previous SR rework series.  It
doesn't apply directly to pm-wip-opp.

> and on adea81232e8fc82334bca3707efa23dc854f29fc commit id.

This commit is a rather old version of pm-wip-opp, please refresh
against current.

Kevin




> Thara Gopinath (3):
>   OMAP3: PM: Bug fix in Smartreflex driver.
>   OMAP3: PM: Smartreflex IP update changes for OMAP3630
>   OMAP3: PM: Adding OMAP3630 support in smartreflex driver
>
>  arch/arm/mach-omap2/omap_hwmod_34xx.h     |   49 ++++-
>  arch/arm/mach-omap2/smartreflex.c         |  354 +++++++++++++++++++++++-----
>  arch/arm/mach-omap2/smartreflex.h         |   51 ++++-
>  arch/arm/mach-omap2/voltage.c             |  167 +++++++++++---
>  arch/arm/mach-omap2/voltage.h             |   32 ++-
>  arch/arm/plat-omap/include/plat/control.h |    8 +
>  6 files changed, 542 insertions(+), 119 deletions(-)

  parent reply	other threads:[~2010-03-08 17:36 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-08 17:20 [PATCH 0/3] OMAP3: PM: OMAP3630 support for smartreflex driver Thara Gopinath
2010-03-08 17:20 ` [PATCH 1/3] OMAP3: PM: Bug fix in Smartreflex driver Thara Gopinath
2010-03-08 17:20   ` [PATCH 2/3] OMAP3: PM: Smartreflex IP update changes for OMAP3630 Thara Gopinath
2010-03-08 17:20     ` [PATCH 3/3] OMAP3: PM: Adding OMAP3630 support in smartreflex driver Thara Gopinath
2010-03-08 18:18       ` Felipe Balbi
2010-03-09  8:55         ` Gopinath, Thara
2010-03-08 17:46     ` [PATCH 2/3] OMAP3: PM: Smartreflex IP update changes for OMAP3630 Kevin Hilman
2010-03-22  7:05       ` Gopinath, Thara
2010-03-08 18:12     ` Felipe Balbi
2010-03-08 17:38   ` [PATCH 1/3] OMAP3: PM: Bug fix in Smartreflex driver Kevin Hilman
2010-03-08 18:05   ` Felipe Balbi
2010-03-08 17:36 ` Kevin Hilman [this message]
2010-03-09  8:59   ` [PATCH 0/3] OMAP3: PM: OMAP3630 support for smartreflex driver Gopinath, Thara
2010-03-09 19:04     ` Kevin Hilman

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=87eijuvhph.fsf@deeprootsystems.com \
    --to=khilman@deeprootsystems.com \
    --cc=b-cousson@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=nm@ti.com \
    --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