From mboxrd@z Thu Jan 1 00:00:00 1970 From: al.kochet@gmail.com (Alexander Kochetkov) Date: Tue, 29 Nov 2016 17:51:53 +0300 Subject: [PATCH] clocksource/arm_global_timer: reconfigure clockevents after cpufreq change In-Reply-To: References: <1480421716-30782-1-git-send-email-al.kochet@gmail.com> <1480421716-30782-2-git-send-email-al.kochet@gmail.com> <763a77c2-3d19-8d20-88df-27f0b8b80b8b@arm.com> Message-ID: To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org > 29 ????. 2016 ?., ? 17:32, Thomas Gleixner ???????(?): > > 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.