adding conversion trigger and raw data read functions #7
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Author
|
Ugh why does the linting have to be like that |
|
If you fix the linting I'll take a look at this; hard to look at the changes since the diff is mostly formatting. |
linguini1
force-pushed
the
ads1115_conversion_trigger
branch
from
086631f to
9fd69ed
Compare
Since the ADS1115 has a relative slow conversion rate, this additional ioctl command makes it possible to trigger a conversion before reading the reading the conversion result, allowing the user to perform other computation in between instead of waiting for the conversion time to complete. It improves sampling time. Signed-off-by: Matteo Golin <matteo.golin@gmail.com>
linguini1
force-pushed
the
ads1115_conversion_trigger
branch
from
9fd69ed to
ee72e82
Compare
|
Opening to upstream |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Note: Please adhere to Contributing Guidelines.
Summary
Update this section with information on why change is necessary,
what it exactly does and how, if new feature shows up, provide
references (dependencies, similar problems and solutions), etc.
Impact
Update this section, where applicable, on how change affects users,
build process, hardware, documentation, security, compatibility, etc.
Testing
Update this section with details on how did you verify the change,
what Host was used for build (OS, CPU, compiler, ..), what Target was
used for verification (arch, board:config, ..), etc. Providing build
and runtime logs from before and after change is highly appreciated.