-
Notifications
You must be signed in to change notification settings - Fork 2.1k
drivers/bmx055: adapt to new i2c api #9466
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
Conversation
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.
How does this driver even works ? I don't see any call to i2c_acquire/i2c_release.
Any clue captain ?
mhm only adapted the existing calls, it works on master with the old API even without the acquire. And if only one I2c device is present it should be fine without acquire and release. However, you're right it will get tricky if multiple i2c devs are present. Should I fix this? |
I would love to test this device on master. I don't think this driver works for all MCUs (like SAM0 based). Shame I don't own this one...
Hum, I think it's safe to fix it. So yes please go ahead :) |
@dylad added acquire and release calls. Could be improved but would need more restructuring, but wanted to keep it simple (for now) to get the I2C rework done. |
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.
It would be great to have someone test it or maybe @smlng you can share some outputs if you find some times
add missing i2c_acquire and i2c_release calls to properly guard i2c read and write operations.
Here some output from the test app:
|
drivers/bmx055: adapt to new i2c api
drivers/bmx055: adapt to new i2c api
drivers/bmx055: adapt to new i2c api
Contribution description
captain obvious to the rescue, i.e. see title
Issues/PRs references
#6577