[riot-notifications] [RIOT-OS/RIOT] sys/xtimer: improve spin define handling/documentation (#11546)

Semjon Kerner notifications at github.com
Fri May 24 11:14:10 CEST 2019


Thanks for testing @cladmi. I reproduced the failures on nucleo-f103rb for `tests/xtimer_periodic_wakeup` and `xtimer_usleep_short`. I reconfigured the boards config for `XTIMER_BACKOFF` in `boards/common/nucleo/include/board_nucleo.h` for STM32F1 family from **5** to **19** (confirmed as smallest working with the broken tests).

So I guess, this would be the correct approach to solve the issues for all boards that redefine `XTIMER_HZ`.

Question is now, is it worth the effort to reevaluate best fitting backoff values or is this PR in vain and XTIMER_BACKOFF should be used as ticks instead, as it seems to be used as ticks in most cases?

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/RIOT-OS/RIOT/pull/11546#issuecomment-495535966
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20190524/d556c2d2/attachment.html>


More information about the notifications mailing list