From: Peter Zijlstra <peterz@infradead.org>
To: Stefan Wahren <stefan.wahren@i2se.com>
Cc: Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Florian Fainelli <f.fainelli@gmail.com>,
linux-rpi-kernel@lists.infradead.org,
bcm-kernel-feedback-list@broadcom.com,
Vince Weaver <vincent.weaver@maine.edu>,
linux-kernel@vger.kernel.org, Eric Anholt <eric@anholt.net>,
linux-arm-kernel@lists.infradead.org,
Mark Rutland <mark.rutland@arm.com>
Subject: Re: [PATCH] arm: bcm2835: Add the PMU to the devicetree.
Date: Thu, 17 May 2018 20:07:59 +0200 [thread overview]
Message-ID: <20180517180758.GK12198@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <307323036.63872.1526576126537@email.1und1.de>
On Thu, May 17, 2018 at 06:55:26PM +0200, Stefan Wahren wrote:
> > Vince Weaver <vincent.weaver@maine.edu> hat am 17. Mai 2018 um 18:34 geschrieben:
> > 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).
> >
> > The proper fix here might be to add a cortex-a53 PMU entry to the armv7
> > code rather than trying to treat it as a cortex-a7.
>
> we like to use the PMU of BCM2837 SoC (4x A53 cores) under arm32 and arm64.
>
> What is the right way (tm) to the define the DT compatibles?
> Does the arm32 PMU driver need patching for proper A53 support?
I'm completely clueless on all of this; Mark might have ideas.
next prev parent reply other threads:[~2018-05-17 18:08 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 [this message]
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
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=20180517180758.GK12198@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=acme@kernel.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=eric@anholt.net \
--cc=f.fainelli@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=stefan.wahren@i2se.com \
--cc=vincent.weaver@maine.edu \
/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