New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sys/auto_init: Fixed initialization of sht1x [backport 2018.10] #10289
Conversation
- the driver for sht1x is initialized two times - the second initialization is done only when SAUL is used, but sht1x needs to be initialized in any case. (SAUL registration is also done there, but only when SAUL is actually being used.) This commit fixes both.
The auto initialization of the sht1x module differs from the initialization of other sensors, but previously no documentation pointed that out. This lack of documentation led to a bug being introduced. This commit provides the previously missing documentation.
(I updated the title)... and description |
looks ok (commits are the same) |
@cladmi have you seen this before? I've been getting this error lately. It's triggered randomly :/ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
untested ACK
this was against |
That just looks like the |
It has appeared in several PRs. Even with doc changes :/ |
Backport of #10267
Contribution description
Commit cef81a1 introduced two bugs:
to be initialized in any case. (SAUL registration is also done there, but
only when SAUL is actually being used.)
This commit fixes both.
Testing procedure
E.g. use
examples/default
on a board that features an SHT1x sensor, e.g. the MSB-A2. Prior to this PR RIOT will not boot due to the double initialization, with this PR applied RIOT will boot again.