[riot-notifications] [RIOT-OS/RIOT] cpu/atmega_common: RTT and RTC support (#8842)

ZetaR60 notifications at github.com
Thu Apr 25 17:44:33 CEST 2019


@jcarrano 
> Now, @ZetaR60, what is not clear to me is whether the RTT/RTC functions are safe to call from within an interrupt. Reading the code suggests it's not as the overflow would not get handled immediately. If that is correct, it should be documented as a limitation.

My latest commits should fix this issue. I _believe_ that all code is now safe from timer events, other ISRs interrupting the current thread, and running the code with interrupts disabled or in ISR mode. It is _not_ safe from concurrent access by multiple threads, except in the case where only state reads are occurring. However, so far as I can tell this is not generally expected of RIOT APIs, and it can be made concurrent access safe by disabling ISRs during access (like everything else).

-- 
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/8842#issuecomment-486728114
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20190425/d4a5a73e/attachment.html>


More information about the notifications mailing list