public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
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 17:51:53 +0300	[thread overview]
Message-ID: <BC3314B3-6504-4324-8707-C04534893DAC@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1611291529520.4358@nanos>


> 29 ????. 2016 ?., ? 17:32, Thomas Gleixner <tglx@linutronix.de> ???????(?):
> 
> Can we just disable that global timer on affected SoCs and use something
> else instead?

I?ve sent patch series for fixing that on rockchip SoC.
http://lists.infradead.org/pipermail/linux-rockchip/2016-November/013217.html

But the series contain fix only for rk3188, because I don?t have another rockchip
SoC. rk3288 and other could be easy fixed with dts files.

There are a lot of other platforms what probably use shed_clock and
clocksource form global-timer.
 
alexander at ubuntu:dts$ grep arm,cortex-a9-global-timer *
am4372.dtsi:		compatible = "arm,cortex-a9-global-timer";
artpec6.dtsi:		compatible = "arm,cortex-a9-global-timer";
bcm5301x.dtsi:			compatible = "arm,cortex-a9-global-timer";
bcm63138.dtsi:			compatible = "arm,cortex-a9-global-timer";
bcm-cygnus.dtsi:			compatible = "arm,cortex-a9-global-timer";
bcm-nsp.dtsi:			compatible = "arm,cortex-a9-global-timer";
hip01.dtsi:			compatible = "arm,cortex-a9-global-timer";
rk3xxx.dtsi:		compatible = "arm,cortex-a9-global-timer";
stih407-family.dtsi:		compatible = "arm,cortex-a9-global-timer";
stih41x.dtsi:		compatible = "arm,cortex-a9-global-timer";
uniphier-common32.dtsi:			compatible = "arm,cortex-a9-global-timer";
uniphier-ph1-sld3.dtsi:			compatible = "arm,cortex-a9-global-timer";
vexpress-v2p-ca5s.dts:		             "arm,cortex-a9-global-timer";
vf500.dtsi:				compatible = "arm,cortex-a9-global-timer";
zx296702.dtsi:			compatible = "arm,cortex-a9-global-timer";
zynq-7000.dtsi:			compatible = "arm,cortex-a9-global-timer?;

Regards,
Alexander.

  parent reply	other threads:[~2016-11-29 14:51 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
2016-11-29 14:51         ` Marc Zyngier
2016-11-29 15:04           ` Alexander Kochetkov
2016-11-29 14:51         ` Alexander Kochetkov [this message]
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=BC3314B3-6504-4324-8707-C04534893DAC@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