From: Will Deacon <will.deacon@arm.com>
To: Sudeep Holla <Sudeep.Holla@arm.com>
Cc: Neil Zhang <zhangwm@marvell.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>,
mathieu.poirier@linaro.org
Subject: Re: [PATCH v4] ARM: perf: save/restore pmu registers in pm notifier
Date: Mon, 20 Oct 2014 10:20:05 +0100 [thread overview]
Message-ID: <20141020092005.GD4370@arm.com> (raw)
In-Reply-To: <5444D2E0.9070205@arm.com>
On Mon, Oct 20, 2014 at 10:16:16AM +0100, Sudeep Holla wrote:
> On 20/10/14 09:46, Neil Zhang wrote:
> > Will, I prefer to check always-on field under PMU node to check
> > whether we need Save/restore them.
> >
> But how do you handle it for different idle states. e.g. if CPU is in
> retention, PMU's *might be* retained. Also I don't think PMUs will be
> placed in "always-on" power domain like timers. So using "always-on"
> sounds incorrect to me.
Adding Mathieu to CC, since I spoke to him at LPC about this and he was
talking about implementing proper PM domain descriptions for coresight
components.
Will
next prev parent reply other threads:[~2014-10-20 9:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1398133596-29170-1-git-send-email-zhangwm@marvell.com>
[not found] ` <1398133596-29170-1-git-send-email-zhangwm-eYqpPyKDWXRBDgjK7y7TUQ@public.gmane.org>
2014-04-22 10:36 ` [PATCH v4] ARM: perf: save/restore pmu registers in pm notifier Will Deacon
2014-04-23 10:31 ` Neil Zhang
2014-04-23 17:08 ` Will Deacon
[not found] ` <20140423170821.GJ5649-5wv7dgnIgG8@public.gmane.org>
2014-04-30 2:21 ` Neil Zhang
[not found] ` <175CCF5F49938B4D99B2E3EF7F558EBE5507A3C1F1-r8ILAu4/owuq90oVIqnETxL4W9x8LtSr@public.gmane.org>
2014-04-30 13:30 ` Sudeep Holla
2014-05-05 6:28 ` Neil Zhang
[not found] ` <6106CAF835F351419ADA79E4836E6EC71B6A53C826@SC-VEXCH4.marvell.com>
[not found] ` <6106CAF835F351419ADA79E4836E6EC71B6A53C826-r8ILAu4/owuq90oVIqnETxL4W9x8LtSr@public.gmane.org>
2014-05-12 10:22 ` Neil Zhang
[not found] ` <9034CBD80F070943B59700D7F8149ED9A0875730-r8ILAu4/owuq90oVIqnETxL4W9x8LtSr@public.gmane.org>
2014-05-13 18:45 ` Will Deacon
[not found] ` <20140513184503.GF16388-5wv7dgnIgG8@public.gmane.org>
2014-05-14 2:28 ` Neil Zhang
[not found] ` <9034CBD80F070943B59700D7F8149ED9A087573F-r8ILAu4/owuq90oVIqnETxL4W9x8LtSr@public.gmane.org>
2014-05-14 9:31 ` Sudeep Holla
[not found] ` <537337F3.4080300-5wv7dgnIgG8@public.gmane.org>
2014-05-21 11:46 ` Neil Zhang
2014-06-30 10:39 ` Neil Zhang
[not found] ` <9034CBD80F070943B59700D7F8149ED90182308172-r8ILAu4/owuq90oVIqnETxL4W9x8LtSr@public.gmane.org>
2014-07-03 17:57 ` Will Deacon
2014-10-20 8:46 ` Neil Zhang
[not found] ` <9034CBD80F070943B59700D7F8149ED9024EB81CD8-r8ILAu4/owuq90oVIqnETxL4W9x8LtSr@public.gmane.org>
2014-10-20 9:16 ` Sudeep Holla
2014-10-20 9:20 ` Will Deacon [this message]
2014-10-20 9:26 ` Neil Zhang
[not found] ` <20141020092005.GD4370-5wv7dgnIgG8@public.gmane.org>
2014-10-20 9:41 ` Geert Uytterhoeven
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=20141020092005.GD4370@arm.com \
--to=will.deacon@arm.com \
--cc=Sudeep.Holla@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mathieu.poirier@linaro.org \
--cc=zhangwm@marvell.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).