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

Using multiple GPIO interrupts is not supported yet (e.g. 4 on P4) #2650

Open
Tracked by #2492
bjoernQ opened this issue Dec 2, 2024 · 5 comments
Open
Tracked by #2492

Using multiple GPIO interrupts is not supported yet (e.g. 4 on P4) #2650

bjoernQ opened this issue Dec 2, 2024 · 5 comments
Labels
peripheral:gpio GPIO peripheral

Comments

@bjoernQ
Copy link
Contributor

bjoernQ commented Dec 2, 2024

No description provided.

@bugadani
Copy link
Contributor

bugadani commented Dec 9, 2024

The P4 is slightly weird in that it allows listening for a single event, but can route it to any or all of the 4 interrupt signals. We'll have to make sure we don't end up with a confusing API. I also suggest a separate, cfg-gated listen function to set up listening, so that users of the earlier/simpler MCUs don't have to deal with a single-variant enum (or EnumSet...).

@tom-borcin tom-borcin changed the title Using multiple GPIO interrupts is supported yet (e.g. 4 on P4) Using multiple GPIO interrupts is not supported yet (e.g. 4 on P4) Dec 18, 2024
@tom-borcin tom-borcin added the investigation Not needed for 1.0, but don't know if we can support without breaking the driver. label Dec 18, 2024
@MabezDev
Copy link
Member

We're not stabilizing interrupts for 1.0 (context: #2900 (comment)), so we can't punt this till post 1.0

@MabezDev MabezDev removed 1.0-blocker investigation Not needed for 1.0, but don't know if we can support without breaking the driver. labels Jan 10, 2025
@tommasoclini

This comment was marked as off-topic.

@MabezDev
Copy link
Member

@tommasoclini please file a separate issue.

@tommasoclini
Copy link
Contributor

I will, should i attach the whole project with Cargo.toml and Cargo.lock, or is the code snippet fine?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
peripheral:gpio GPIO peripheral
Projects
Status: Todo
Development

No branches or pull requests

5 participants