lkml.org 
[lkml]   [2020]   [May]   [22]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH v4 12/13] mips: csrc-r4k: Mark R4K timer as unstable if CPU freq changes
On Thu, May 21, 2020 at 05:07:23PM +0300, Serge Semin wrote:
> Commit 07d69579e7fe ("MIPS: Don't register r4k sched clock when CPUFREQ
> enabled") disabled the r4k-clock usage for scheduler ticks counting due
> to the scheduler being non-tolerant for unstable clocks sources. For the
> same reason the clock should be used in the system clocksource framework
> with care. As soon as CPU frequency changes the clocksource framework
> should be notified about this by marking the R4K timer being unstable
> (which it really is, since the ticks rate has been changed synchronously
> with the CPU frequency).
>
> Signed-off-by: Serge Semin <Sergey.Semin@baikalelectronics.ru>
> Cc: Alexey Malahov <Alexey.Malahov@baikalelectronics.ru>
> Cc: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
> Cc: Paul Burton <paulburton@kernel.org>
> Cc: Ralf Baechle <ralf@linux-mips.org>
> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Cc: Arnd Bergmann <arnd@arndb.de>
> Cc: Rob Herring <robh+dt@kernel.org>
> Cc: devicetree@vger.kernel.org
> ---
> arch/mips/Kconfig | 1 +
> arch/mips/kernel/csrc-r4k.c | 40 +++++++++++++++++++++++++++++++++++++
> 2 files changed, 41 insertions(+)

applied to mips-next.

Thomas.

--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]

\
 
 \ /
  Last update: 2020-05-22 09:32    [W:0.116 / U:10.516 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site