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: Thu, 3 Jul 2014 18:57:06 +0100	[thread overview]
Message-ID: <20140703175706.GI17372@arm.com> (raw)
In-Reply-To: <9034CBD80F070943B59700D7F8149ED90182308172@SC-VEXCH4.marvell.com>

On Mon, Jun 30, 2014 at 11:39:15AM +0100, Neil Zhang wrote:
> > > > I will prepare another patch to add DT description under PMU since
> > > > there is no generic power domain support for pm notifier if no other
> > > concerns.
> > > > We can change the manner if there is generic power domain support
> > > > for
> > > pm notifier later.
> > > > Thanks.
> > >
> > > No, please don't add any DT bindings for power domains specific to PMU
> > > node.
> > > We can't change the DT bindings once added.
> > >
> > > As I pointed out the DT bindings for generic power domains are under
> > > discussion.
> > > See if you can reuse it, if not help in extending it so that it can be used.
> > >
> > 
> > Sorry for reply later.
> > As I said before the under discussed generic power domain is not suitable for
> > CPU peripherals since they are all known belong to CPU or cluster power
> > domain.
> > If we want to follow the way they are discussion, we need to register core
> > and cluster power provider, and need vfp/gic/pmu etc to require them.
> > Is it really suitable?
> > 
> Do you have any comments?
> If no, I would like to put it under PMU node.

Sudeep is a better person to comment than me, but I'd still rather this was
handled more generically as opposed to a PMU-specific hack. I don't see a
problem including GIC and VFP here, but only when we actually need to
save/restore them (i.e. what the hardware guys went crazy with the power
domains).

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: Thu, 3 Jul 2014 18:57:06 +0100	[thread overview]
Message-ID: <20140703175706.GI17372@arm.com> (raw)
In-Reply-To: <9034CBD80F070943B59700D7F8149ED90182308172-r8ILAu4/owuq90oVIqnETxL4W9x8LtSr@public.gmane.org>

On Mon, Jun 30, 2014 at 11:39:15AM +0100, Neil Zhang wrote:
> > > > I will prepare another patch to add DT description under PMU since
> > > > there is no generic power domain support for pm notifier if no other
> > > concerns.
> > > > We can change the manner if there is generic power domain support
> > > > for
> > > pm notifier later.
> > > > Thanks.
> > >
> > > No, please don't add any DT bindings for power domains specific to PMU
> > > node.
> > > We can't change the DT bindings once added.
> > >
> > > As I pointed out the DT bindings for generic power domains are under
> > > discussion.
> > > See if you can reuse it, if not help in extending it so that it can be used.
> > >
> > 
> > Sorry for reply later.
> > As I said before the under discussed generic power domain is not suitable for
> > CPU peripherals since they are all known belong to CPU or cluster power
> > domain.
> > If we want to follow the way they are discussion, we need to register core
> > and cluster power provider, and need vfp/gic/pmu etc to require them.
> > Is it really suitable?
> > 
> Do you have any comments?
> If no, I would like to put it under PMU node.

Sudeep is a better person to comment than me, but I'd still rather this was
handled more generically as opposed to a PMU-specific hack. I don't see a
problem including GIC and VFP here, but only when we actually need to
save/restore them (i.e. what the hardware guys went crazy with the power
domains).

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: Thu, 3 Jul 2014 18:57:06 +0100	[thread overview]
Message-ID: <20140703175706.GI17372@arm.com> (raw)
In-Reply-To: <9034CBD80F070943B59700D7F8149ED90182308172@SC-VEXCH4.marvell.com>

On Mon, Jun 30, 2014 at 11:39:15AM +0100, Neil Zhang wrote:
> > > > I will prepare another patch to add DT description under PMU since
> > > > there is no generic power domain support for pm notifier if no other
> > > concerns.
> > > > We can change the manner if there is generic power domain support
> > > > for
> > > pm notifier later.
> > > > Thanks.
> > >
> > > No, please don't add any DT bindings for power domains specific to PMU
> > > node.
> > > We can't change the DT bindings once added.
> > >
> > > As I pointed out the DT bindings for generic power domains are under
> > > discussion.
> > > See if you can reuse it, if not help in extending it so that it can be used.
> > >
> > 
> > Sorry for reply later.
> > As I said before the under discussed generic power domain is not suitable for
> > CPU peripherals since they are all known belong to CPU or cluster power
> > domain.
> > If we want to follow the way they are discussion, we need to register core
> > and cluster power provider, and need vfp/gic/pmu etc to require them.
> > Is it really suitable?
> > 
> Do you have any comments?
> If no, I would like to put it under PMU node.

Sudeep is a better person to comment than me, but I'd still rather this was
handled more generically as opposed to a PMU-specific hack. I don't see a
problem including GIC and VFP here, but only when we actually need to
save/restore them (i.e. what the hardware guys went crazy with the power
domains).

Will

  reply	other threads:[~2014-07-03 17:57 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
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 [this message]
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=20140703175706.GI17372@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.