_camera.i2c_read()
and _camera.i2c_write()
#281
Merged
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.
This patch should allow sending custom I2C commands to the camera for the various purposes:
These do not need to be documented or even work now: this is the point of the patch: allow turning on features already present in the device, simply by documenting them.
As long as they do not damage is done by using these functions, they could be shipped.
The I2C address is limited to the camera, which avoids any risk of communicating with any other device.]
Usage:
The mask is hard-coded to 0xFF, which can be adjusted by calling
i2c_read
, masking, then callingi2c_write
.I did not test this all yet.