1. 04 Feb, 2019 2 commits
    • Philippe Gerum's avatar
      drivers/gpio: provide optional timestamped readouts · d35f3e41
      Philippe Gerum authored
      
      
      In timestamping mode, read() returns the timestamp of the latest event
      receipt on the pin based on CLOCK_MONOTONIC, along with the pin
      state. This is an optional pin readout mode controlled by the
      GPIO_RTIOC_TS request, e.g.:
      
      struct rtdm_gpio_readout rdo;
      int ret, on, val;
      
      on = 1;
      ret = ioctl(pinfd, GPIO_RTIOC_TS, &on);
      ret = read(pinfd, &rdo, sizeof(rdo));
      /* pin state changed to rdo.value at time rdo.timestamp */
      
      on = 0;
      ret = ioctl(pinfd, GPIO_RTIOC_TS, &on);
      ret = read(pinfd, &val, sizeof(val));
      /* pin state changed to value (time of change unspecified) */
      
      By default, timestamping mode is disabled, which corresponds to the
      original behavior.
      Signed-off-by: Philippe Gerum's avatarPhilippe Gerum <rpm@xenomai.org>
      Signed-off-by: Jan Kiszka's avatarJan Kiszka <jan.kiszka@siemens.com>
      d35f3e41
    • Philippe Gerum's avatar
      testsuite/smokey: posix_clock: prevent false positive in time-dependent test · 99348f65
      Philippe Gerum authored
      
      
      clock_decrease_after_periodic_timer_first_tick checks that periodic
      interval timers based on CLOCK_REALTIME are not (pathologically)
      affected by the epoch going backwards.
      
      To this end, we measure the actual time observed between two ticks of
      a periodic timer based on CLOCK_REALTIME with a call to
      clock_settime() injecting a negative offset in between, equivalent to
      five ticks.
      
      Due to processing delays induced by clock_settime() and other latency,
      we could observe a duration which exceeds a tick by a few tenths of
      microseconds. Since we can't anticipate the amount of latency
      involved, let's accept a longer delay of at most two ticks.
      
      This is still correct from the standpoint of the test, which verifies
      that no correlation exists between the clock offset injected by
      clock_settime() and the delay until the next tick generated by the
      affected clock.
      Signed-off-by: Philippe Gerum's avatarPhilippe Gerum <rpm@xenomai.org>
      Signed-off-by: Jan Kiszka's avatarJan Kiszka <jan.kiszka@siemens.com>
      99348f65
  2. 16 Jan, 2019 3 commits
  3. 14 Jan, 2019 1 commit
  4. 09 Jan, 2019 1 commit
  5. 20 Dec, 2018 2 commits
  6. 14 Dec, 2018 1 commit
  7. 06 Dec, 2018 1 commit
  8. 30 Nov, 2018 5 commits
  9. 28 Nov, 2018 2 commits
  10. 23 Nov, 2018 2 commits
  11. 16 Nov, 2018 13 commits
  12. 06 Nov, 2018 3 commits
  13. 05 Nov, 2018 1 commit
  14. 31 Oct, 2018 2 commits
  15. 28 Oct, 2018 1 commit