[riot-notifications] [RIOT-OS/RIOT] Proposal: eSAUL - Extended Sensor Actuator Uber Layer (#14121)
notifications at github.com
Mon May 25 17:08:15 CEST 2020
> In a message approach (as I understand, no matter whether regular msg or msg bus), you might lose the last messages.
This might not be an issue. If the message contains a pointer to the `saul_reg_t` and not the actual value, the subscriber will still need to manually read the actual value. In that case the subscriber will always have the lasted value and will potentially loose intermediate ones.
> In xtimer, we're offering several ways for an event receiver to set itself up -- as a message, as a flag, at a mutex or through a signal.
>From the high level perspective this is true. But from the low level perspective xtimer will always call a callback function in interrupt context. There are utility functions that implement well-known callback functions that will in a second stage wake up a thread, unlock a mutex, send message, ...
I think we should do the same here: Implement only one IPC mechanism that fits the standard use case best. If more are indeed needed, those mechanisms can provided as utility functions on top.
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