From: tglx@linutronix.de (Thomas Gleixner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] clocksource/arm_global_timer: reconfigure clockevents after cpufreq change
Date: Tue, 29 Nov 2016 15:32:28 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.20.1611291529520.4358@nanos> (raw)
In-Reply-To: <763a77c2-3d19-8d20-88df-27f0b8b80b8b@arm.com>
On Tue, 29 Nov 2016, Marc Zyngier wrote:
> On 29/11/16 13:42, Thomas Gleixner wrote:
> > Assumptions w/o real impact are a perfect reason not to apply that
> > patch. This want's a proper proof that the global timer really changes and
> > this hackery is required, which I seriously doubt.
>
> Well, let's not underestimate the "creativity" [1] of A5/A9 when it
> comes to the timer clocks, and it is a very sad fact that both the
> global timer and the local timers are clocked by PERIPHCLK, which is
> ticking at a fixed ratio N (N >= 2) of the main CPU clock (CLK):
>
> http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.ddi0407f/CIHGECHJ.html
>
> I'm not sure how feasible it is to change this ratio (the TRM seems to
> be very silent on the subject).
The CRU documentation of the RK3188 suggests that you can adjust it as it
has a seperate divider, but who knows.
> So short of being able to reconfigure it on the fly, this will probably
> need some surgery similar to what we already do for the TWD (which this
> patch mimics).
>
> Thankfully, we don't see that anymore on moderately recent HW (anything
> since A15) and the advent of the arch timer, which is guaranteed to have
> a fixed frequency.
Can we just disable that global timer on affected SoCs and use something
else instead?
Thanks,
tglx
next prev parent reply other threads:[~2016-11-29 14:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-29 12:15 [PATCH] clocksource/arm_global_timer: reconfigure clockevents after cpufreq change Alexander Kochetkov
2016-11-29 12:15 ` Alexander Kochetkov
2016-11-29 13:42 ` Thomas Gleixner
2016-11-29 14:05 ` Alexander Kochetkov
2016-11-29 14:09 ` Thomas Gleixner
2016-11-29 14:14 ` Marc Zyngier
2016-11-29 14:32 ` Thomas Gleixner [this message]
2016-11-29 14:51 ` Marc Zyngier
2016-11-29 15:04 ` Alexander Kochetkov
2016-11-29 14:51 ` Alexander Kochetkov
2016-11-29 15:07 ` Robin Murphy
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=alpine.DEB.2.20.1611291529520.4358@nanos \
--to=tglx@linutronix.de \
--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