linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jon Hunter <jon-hunter@ti.com>
To: Will Deacon <will.deacon@arm.com>
Cc: Kevin Hilman <khilman@ti.com>,
	linux-omap <linux-omap@vger.kernel.org>,
	Ming Lei <ming.lei@canonical.com>,
	Benoit Cousson <b-cousson@ti.com>, Paul Walmsley <paul@pwsan.com>
Subject: Re: [PATCH 4/6] ARM: OMAP4: PMU: Add runtime PM support
Date: Wed, 6 Jun 2012 20:24:41 -0500	[thread overview]
Message-ID: <4FD002D9.8000404@ti.com> (raw)
In-Reply-To: <20120606173331.GB19478@mudshark.cambridge.arm.com>

Hi Will,

On 06/06/2012 12:33 PM, Will Deacon wrote:
> On Tue, Jun 05, 2012 at 02:19:02PM +0100, Jon Hunter wrote:
>> Hi Will,
> 
> Hi Jon,
> 
>> On 06/04/2012 04:44 PM, Jon Hunter wrote:
>> Anyway, let me know what you think of this approach. An alternative is
>> to put the calls pm_runtime_get/put outside of the reserve/release_pmu,
>> which would be a simpler change, but I was thinking that the above maybe
>> more aligned with your thinking.
> 
> Ok, thanks for this. Whilst your code is definitely more like I'm
> envisaging, you're right about the churn and until I've sorted out the
> reservation code so that it's a callback via the PMU structure, it is
> overly messy.
> 
> So for the time being let's do what you suggested and put the suspend/resume
> calls into armpmu_{reserve,release}_hardware. We can still kill the irq
> enable/disable calls and I can rework this slightly when I change the
> reservation code.

Sounds good. I will send out my V2 series tomorrow that will include the
above change.

Cheers
Jon

  reply	other threads:[~2012-06-07  1:24 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-09 21:35 [PATCH 4/6] ARM: OMAP4: PMU: Add runtime PM support Jon Hunter
2012-05-10  6:21 ` Shilimkar, Santosh
2012-05-15  4:53 ` Ming Lei
2012-05-15 14:39   ` Jon Hunter
     [not found]     ` <CACVXFVNqWM7G8dK2AA90JPvE6e_L0_Zwk-BJTjThY+nZ6ONnQA@mail.gmail.com>
2012-05-16  8:17       ` Ming Lei
2012-05-17  5:28         ` Ming Lei
2012-05-29 21:17 ` Kevin Hilman
2012-05-29 22:07   ` Jon Hunter
2012-05-29 22:27     ` Jon Hunter
2012-05-30 21:50       ` Kevin Hilman
2012-05-31  1:29         ` Will Deacon
2012-05-31 15:05           ` Jon Hunter
2012-05-31 18:49             ` Jon Hunter
2012-05-31 18:11           ` Jon Hunter
2012-05-31 20:42             ` Kevin Hilman
2012-05-31 21:23               ` Jon Hunter
2012-05-31 22:36                 ` Kevin Hilman
2012-05-31 23:02                   ` Jon Hunter
2012-06-01  0:27                     ` Kevin Hilman
2012-06-01 14:42                       ` Jon Hunter
2012-06-02 16:42                         ` Will Deacon
2012-06-04 21:44                           ` Jon Hunter
2012-06-05 13:19                             ` Jon Hunter
2012-06-06 17:33                               ` Will Deacon
2012-06-07  1:24                                 ` Jon Hunter [this message]
2012-05-31 15:04         ` Jon Hunter
2012-05-31 16:22           ` 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=4FD002D9.8000404@ti.com \
    --to=jon-hunter@ti.com \
    --cc=b-cousson@ti.com \
    --cc=khilman@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=ming.lei@canonical.com \
    --cc=paul@pwsan.com \
    --cc=will.deacon@arm.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;
as well as URLs for NNTP newsgroup(s).