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, b-cousson@ti.com,
	vishwanath.bs@ti.com, sawant@ti.com, nm@ti.com
Subject: Re: [PATCHv5 00/10] OMAP: Adding Smartreflex and Voltage driver support
Date: Thu, 16 Dec 2010 17:30:39 -0800	[thread overview]
Message-ID: <8739px9oe8.fsf@deeprootsystems.com> (raw)
In-Reply-To: <1292004181-4804-1-git-send-email-thara@ti.com> (Thara Gopinath's message of "Fri, 10 Dec 2010 23:32:51 +0530")

Hi Thara,

Thara Gopinath <thara@ti.com> writes:

> This patch series introduces smartreflex and voltage driver support
> for OMAP3430 and OMAP3630. SmartReflex modules do adaptive voltage
> control for real-time voltage adjustments.


[...]

> This patch series has been tested on OMAP3430 SDP with omap2plus_defconfig
> with the following menuconfig options enabled.

Any testing on 3630?

> System type -> TI OMAP Implementations -> Smartreflex Support
> System type -> TI OMAP Implementations ->
>                 Class 3 mode of Smartreflex Implementation
>
> Major Changes in v5
>
> 	- Rebased to k.org 2.6.37-rc3
> 	- Rebased to Nishant Menon's latest opp patches
> 	- Voltage pmic info structure extended to include a
> 		vast set of PMIC dependent parameters.
> 	- Smartreflex software n-target values support
> 		removed from the kernel. Instead n-target
> 		values are exposed as debugfs entries which can
> 		be written into by the user if needed.
> 	- Introduced a new file arch/arm/mach-omap2/omap_twl.c
> 		for specifying OMAP and TWL related info for
> 		the voltage layer.
> 	- Remove default enabling of smartreflex autocompensation
> 		during boot on OMAP3430 ES3.1 chips. Instead
> 		an API is provided that can be called from
> 		board files in case autocompensation needs
> 		to be enabled during boot up itself.
> 	- Other review comments on v4
> 	
>

This series is looking good.  I have a couple minor comments on specific
patches.

Also, it needs (hopefully only) one more rebase/repost.

First, a few things have changed at the PRCM API level that need to be
updated.  I have a untested patch (below) that should fix this for you,
that you'll need to split and apply to the OMAP3 and OMAP4 voltage
driver patches.

To test with those changes, you can rebase onto my pm-core branch, which
contains not only the PRCM API changes, but also Nishanth's latest OPP
branch, and several other clock, hwmod, PM core changes queued for
2.6.38

Second, please also Cc the linux-arm-kernel mailing list, so if/when we
merge this into linux-omap, it doesn't need a last minute repost.

Thanks,

Kevin

  parent reply	other threads:[~2010-12-17  1:30 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-10 18:02 [PATCHv5 00/10] OMAP: Adding Smartreflex and Voltage driver support Thara Gopinath
2010-12-10 18:02 ` [PATCHv5 01/10] OMAP3: PM: Adding voltage " Thara Gopinath
2010-12-10 18:02 ` [PATCHv5 02/10] OMAP: Introduce voltage domain information in the hwmod structures Thara Gopinath
2010-12-10 18:02 ` [PATCHv5 03/10] OMAP3: PM: Adding smartreflex driver support Thara Gopinath
2010-12-10 18:02 ` [PATCHv5 04/10] OMAP3: PM: Adding smartreflex device file Thara Gopinath
2010-12-10 18:02 ` [PATCHv5 05/10] OMAP3: PM: Adding smartreflex hwmod data Thara Gopinath
2010-12-10 18:02 ` [PATCHv5 06/10] OMAP3: PM: Adding smartreflex class3 driver Thara Gopinath
2010-12-10 18:02 ` [PATCHv5 07/10] OMAP3: PM: Adding T2 enabling of smartreflex support Thara Gopinath
2010-12-10 18:02 ` [PATCHv5 08/10] OMAP3: PM: Register TWL4030 pmic info with the voltage driver Thara Gopinath
2010-12-10 18:03 ` [PATCHv5 09/10] OMAP3: PM: Adding debug support to Voltage and Smartreflex drivers Thara Gopinath
2010-12-17  0:58   ` Kevin Hilman
2010-12-10 18:03 ` [PATCHv5 10/10] OMAP3: PM: Program correct init voltages for VDD1 and VDD2 Thara Gopinath
2010-12-17  1:30 ` Kevin Hilman [this message]
2010-12-17  6:43   ` [PATCHv5 00/10] OMAP: Adding Smartreflex and Voltage driver support Vishwanath Sripathy
2010-12-17 11:36   ` Gopinath, Thara
2010-12-17 14:32     ` 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=8739px9oe8.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