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

MPFS_GPIO Level-triggered Interrupt Bug #539

Open
Eoin-Dickson opened this issue Oct 24, 2023 · 1 comment
Open

MPFS_GPIO Level-triggered Interrupt Bug #539

Eoin-Dickson opened this issue Oct 24, 2023 · 1 comment

Comments

@Eoin-Dickson
Copy link

Description

There is a problem in how to the GPIOInterruptManager is dealing with level-triggered interrupts for the MPFS_GPIO peripheral. According to the GPIO SAC specifications when the input that is causing a level-triggered interrupt is removed, then the interrupt should de-assert by itself.

Expected behaviour

Once the input causing a level-triggered interrupt is removed then the interrupt should go back to 0

How to reproduce?

I have tried this with a local project and it results in the interrupt staying high rather than de-asserting itself.

Environment

Windows
Renode 1.14.0

Do you plan to address this issue and file a PR?

Yes, I will create a PR for this issue

@PiotrZierhoffer
Copy link
Member

Thanks a lot for the PR: renode/renode-infrastructure#89

We'll review it internally and get back to you with feedback.

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

No branches or pull requests

2 participants