Norman Feske 49481dd3fb timer: restore semantics of periodic timeout 0 ... The 'Timer::Session::trigger_periodic' RPC function used to accept 0 as a way to de-schedule the periodic processing. Several components such as nitpicker relied on this special case. In "timeout: rework timeout framework", the value of zero was silently clamped to 1, which has the opposite effect: triggering signals at the maximum rate. This results in a visible effect in Sculpt where the leitzentrale-nitpicker instance produces a constant load of 2% CPU time. This patch restores the original timer semantics by - Documenting it in timer_session.h, - Handling the case explicitly in the timer implementation, and - Replacing the silent clamping of the unexpected value 0 passed to the timeout framework by a diagnostic error message. Issue #3884		2021-04-20 12:03:03 +02:00
..
epit	base: remove SPEC variables of boards (fix #3971)	2021-01-25 13:58:09 +01:00
fiasco	base: use Mutex/Blockade	2020-04-17 12:40:12 +02:00
gpt	timeout: rework timeout framework	2020-10-09 13:35:56 +02:00
include	timer: restore semantics of periodic timeout 0	2021-04-20 12:03:03 +02:00
periodic	timeout: rework timeout framework	2020-10-09 13:35:56 +02:00
pit	timeout: rework timeout framework	2020-10-09 13:35:56 +02:00
main.cc	Move timer from os to base repository	2019-01-14 12:33:57 +01:00
target.inc	Move timer from os to base repository	2019-01-14 12:33:57 +01:00