[riot-notifications] [RIOT-OS/RIOT] sys/xtimer: make xtimer_mutex_lock_timeout() actually use us arg (#11165)

Kaspar Schleiser notifications at github.com
Tue Mar 12 16:21:25 CET 2019


### Contribution description

The docs state that ```xtimer_mutex_lock_timeout()``` gets an microsecond timeout, but then it uses the internal ```_xtimer_set64()``` to set the timer, which expects xtimer ticks. This breaks if ticks are not 1us.

### Testing procedure

Try the sema tests on hifive1, which uses 32768Hz ticks.

### Issues/PRs references

#5608
You can view, comment on, or merge this pull request online at:

  https://github.com/RIOT-OS/RIOT/pull/11165

-- Commit Summary --

  * sys/xtimer: make xtimer_mutex_lock_timeout() actually use us arg

-- File Changes --

    M sys/xtimer/xtimer.c (2)

-- Patch Links --

https://github.com/RIOT-OS/RIOT/pull/11165.patch
https://github.com/RIOT-OS/RIOT/pull/11165.diff

-- 
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/11165
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20190312/50ec6b73/attachment.html>


More information about the notifications mailing list