From: al.kochet@gmail.com (Alexander Kochetkov)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] clocksource/arm_global_timer: reconfigure clockevents after cpufreq change
Date: Tue, 29 Nov 2016 15:15:15 +0300 [thread overview]
Message-ID: <1480421716-30782-1-git-send-email-al.kochet@gmail.com> (raw)
Hello,
I found what arm-global-timer doesn't update clockevent's frequency
after cpufreq change. So I've backported two patches from
local-timer (smp_twd) to implement clockevent frequency adjustment.
Alexander Kochetkov (1):
clocksource/arm_global_timer: reconfigure clockevents after cpufreq
change
drivers/clocksource/arm_global_timer.c | 93 +++++++++++++++++++++++++++++++-
1 file changed, 92 insertions(+), 1 deletion(-)
--
1.7.9.5
next reply other threads:[~2016-11-29 12:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-29 12:15 Alexander Kochetkov [this message]
2016-11-29 12:15 ` [PATCH] clocksource/arm_global_timer: reconfigure clockevents after cpufreq change 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
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=1480421716-30782-1-git-send-email-al.kochet@gmail.com \
--to=al.kochet@gmail.com \
--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