Skip to content
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

Tidy up Camera according to latest guidelines #3237

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

Dominaezzz
Copy link
Collaborator

Thank you for your contribution!

We appreciate the time and effort you've put into this pull request.
To help us review it efficiently, please ensure you've gone through the following checklist:

Submission Checklist 📝

  • I have updated existing examples or added new ones (if applicable).
  • I have used cargo xtask fmt-packages command to ensure that all changed code is formatted correctly.
  • My changes were added to the CHANGELOG.md in the proper section.
  • I have added necessary changes to user code to the Migration Guide.
  • My changes are in accordance to the esp-rs developer guidelines

Extra:

Pull Request Details 📖

Description

All Camera pins are now configured using with_*() methods.
Some implicit config has now been made explicit to make this change possible.

Not sure if there's a preference between with_vertical_sync and with_vsync but I chose the latter for now. (Happy to change it).

Testing

Ran the qa-test and I'm entrusting the HIL test to CI.

@Dominaezzz Dominaezzz mentioned this pull request Mar 9, 2025
6 tasks
+ config.with_enable_2byte_mode(true) // If you were previously using RxSixteenBits
)?;

+ camera.with_data0(peripherals.GPIO11).with_data1(peripherals.GPIO9).with_dataX();

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this isn't so much about the PR and more about an issue i have with the dev. guidelines which is very well outlined in this PR: in the current API you have to use all data pins. but with the new API introduces with this PR there's now the real risk that you forget to pass one of the data pins. finding this bug is much more cumbersome with the new API.

what is the rationale for this design choice? have these downsides been considered and what can be done to mitigate them?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants