[riot-notifications] [RIOT-OS/RIOT] RFC: Change of sensor and actoator API & auto initialization (#11826)

Juan I Carrano notifications at github.com
Fri Jul 12 15:46:01 CEST 2019


I believe we should find a way to have _less_ things in auto_init instead of _more_.

Right there, in the example you cite (DHT) there is code in `sys/auto_init`. That code interacts with `sys/saul_reg` and `drivers/dht`. So not only does it cross module boundaries, it crosses the sys-drivers boundary. This is not specific to DHT and is a general feature of auto_init code.

Would having access to the lowel-level device handle through saul work, or do we also require that the module be auto initialized when saul is not being used?

I think the first one is a not-pretty but acceptable work-around. The second would be adding a tons of stuff to auto_init and while it would not be better or worse than what is now, it would add to pile that we should clean up some day.

-- 
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/11826#issuecomment-510892185
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20190712/91f44ad8/attachment.html>


More information about the notifications mailing list