linux-toradex.git/drivers/clocksource/nomadik-mtu.c, branch v6.15-rc5

clocksource: Explicitly include correct DT includes

2023-08-28T18:30:57+00:00

The DT of_device.h and of_platform.h date back to the separate
of_platform_bus_type before it was merged into the regular platform bus.
As part of that merge prepping Arm DT support 13 years ago, they
"temporarily" include each other. They also include platform_device.h
and of.h. As a result, there's a pretty much random mix of those include
files used throughout the tree. In order to detangle these headers and
replace the implicit includes with struct declarations, users need to
explicitly include the correct includes.

Link: https://lore.kernel.org/r/20230714174409.4053843-1-robh@kernel.org
Signed-off-by: Rob Herring

clocksource/drivers/nomadik-mtu: Handle 32kHz clock

2020-07-23T14:57:43+00:00

It happens on the U8420-sysclk Ux500 PRCMU firmware
variant that the MTU clock is just 32768 Hz, and in this
mode the minimum ticks is 5 rather than two.

I think this is simply so that there is enough time
for the register write to propagate through the
interconnect to the registers.

Signed-off-by: Linus Walleij 
Signed-off-by: Daniel Lezcano 
Link: https://lore.kernel.org/r/20200628220153.67011-1-linus.walleij@linaro.org

clocksource: Replace setup_irq() by request_irq()

2020-02-27T11:15:24+00:00

request_irq() is preferred over setup_irq(). The early boot setup_irq()
invocations happen either via 'init_IRQ()' or 'time_init()', while
memory allocators are ready by 'mm_init()'.

Per tglx[1], setup_irq() existed in olden days when allocators were not
ready by the time early interrupts were initialized.

Hence replace setup_irq() by request_irq().

Seldom remove_irq() usage has been observed coupled with setup_irq(),
wherever that has been found, it too has been replaced by free_irq().

A build error that was reported by kbuild test robot 
in the previous version of the patch also has been fixed.

[1] https://lkml.kernel.org/r/alpine.DEB.2.20.1710191609480.1971@nanos

Signed-off-by: afzal mohammed 
Signed-off-by: Daniel Lezcano 
Link: https://lore.kernel.org/r/91961c77c1cf93d41523f5e1ac52043f32f97077.1582799709.git.afzal.mohd.ma@gmail.com

treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 500

2019-06-19T15:09:55+00:00

Based on 2 normalized pattern(s):

  this program is free software you can redistribute it and or modify
  it under the terms of the gnu general public license version 2 as
  published by the free software foundation

  this program is free software you can redistribute it and or modify
  it under the terms of the gnu general public license version 2 as
  published by the free software foundation #

extracted by the scancode license scanner the SPDX license identifier

  GPL-2.0-only

has been chosen to replace the boilerplate/reference in 4122 file(s).

Signed-off-by: Thomas Gleixner 
Reviewed-by: Enrico Weigelt 
Reviewed-by: Kate Stewart 
Reviewed-by: Allison Randal 
Cc: linux-spdx@vger.kernel.org
Link: https://lkml.kernel.org/r/20190604081206.933168790@linutronix.de
Signed-off-by: Greg Kroah-Hartman

clocksource/drivers/ux500: Drop Ux500 custom SCHED_CLOCK

2018-12-18T21:22:23+00:00

The two drivers used for Ux500 sched_clock use two Kconfig
symbols to select which of the two gets used as sched_clock.

This isn't right: the workaround is trying to make sure that
the NONSTOP timer is used for sched_clock in order to keep
that clock ticking consistently over a suspend/resume
cycle. (Otherwise sched_clock simply stops during suspend
and continues after resume).

This will notably affect any timetstamped debug prints,
so that they show the absolute number of seconds since the
system was booted and does not loose wall-clock time during
suspend and resume as if time stood still.

The real way to fix this problem is to make sched_clock
take advantage of any NONSTOP clock source on the system
and adjust accordingly, not to try to work around this by
using a different sched_clock depending on what system
we are compiling for. This can solve the problem for
everyone instead of providing a local solution.

Cc: Baolin Wang 
Signed-off-by: Linus Walleij 
Signed-off-by: Daniel Lezcano

clocksource/drivers: Rename CLOCKSOURCE_OF_DECLARE to TIMER_OF_DECLARE

2017-06-14T09:58:45+00:00

The CLOCKSOURCE_OF_DECLARE macro is used widely for the timers to declare the
clocksource at early stage. However, this macro is also used to initialize
the clockevent if any, or the clockevent only.

It was originally suggested to declare another macro to initialize a
clockevent, so in order to separate the two entities even they belong to the
same IP. This was not accepted because of the impact on the DT where splitting
a clocksource/clockevent definition does not make sense as it is a Linux
concept not a hardware description.

On the other side, the clocksource has not interrupt declared while the
clockevent has, so it is easy from the driver to know if the description is
for a clockevent or a clocksource, IOW it could be implemented at the driver
level.

So instead of dealing with a named clocksource macro, let's use a more generic
one: TIMER_OF_DECLARE.

The patch has not functional changes.

Signed-off-by: Daniel Lezcano 
Acked-by: Heiko Stuebner 
Acked-by: Neil Armstrong 
Acked-by: Arnd Bergmann 
Acked-by: Matthias Brugger 
Reviewed-by: Linus Walleij

clocksource: Add missing line break to error messages

2017-04-07T14:23:04+00:00

Printing with pr_* functions requires adding line break manually.

Signed-off-by: Rafał Miłecki 
Acked-by: Thierry Reding 
Signed-off-by: Daniel Lezcano

clocksources: Switch back to the clksrc table

2016-06-28T08:19:35+00:00

All the clocksource drivers's init function are now converted to return
an error code. CLOCKSOURCE_OF_DECLARE is no longer used as well as the
clksrc-of table.

Let's convert back the names:
 - CLOCKSOURCE_OF_DECLARE_RET => CLOCKSOURCE_OF_DECLARE
 - clksrc-of-ret              => clksrc-of

Signed-off-by: Daniel Lezcano 

For exynos_mct and samsung_pwm_timer:
Acked-by: Krzysztof Kozlowski 

For arch/arc:
Acked-by: Vineet Gupta 

For mediatek driver:
Acked-by: Matthias Brugger 

For the Rockchip-part
Acked-by: Heiko Stuebner 

For STi :
Acked-by: Patrice Chotard 

For the mps2-timer.c and versatile.c changes:
Acked-by: Liviu Dudau 

For the OXNAS part :
Acked-by: Neil Armstrong 

For LPC32xx driver:
Acked-by: Sylvain Lemieux 

For Broadcom Kona timer change:
Acked-by: Ray Jui 

For Sun4i and Sun5i:
Acked-by: Chen-Yu Tsai 

For Meson6:
Acked-by: Carlo Caione 

For Keystone:
Acked-by: Santosh Shilimkar 

For NPS:
Acked-by: Noam Camus 

For bcm2835:
Acked-by: Eric Anholt

clocksource/drivers/nomadik-mtu: Convert init function to return error

2016-06-28T08:19:25+00:00

The init functions do not return any error. They behave as the following:

  - panic, thus leading to a kernel crash while another timer may work and
       make the system boot up correctly

  or

  - print an error and let the caller unaware if the state of the system

Change that by converting the init functions to return an error conforming
to the CLOCKSOURCE_OF_RET prototype.

Proper error handling (rollback, errno value) will be changed later case
by case, thus this change just return back an error or success in the init
function.

Signed-off-by: Daniel Lezcano

clockevents/drivers/nomadik-mtu: Migrate to new 'set-state' interface

2015-08-10T09:40:34+00:00

Migrate nomadik-mtu driver to the new 'set-state' interface provided by
clockevents core, the earlier 'set-mode' interface is marked obsolete
now.

This also enables us to implement callbacks for new states of clockevent
devices, for example: ONESHOT_STOPPED.

Cc: Linus Walleij 
Signed-off-by: Viresh Kumar 
Signed-off-by: Daniel Lezcano 
Acked-by: Linus Walleij