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

Re-add API to get a GPIO's interrupt status bit #929

Merged
merged 2 commits into from
Nov 13, 2023

Conversation

bjoernQ
Copy link
Contributor

@bjoernQ bjoernQ commented Nov 13, 2023

Fixes #923

No examples added / changed. I could use it in the gpio_interrupt.rs example (although not needed there) - not sure if that will help or confuse users

Copy link
Member

@MabezDev MabezDev left a comment

Choose a reason for hiding this comment

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

LGTM, thanks!

@bjoernQ bjoernQ merged commit 98a52ea into esp-rs:main Nov 13, 2023
17 checks passed
@noahbliss
Copy link

An example would be super helpful if it isn't too much of a hassle. Something like a 2 button, 1 led demo where button 1 turns it on, button 2 turns it off.

@bjoernQ
Copy link
Contributor Author

bjoernQ commented Nov 14, 2023

Maybe such an example would fit even better into the no-std training book: https://github.com/esp-rs/no_std-training together with some more explanation

@bjoernQ bjoernQ deleted the gpio-interrupt-status-check-api branch November 26, 2024 08:42
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.

(Re)add a way to ask which GPIO pin caused an interrupt
3 participants