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.

Sign up for GitHub

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

Jump to bottom

(Re)add a way to ask which GPIO pin caused an interrupt #923

Closed
bjoernQ opened this issue Nov 10, 2023 · 2 comments · Fixed by #929
Closed

(Re)add a way to ask which GPIO pin caused an interrupt #923

bjoernQ opened this issue Nov 10, 2023 · 2 comments · Fixed by #929
Labels
peripheral:gpio GPIO peripheral

Comments

@bjoernQ
Copy link
Contributor

bjoernQ commented Nov 10, 2023

We had it before but somehow it got lost - without it's very convenient to write a GPIO interrupt handler which is listening on multiple pins
@noahbliss
Copy link

Total noob working through rust on esp and am ashamed to admit I spent half my day trying to figure out what I was doing wrong haha. Just my $0.02 that this would be extremely helpful. I'm over on the xtensa side of the yard if it makes any difference.

@bjoernQ
Copy link
Contributor Author

bjoernQ commented Nov 13, 2023

Sorry to hear you lost half a day with this - hope we will fix this soon

@bjoernQ bjoernQ mentioned this issue Nov 13, 2023
Merged
@github-project-automation github-project-automation bot moved this from Todo to Done in esp-rs Nov 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
peripheral:gpio GPIO peripheral
Projects
esp-rs
Archived in project
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Re-add API to get a GPIO's interrupt status bit bjoernQ/esp-hal
3 participants
@jessebraham @bjoernQ @noahbliss