[riot-notifications] [RIOT-OS/RIOT] Proposal: eSAUL - Extended Sensor Actuator Uber Layer (#14121)

Marian Buschsieweke notifications at github.com
Mon May 25 16:28:02 CEST 2020


> The receiver would receive just an indication

That indication needs to be implemented somehow. `core_msg` is widely used, very stable and quite efficient, so that IMO would be a suitable way to implement that indication. Still, the message bus on top is quite new and not yet widely used and as thouroghly tested, but it is a rather slim layer on top. And it is not too difficult to image use cases for multiple subscribers for a single sensor. (E.g. a smart watch with the UI code being one subscriber and a CoAP interface to it being a second subscriber. Or a smart media station with the UI again one subscriber and CoAP interface the second.)

I like the idea to subscribe for individual sensors instead of having one global bus (or other IPC mechanism), as no filtering of messages (or indications) is needed. However, most hardware has few sensors and actuators, so filtering shouldn't be too expensive CPU wise. And only having to allocate the state one subscription per subscribers safes some RAM. So this is a trade-off.

-- 
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/issues/14121#issuecomment-633598112
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20200525/c381ac0d/attachment.htm>


More information about the notifications mailing list