1. 07 Mar, 2021 3 commits
    • Jan Kiszka's avatar
      ipipe: Clean up per-CPU host timers on hotplug · eefe5e62
      Jan Kiszka authored
      
      
      When a CPU is unplugged, make sure to drop all per-CPU ipipe timer
      devices when removing the CPU. Otherwise, we will corrupt the device
      list when re-registering the host timer on CPU onlining.
      Signed-off-by: Jan Kiszka's avatarJan Kiszka <jan.kiszka@siemens.com>
      eefe5e62
    • Philippe Gerum's avatar
      ipipe: tick: cap timer_set op to device supported max · 88d636d3
      Philippe Gerum authored and Jan Kiszka's avatar Jan Kiszka committed
      At this chance, switch the min_delay_tick value to unsigned long to
      match the corresponding clockevent definition.
      88d636d3
    • Philippe Gerum's avatar
      ipipe: add out-of-band tick device · e0cecb8d
      Philippe Gerum authored and Jan Kiszka's avatar Jan Kiszka committed
      
      
      The out-of-band tick device manages the timer hardware by interposing
      on selected clockevent handlers transparently, so that a client domain
      (e.g. a co-kernel) eventually controls such hardware for scheduling
      the high-precision timer events it needs to. Those events are
      delivered to out-of-hand activities running on the head stage,
      unimpeded by (only virtually) interrupt-free sections of the regular
      kernel code.
      
      This commit introduces the generic API for controlling the out-of-band
      tick device from a co-kernel. It also provides for the internal API
      clock event chip drivers should use for enabling high-precision
      timing for their hardware.
      Signed-off-by: Jan Kiszka's avatarJan Kiszka <jan.kiszka@siemens.com>
      e0cecb8d