linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Will Deacon <will.deacon@arm.com>
To: Kevin Hilman <khilman@deeprootsystems.com>
Cc: Jon Hunter <jon-hunter@ti.com>,
	linux-omap <linux-omap@vger.kernel.org>,
	linux-arm <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] ARM: PMU: fix runtime PM enable
Date: Thu, 25 Oct 2012 17:47:14 +0100	[thread overview]
Message-ID: <20121025164714.GK11267@mudshark.cambridge.arm.com> (raw)
In-Reply-To: <87vcdy33ma.fsf@deeprootsystems.com>

On Thu, Oct 25, 2012 at 05:42:21PM +0100, Kevin Hilman wrote:
> Jon Hunter <jon-hunter@ti.com> writes:
> > On 10/24/2012 12:23 PM, Will Deacon wrote:
> >> What do other drivers do? Grepping around, I see calls to pm_runtime_enable
> >> made in various drivers and, given that you pass the device in there, what's
> >> the problem with us just calling that unconditionally from perf? I know you
> >> said that will work for OMAP, but I'm trying to understand the effect that
> >> has on PM-aware platforms that don't require this for the PMU (since this
> >> seems to be per-device).
> >
> > I had done this initially when testing on OMAP platforms that do and
> > don't require runtime PM for PMU. I don't see any side affect of this,
> > however, may be Kevin could comment on if that is ok. It would be the
> > best approach.
> 
> Unconditonally enabling runtime PM should be fine.  It may add a slight
> bit of overhead calling runtime PM functions that ultimately do nothing
> (because there are no callbacks), but it will be harmless.
> 
> Personally, I think that would be cleaner.  The less pdata we need, the
> better, IMO.

Thanks Kevin, I'm fine with that. Jon: want me to write a patch or do you
have something I can take into the ARM perf tree (if the latter, please
base against perf/updates)?

Cheers,

Will

  reply	other threads:[~2012-10-25 16:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-23 20:31 [PATCH] ARM: PMU: fix runtime PM enable Jon Hunter
2012-10-24  9:31 ` Will Deacon
2012-10-24 14:16   ` Jon Hunter
2012-10-24 14:32     ` Will Deacon
2012-10-24 15:06       ` Jon Hunter
2012-10-24 17:23         ` Will Deacon
2012-10-24 17:41           ` Jon Hunter
2012-10-25 16:42             ` Kevin Hilman
2012-10-25 16:47               ` Will Deacon [this message]
2012-10-25 16:50                 ` Jon Hunter

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=20121025164714.GK11267@mudshark.cambridge.arm.com \
    --to=will.deacon@arm.com \
    --cc=jon-hunter@ti.com \
    --cc=khilman@deeprootsystems.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    /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).