[riot-notifications] [RIOT-OS/RIOT] doc: XTIMER_BACKOFF inconsistency (#11522)
notifications at github.com
Fri May 17 15:04:26 CEST 2019
> So from my point of view it is not a problem of documentation, but of proper casting.
It is a problem of documentation. The fact that it is ambiguous doesn't make it clear if when implemented it was thought of as a per board configuration variable in ticks or us. I don't know the details of the concept behind the implementation. That being said, you are right 'us' is more intuitive. I would like @kaspar030 input on this since its his implementation.
> I'd even prefer if this value of 30us is reviewed properly, to determine a more exact bound.
+1, and the reasoning for it
> Also I realized there are varying redefinitions of XTIMER_BACKOFF for different boards. Assuming the developers who set this values stuck to the documentation, all those values are supposed to be microseconds, not ticks and hence should be used accordingly, instead of bloating the documentation.
Going back to this, looking at discussion thread https://github.com/RIOT-OS/RIOT/issues/7347 the reasoning behind the value doesn't seem to be more than works/doesn't work. The fact that the discussion makes sense when comparing XTIMER_BACKOFF to 'us' is only because the timer in most cases is 1Mhz. But this is not always the case as in some 8 bit MCU or when using slow low power timers (frdm-kw41z).
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the notifications