[riot-notifications] [RIOT-OS/RIOT] core: Added thread_signal & thread_await_signal (#11006)

Marian Buschsieweke notifications at github.com
Wed Feb 13 07:43:31 CET 2019


> can't this be done with thread flags?

Yes. Also an event queue and likely a cond could be used for that when investing significant work and paying more overhead. The point is that this approach is more lightweight in the backend and requires less code to be written to use it for its use case.

> or, a mutex?

I think that unlocking a mutex from ISR that was locked in thread context would work technicality in RIOT. I have not looked at that. But the concept of a mutex does not allow it to be unlocked from a different context than it was locked. So even if abusing the mutex for this would work here, it will make future changes of the mutex internals very difficult, when not only legitimate users but also abusers of the API need to be taken in mind.

-- 
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/11006#issuecomment-463079299
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20190212/11f24d5b/attachment-0001.html>


More information about the notifications mailing list