From: eric@anholt.net (Eric Anholt)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm: bcm2835: Add the PMU to the devicetree.
Date: Thu, 17 May 2018 18:09:34 +0100 [thread overview]
Message-ID: <877eo2mcoh.fsf@anholt.net> (raw)
In-Reply-To: <alpine.DEB.2.21.1805171233500.7984@macbook-air>
Vince Weaver <vincent.weaver@maine.edu> writes:
> On Thu, 17 May 2018, Stefan Wahren wrote:
>
>>
>> > Eric Anholt <eric@anholt.net> hat am 17. Mai 2018 um 15:17 geschrieben:
>> >
>> >
>> > The a53 and a7 counters seem to match up, so we advertise a7 so that
>> > arm32 can probe.
>
> so how closely did you look at the a53/a7 differences? I see some major
> differences, especially with the CPU_CYCLES event (0xff vs 0x11).
I'm a bit lost in the code, but it seemed like the 0xff was a
placeholder for a bit of special behavior, but that the cpu_cycles ->
ARMV7_PERFCTR_CLOCK_CYCLES mapping got you that same value in the end.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 832 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20180517/24fefc2e/attachment-0001.sig>
next prev parent reply other threads:[~2018-05-17 17:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-17 13:17 [PATCH] arm: bcm2835: Add the PMU to the devicetree Eric Anholt
2018-05-17 14:11 ` Vince Weaver
2018-05-17 14:30 ` Eric Anholt
2018-05-17 16:02 ` Vince Weaver
2018-05-17 16:06 ` Stefan Wahren
2018-05-17 15:59 ` Stefan Wahren
2018-05-17 16:34 ` Vince Weaver
2018-05-17 16:55 ` Stefan Wahren
2018-05-17 18:07 ` Peter Zijlstra
2018-05-17 18:27 ` Vince Weaver
2018-05-17 19:31 ` Vince Weaver
2018-05-17 19:59 ` Florian Fainelli
2018-05-18 8:07 ` Marc Zyngier
2018-05-18 9:37 ` Stefan Wahren
2018-05-18 9:49 ` Marc Zyngier
2018-05-17 17:09 ` Eric Anholt [this message]
2018-05-17 16:44 ` Peter Robinson
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=877eo2mcoh.fsf@anholt.net \
--to=eric@anholt.net \
--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 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).