public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@deeprootsystems.com>
To: Tony Lindgren <tony@atomide.com>
Cc: Thara Gopinath <thara@ti.com>,
	linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	paul@pwsan.com, b-cousson@ti.com, vishwanath.bs@ti.com,
	sawant@ti.com, nm@ti.com
Subject: Re: [PATCH v6 00/10] OMAP: Adding Smartreflex and Voltage driver support
Date: Tue, 21 Dec 2010 08:17:57 -0800	[thread overview]
Message-ID: <87lj3jyua2.fsf@deeprootsystems.com> (raw)
In-Reply-To: <20101221022329.GC5829@atomide.com> (Tony Lindgren's message of "Mon, 20 Dec 2010 18:23:30 -0800")

Tony Lindgren <tony@atomide.com> writes:

> * Kevin Hilman <khilman@deeprootsystems.com> [101220 17:05]:
>> 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.
>> 
>> Thanks Thara, these are looking good for 2.6.38.
>> 
>> Tony, unless there are major objections, I'll be queuing these two SR
>> series for 2.6.38.  They have dependencies on Paul's integration branch
>
> Well looking at patch 3/6 I think it should live under drivers somewhere
> and mostly be compiled as a module. Probably the only change needed
> for that is to not call cpu_is_omapxxxx but instead use some flags
> passed in the platform_data. Otherwise the whole series looks OK to me.

Moving this to be a regulator driver is part of the medium-term plan,
and is already under development.  For this phase, we just split up the
current driver into device and driver code and left under mach-omap2.
We are investigating (and making) changes to the regulator core so that
SmartReflex can be converted into a real regulator driver, but that is
still under development.

So, in the mean time, I'd like to merge this version so that other
development that depends on this (the regulator work mentioned above,
the DVFS work, etc.) can have a stable starting point.

Kevin

  parent reply	other threads:[~2010-12-21 16:18 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-20 16:59 [PATCH v6 00/10] OMAP: Adding Smartreflex and Voltage driver support Thara Gopinath
2010-12-20 16:59 ` [PATCH v6 01/10] OMAP3: PM: Adding voltage " Thara Gopinath
2010-12-22 22:29   ` Kevin Hilman
2010-12-28 16:17   ` Anand Sawant
2010-12-20 16:59 ` [PATCH v6 02/10] OMAP: Introduce voltage domain information in the hwmod structures Thara Gopinath
2010-12-20 16:59 ` [PATCH v6 03/10] OMAP3: PM: Adding smartreflex driver support Thara Gopinath
2010-12-20 16:59 ` [PATCH v6 04/10] OMAP3: PM: Adding smartreflex device file Thara Gopinath
2010-12-20 16:59 ` [PATCH v6 05/10] OMAP3: PM: Adding smartreflex hwmod data Thara Gopinath
2010-12-20 16:59 ` [PATCH v6 06/10] OMAP3: PM: Adding smartreflex class3 driver Thara Gopinath
2010-12-20 16:59 ` [PATCH v6 07/10] OMAP3: PM: Adding T2 enabling of smartreflex support Thara Gopinath
2010-12-22 20:30   ` Kevin Hilman
2010-12-31  8:01     ` Gopinath, Thara
2011-01-02 14:28       ` Woodruff, Richard
2010-12-20 16:59 ` [PATCH v6 08/10] OMAP3: PM: Register TWL4030 pmic info with the voltage driver Thara Gopinath
2010-12-20 16:59 ` [PATCH v6 09/10] OMAP3: PM: Adding debug support to Voltage and Smartreflex drivers Thara Gopinath
2010-12-28 17:07   ` Anand Sawant
2010-12-20 16:59 ` [PATCH v6 10/10] OMAP3: PM: Program correct init voltages for VDD1 and VDD2 Thara Gopinath
2010-12-21  1:05 ` [PATCH v6 00/10] OMAP: Adding Smartreflex and Voltage driver support Kevin Hilman
2010-12-21  2:23   ` Tony Lindgren
2010-12-21  3:18     ` Tony Lindgren
2010-12-21 16:17     ` Kevin Hilman [this message]
2010-12-21 18:55       ` Tony Lindgren

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=87lj3jyua2.fsf@deeprootsystems.com \
    --to=khilman@deeprootsystems.com \
    --cc=b-cousson@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=paul@pwsan.com \
    --cc=sawant@ti.com \
    --cc=thara@ti.com \
    --cc=tony@atomide.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