Thread (13 messages) 13 messages, 5 authors, 2014-10-21

[PATCH v4] ARM: perf: save/restore pmu registers in pm notifier

flat view

From: Neil Zhang <hidden>
Date: 2014-10-20 08:47:06
Also in: linux-devicetree, lkml

-----Original Message-----
From: Will Deacon [mailto:will.deacon at arm.com]
Sent: 2014?7?4? 1:57
To: Neil Zhang
Cc: Sudeep Holla; 'linux at arm.linux.org.uk'; 'linux-arm-
kernel at lists.infradead.org'; 'linux-kernel at vger.kernel.org';
'devicetree at vger.kernel.org'
Subject: Re: [PATCH v4] ARM: perf: save/restore pmu registers in pm
notifier

On Mon, Jun 30, 2014 at 11:39:15AM +0100, Neil Zhang wrote:
quoted
quoted
quoted
quoted
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.
quoted
We can change the manner if there is generic power domain
support for
pm notifier later.
quoted
Thanks.
No, please don't add any DT bindings for power domains specific
to
quoted
quoted
quoted
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.
quoted
quoted
quoted
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.
quoted
quoted
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).
Long time no follow up for this loop.
Sorry that I will pick it again.

Will,
I prefer to check always-on field under PMU node to check whether we need
Save/restore them.

Here is a sample for arch timer which also add under itself.
What do you think?

commit 82a5619410d4c4df65c04272db198eca5a867c18
Author: Lorenzo Pieralisi [off-list ref]
Date:   Tue Apr 8 10:04:32 2014 +0100

    clocksource: arch_arm_timer: Fix age-old arch timer C3STOP detection issue

Will
Best Regards,
Neil Zhang
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help