-
Notifications
You must be signed in to change notification settings - Fork 19
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
Added interrupt feature #10
base: master
Are you sure you want to change the base?
Conversation
Memory usage change @ b82d9c6
Click for full report table
Click for full report CSV
|
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.
are all this function need to enable the interrupt? if all of them are required it is better put all inside one unique API, if the API can be used alone and have effect that are not involved with interrupt(i mean that the user could do some action non involved with interrupt), of course if you implement a enable interrupt you shall do a disable interrupt that do the inverse action of all these API
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.
no this not works we already used this and was changed here the commit:
d3d6bac
the reasons as mentioned by the comment is that the correct flow have to:
If the ONE_SHOT bit in CTRL_REG2 (11h) is set to '1', One-shot mode is triggered and a new acquisition starts when it is required. Enabling this mode is possible only if the device was previously in power-down mode (ODR bits set to '000'). Once the acquisition is completed and the output registers updated, the device automatically enters in power-down mode. ONE_SHOT bit self-clears itself.
Ping ... @marqdevx 👋 😉 |
No description provided.