linux-toradex.git/kernel/time/tick-oneshot.c, branch v6.19

treewide: Update email address

2026-01-11T16:09:11+00:00

In a vain attempt to consolidate the email zoo switch everything to the
kernel.org account.

Signed-off-by: Thomas Gleixner 
Signed-off-by: Linus Torvalds

time: tick-oneshot: Add missing Return and parameter descriptions to kernel-doc

2025-11-14T19:17:44+00:00

Several functions in kernel/time/tick-oneshot.c are missing parameter and
return value descriptions in their kernel-doc comments. This causes
warnings during doc generation.

Update the kernel-doc blocks to include detailed @param and Return:
descriptions for better clarity and to fix kernel-doc warnings.  No
functional code changes are made.

Signed-off-by: Sunday Adelodun 
Signed-off-by: Thomas Gleixner 
Link: https://patch.msgid.link/20251106113938.34693-3-adelodunolaoluwa@yahoo.com

time: Fix various kernel-doc problems

2023-01-03T10:07:58+00:00

Clean up kernel-doc complaints about function names and non-kernel-doc
comments in kernel/time/. Fixes these warnings:

  kernel/time/time.c:479: warning: expecting prototype for set_normalized_timespec(). Prototype was for set_normalized_timespec64() instead
  kernel/time/time.c:553: warning: expecting prototype for msecs_to_jiffies(). Prototype was for __msecs_to_jiffies() instead

  kernel/time/timekeeping.c:1595: warning: contents before sections
  kernel/time/timekeeping.c:1705: warning: This comment starts with '/**', but isn't a kernel-doc comment.
   * We have three kinds of time sources to use for sleep time
  kernel/time/timekeeping.c:1726: warning: This comment starts with '/**', but isn't a kernel-doc comment.
   * 1) can be determined whether to use or not only when doing

  kernel/time/tick-oneshot.c:21: warning: missing initial short description on line:
   * tick_program_event
  kernel/time/tick-oneshot.c:107: warning: expecting prototype for tick_check_oneshot_mode(). Prototype was for tick_oneshot_mode_active() instead

Signed-off-by: Randy Dunlap 
Signed-off-by: Ingo Molnar 
Link: https://lore.kernel.org/r/20230103032849.12723-1-rdunlap@infradead.org

timekeeping, clocksource: Fix various typos in comments

2021-03-22T22:06:48+00:00

Fix ~56 single-word typos in timekeeping & clocksource code comments.

Signed-off-by: Ingo Molnar 
Cc: Thomas Gleixner 
Cc: John Stultz 
Cc: Stephen Boyd 
Cc: Daniel Lezcano 
Cc: linux-kernel@vger.kernel.org

hrtimers/tick/clockevents: Remove sloppy license references

2018-11-23T10:51:21+00:00

"For licencing details see kernel-base/COPYING" and similar license
references have no value over the SPDX identifier. Remove them.

Signed-off-by: Thomas Gleixner 
Acked-by: Kees Cook 
Acked-by: Ingo Molnar 
Acked-by: John Stultz 
Acked-by: Corey Minyard 
Cc: Peter Zijlstra 
Cc: Kate Stewart 
Cc: Philippe Ombredanne 
Cc: Peter Anvin 
Cc: Russell King 
Cc: Richard Cochran 
Cc: "Paul E. McKenney" 
Cc: Nicolas Pitre 
Cc: David Riley 
Cc: Colin Cross 
Cc: Mark Brown 
Link: https://lkml.kernel.org/r/20181031182252.963632760@linutronix.de

time: Add SPDX license identifiers

2018-11-23T10:51:20+00:00

Update the time(r) core files files with the correct SPDX license
identifier based on the license text in the file itself. The SPDX
identifier is a legally binding shorthand, which can be used instead of the
full boiler plate text.

This work is based on a script and data from Philippe Ombredanne, Kate
Stewart and myself. The data has been created with two independent license
scanners and manual inspection.

The following files do not contain any direct license information and have
been omitted from the big initial SPDX changes:

  timeconst.bc: The .bc files were not touched
  time.c, timer.c, timekeeping.c: Licence was deduced from EXPORT_SYMBOL_GPL

As those files do not contain direct license references they fall under the
project license, i.e. GPL V2 only.

Signed-off-by: Thomas Gleixner 
Acked-by: Kees Cook 
Acked-by: Ingo Molnar 
Acked-by: John Stultz 
Acked-by: Corey Minyard 
Cc: Peter Zijlstra 
Cc: Kate Stewart 
Cc: Philippe Ombredanne 
Cc: Russell King 
Cc: Richard Cochran 
Cc: Nicolas Pitre 
Cc: David Riley 
Cc: Colin Cross 
Cc: Mark Brown 
Cc: H. Peter Anvin 
Cc: Paul E. McKenney 
Link: https://lkml.kernel.org/r/20181031182252.879109557@linutronix.de

time: Remove useless filenames in top level comments

2018-11-23T10:51:20+00:00

Remove the pointless filenames in the top level comments. They have no
value at all and just occupy space. While at it tidy up some of the
comments and remove a stale one.

Signed-off-by: Thomas Gleixner 
Acked-by: Nicolas Pitre 
Acked-by: Kees Cook 
Acked-by: Ingo Molnar 
Acked-by: John Stultz 
Acked-by: Corey Minyard 
Cc: Peter Zijlstra 
Cc: Kate Stewart 
Cc: Philippe Ombredanne 
Cc: Peter Anvin 
Cc: Russell King 
Cc: Richard Cochran 
Cc: "Paul E. McKenney" 
Cc: David Riley 
Cc: Colin Cross 
Cc: Mark Brown 
Link: https://lkml.kernel.org/r/20181031182252.794898238@linutronix.de

clockevents: Fix kernel messages split across multiple lines

2018-04-17T15:18:04+00:00

Convert the clockevents driver from old-style printk() to pr_info() and
pr_cont(), to fix split kernel messages like below:

    Clockevents: could not switch to one-shot mode:
     dummy_timer is not functional.

Signed-off-by: Geert Uytterhoeven 
Signed-off-by: Thomas Gleixner 
Cc: Frederic Weisbecker 
Link: https://lkml.kernel.org/r/1522942018-14471-1-git-send-email-geert%2Brenesas@glider.be

clockevents: Update clockevents device next_event on stop

2017-11-01T17:20:17+00:00

clockevent_device::next_event holds the next timer event of a clock event
device. The value is updated in clockevents_program_event(), i.e. when the
hardware timer is armed for the next expiry.

When there are no software timers armed on a CPU, the corresponding per CPU
clockevent device is brought into ONESHOT_STOPPED state, but
clockevent_device::next_event is not updated, because
clockevents_program_event() is not called.

So the content of clockevent_device::next_event is stale, which is not an
issue when real hardware is used. But the hrtimer broadcast device relies
on that information and the stale value causes spurious wakeups.

Update clockevent_device::next_event to KTIME_MAX when it has been brought
into ONESHOT_STOPPED state to avoid spurious wakeups. This reflects the
proper expiry time of the stopped timer: infinity.

[ tglx: Massaged changelog ]

Signed-off-by: Prasad Sodagudi 
Signed-off-by: Thomas Gleixner 
Cc: viresh.kumar@linaro.org
Link: https://lkml.kernel.org/r/1509043042-32486-1-git-send-email-psodagud@codeaurora.org

ktime: Get rid of the union

2016-12-25T16:21:22+00:00

ktime is a union because the initial implementation stored the time in
scalar nanoseconds on 64 bit machine and in a endianess optimized timespec
variant for 32bit machines. The Y2038 cleanup removed the timespec variant
and switched everything to scalar nanoseconds. The union remained, but
become completely pointless.

Get rid of the union and just keep ktime_t as simple typedef of type s64.

The conversion was done with coccinelle and some manual mopping up.

Signed-off-by: Thomas Gleixner 
Cc: Peter Zijlstra