All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@deeprootsystems.com>
To: "Gopinath, Thara" <thara@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	"paul@pwsan.com" <paul@pwsan.com>,
	"Cousson, Benoit" <b-cousson@ti.com>,
	"Sripathy, Vishwanath" <vishwanath.bs@ti.com>,
	"Sawant, Anand" <sawant@ti.com>,
	"Derrick, David" <dderrick@ti.com>
Subject: Re: [PATCHv2 4/8] OMAP3: PM: Adding smartreflex device file.
Date: Tue, 14 Sep 2010 09:03:19 -0700	[thread overview]
Message-ID: <8739tctirc.fsf@deeprootsystems.com> (raw)
In-Reply-To: <5A47E75E594F054BAF48C5E4FC4B92AB0329441CF0@dbde02.ent.ti.com> (Thara Gopinath's message of "Tue, 14 Sep 2010 21:06:57 +0530")

"Gopinath, Thara" <thara@ti.com> writes:

[...]

>>>> +	sr_data->device_enable = omap_device_enable;
>>>> +	sr_data->device_shutdown = omap_device_shutdown;
>>>> +	sr_data->device_idle = omap_device_idle;
>>>
>>>Please drop these and use runtime PM as suggested in previous patch.
>
> At this stage I am not sure whether we should make smartreflex patches
> dependent on runtime pm. I would like to do the conversion once and for all
> once runtime pm is up streamed. 

Using runtime PM instead of the sr_data-> calls will simplify this
patch.  

Also, runtime PM core for OMAP will be merged this merge window.  If you
use my 'pm-core' branch for testing, you will have it included in your
baseline, along with all the other things that are targeted for merge in
2.6.37.

Kevin



  reply	other threads:[~2010-09-14 16:03 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-13 13:47 [PATCHv2 0/8] OMAP3: Adding Smartreflex and Voltage driver support Thara Gopinath
2010-08-13 13:47 ` [PATCHv2 1/8] OMAP: PM: Allowing an early init of pm debugfs driver Thara Gopinath
2010-08-24 22:16   ` Kevin Hilman
2010-08-24 22:21     ` Kevin Hilman
2010-09-14 14:56       ` Gopinath, Thara
2010-08-13 13:47 ` [PATCHv2 2/8] OMAP3: PM: Adding voltage driver support for OMAP3 Thara Gopinath
2010-08-25  0:01   ` Kevin Hilman
2010-09-14 15:32     ` Gopinath, Thara
2010-08-30 23:06   ` Kevin Hilman
2010-08-30 23:21   ` Kevin Hilman
2010-08-13 13:47 ` [PATCHv2 3/8] OMAP3: PM: Adding smartreflex driver support Thara Gopinath
2010-08-25 22:21   ` Kevin Hilman
2010-09-14 15:58     ` Gopinath, Thara
2010-09-14 17:04       ` Kevin Hilman
2010-08-13 13:47 ` [PATCHv2 4/8] OMAP3: PM: Adding smartreflex device file Thara Gopinath
2010-08-25 22:26   ` Kevin Hilman
2010-09-14 15:36     ` Gopinath, Thara
2010-09-14 16:03       ` Kevin Hilman [this message]
2010-09-15  6:12         ` Gopinath, Thara
2010-08-13 13:47 ` [PATCHv2 5/8] OMAP3: PM: Adding smartreflex hwmod data Thara Gopinath
2010-08-25 22:29   ` Kevin Hilman
2010-08-13 13:47 ` [PATCHv2 6/8] OMAP3: PM: Adding smartreflex class3 driver Thara Gopinath
2010-08-25 22:31   ` Kevin Hilman
2010-09-14 15:58     ` Gopinath, Thara
2010-08-13 13:47 ` [PATCHv2 7/8] OMAP3: PM: Adding T2 enabling of smartreflex support Thara Gopinath
2010-08-13 13:47 ` [PATCHv2 8/8] OMAP3: PM: Adding debug support to Voltage and Smartreflex drivers Thara Gopinath
2010-08-24 23:53   ` Kevin Hilman
2010-09-14 14:58     ` Gopinath, Thara
2010-09-14 16:05       ` 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=8739tctirc.fsf@deeprootsystems.com \
    --to=khilman@deeprootsystems.com \
    --cc=b-cousson@ti.com \
    --cc=dderrick@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.