All of lore.kernel.org
 help / color / mirror / Atom feed
From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4] ARM: perf: save/restore pmu registers in pm notifier
Date: Tue, 13 May 2014 19:45:03 +0100	[thread overview]
Message-ID: <20140513184503.GF16388@arm.com> (raw)
In-Reply-To: <9034CBD80F070943B59700D7F8149ED9A0875730@SC-VEXCH4.marvell.com>

On Mon, May 12, 2014 at 11:22:09AM +0100, Neil Zhang wrote:
> > > The device tree bindings for power domains is under discussion [1]
> > 
> > Thanks for the information.
> > But it currently for device only, core related stuff are not supported.
> > And is it really good to register power provider for core and let vfp / pmu etc
> > to get it?
> > 
> 
> What's your suggestion about it?
> Is it OK that I add it under the PMU node?

I don't really mind. I just want to avoid re-inventing the wheel in a
PMU-specific way and having to maintain that code forever because it ended
up in our DT description.

Will

WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will.deacon-5wv7dgnIgG8@public.gmane.org>
To: Neil Zhang <zhangwm-eYqpPyKDWXRBDgjK7y7TUQ@public.gmane.org>
Cc: Sudeep Holla <Sudeep.Holla-5wv7dgnIgG8@public.gmane.org>,
	"'linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org'"
	<linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org>,
	"'linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org'"
	<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
	"'linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org'"
	<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	"'devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org'"
	<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH v4] ARM: perf: save/restore pmu registers in pm notifier
Date: Tue, 13 May 2014 19:45:03 +0100	[thread overview]
Message-ID: <20140513184503.GF16388@arm.com> (raw)
In-Reply-To: <9034CBD80F070943B59700D7F8149ED9A0875730-r8ILAu4/owuq90oVIqnETxL4W9x8LtSr@public.gmane.org>

On Mon, May 12, 2014 at 11:22:09AM +0100, Neil Zhang wrote:
> > > The device tree bindings for power domains is under discussion [1]
> > 
> > Thanks for the information.
> > But it currently for device only, core related stuff are not supported.
> > And is it really good to register power provider for core and let vfp / pmu etc
> > to get it?
> > 
> 
> What's your suggestion about it?
> Is it OK that I add it under the PMU node?

I don't really mind. I just want to avoid re-inventing the wheel in a
PMU-specific way and having to maintain that code forever because it ended
up in our DT description.

Will
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will.deacon@arm.com>
To: Neil Zhang <zhangwm@marvell.com>
Cc: Sudeep Holla <Sudeep.Holla@arm.com>,
	"'linux@arm.linux.org.uk'" <linux@arm.linux.org.uk>,
	"'linux-arm-kernel@lists.infradead.org'" 
	<linux-arm-kernel@lists.infradead.org>,
	"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>,
	"'devicetree@vger.kernel.org'" <devicetree@vger.kernel.org>
Subject: Re: [PATCH v4] ARM: perf: save/restore pmu registers in pm notifier
Date: Tue, 13 May 2014 19:45:03 +0100	[thread overview]
Message-ID: <20140513184503.GF16388@arm.com> (raw)
In-Reply-To: <9034CBD80F070943B59700D7F8149ED9A0875730@SC-VEXCH4.marvell.com>

On Mon, May 12, 2014 at 11:22:09AM +0100, Neil Zhang wrote:
> > > The device tree bindings for power domains is under discussion [1]
> > 
> > Thanks for the information.
> > But it currently for device only, core related stuff are not supported.
> > And is it really good to register power provider for core and let vfp / pmu etc
> > to get it?
> > 
> 
> What's your suggestion about it?
> Is it OK that I add it under the PMU node?

I don't really mind. I just want to avoid re-inventing the wheel in a
PMU-specific way and having to maintain that code forever because it ended
up in our DT description.

Will

  reply	other threads:[~2014-05-13 18:45 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-22  2:26 [PATCH v4] ARM: perf: save/restore pmu registers in pm notifier Neil Zhang
2014-04-22  2:26 ` Neil Zhang
2014-04-22 10:36 ` Will Deacon
2014-04-22 10:36   ` Will Deacon
2014-04-22 10:36   ` Will Deacon
2014-04-23 10:31   ` Neil Zhang
2014-04-23 10:31     ` Neil Zhang
2014-04-23 10:31     ` Neil Zhang
2014-04-23 17:08     ` Will Deacon
2014-04-23 17:08       ` Will Deacon
2014-04-30  2:21       ` Neil Zhang
2014-04-30  2:21         ` Neil Zhang
2014-04-30  2:21         ` Neil Zhang
2014-04-30 13:30         ` Sudeep Holla
2014-04-30 13:30           ` Sudeep Holla
2014-04-30 13:30           ` Sudeep Holla
2014-05-05  6:28           ` Neil Zhang
2014-05-05  6:28             ` Neil Zhang
2014-05-05  6:28             ` Neil Zhang
     [not found]           ` <6106CAF835F351419ADA79E4836E6EC71B6A53C826@SC-VEXCH4.marvell.com>
2014-05-12 10:22             ` Neil Zhang
2014-05-12 10:22               ` Neil Zhang
2014-05-12 10:22               ` Neil Zhang
2014-05-13 18:45               ` Will Deacon [this message]
2014-05-13 18:45                 ` Will Deacon
2014-05-13 18:45                 ` Will Deacon
2014-05-14  2:28                 ` Neil Zhang
2014-05-14  2:28                   ` Neil Zhang
2014-05-14  2:28                   ` Neil Zhang
2014-05-14  9:31                   ` Sudeep Holla
2014-05-14  9:31                     ` Sudeep Holla
2014-05-14  9:31                     ` Sudeep Holla
2014-05-21 11:46                     ` Neil Zhang
2014-05-21 11:46                       ` Neil Zhang
2014-05-21 11:46                       ` Neil Zhang
2014-06-30 10:39                       ` Neil Zhang
2014-06-30 10:39                         ` Neil Zhang
2014-06-30 10:39                         ` Neil Zhang
2014-07-03 17:57                         ` Will Deacon
2014-07-03 17:57                           ` Will Deacon
2014-07-03 17:57                           ` Will Deacon
2014-10-20  8:46                           ` Neil Zhang
2014-10-20  8:46                             ` Neil Zhang
2014-10-20  8:46                             ` Neil Zhang
2014-10-20  9:16                             ` Sudeep Holla
2014-10-20  9:16                               ` Sudeep Holla
2014-10-20  9:16                               ` Sudeep Holla
2014-10-20  9:20                               ` Will Deacon
2014-10-20  9:20                                 ` Will Deacon
2014-10-20  9:26                                 ` Neil Zhang
2014-10-20  9:26                                   ` Neil Zhang
2014-10-20  9:26                                   ` Neil Zhang
2014-10-20  9:41                                 ` Geert Uytterhoeven
2014-10-20  9:41                                   ` Geert Uytterhoeven
2014-10-20  9:41                                   ` Geert Uytterhoeven
2014-10-21 12:52                                 ` Mathieu Poirier
2014-10-21 12:52                                   ` Mathieu Poirier

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=20140513184503.GF16388@arm.com \
    --to=will.deacon@arm.com \
    --cc=linux-arm-kernel@lists.infradead.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 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.