-
Notifications
You must be signed in to change notification settings - Fork 319
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
imx: clear general purpose pending interrupt #6658
imx: clear general purpose pending interrupt #6658
Conversation
SOFCI TEST |
@iuliana-prodan can you check here, this PR is breaking the qemu boot on IMX ? |
I'm looking into it. |
@iuliana-prodan any update ? |
Sorry for the late reply, we had some days off (National day in Romania). |
Qemu update merged, not sure if container needs a manual update or not. Have asked. |
SOFCI TEST |
Clear general purpose pending interrupt before enabling interrupts between host and DSP. The GIPn bit, from MU Status Register is cleared by writing it as “1” in order to de-assert the interrupt request source at the interrupt controller. This fixes a fw loading failure after a soft reboot caused by GIP bit that was 1. The problem was the MU which triggered endless interrupts causing timeout on Kernel side, which was waiting for FW_READY message. Signed-off-by: Iuliana Prodan <[email protected]>
311e742
to
2748d24
Compare
yes docker updates are always manual (and generally rare). See discussions in |
Clear general purpose pending interrupt
before enabling interrupts between host and DSP.
The GIPn bit, from MU Status Register is cleared
by writing it as “1” in order to de-assert the
interrupt request source at the interrupt controller.
This fixes a fw loading failure after a soft reboot caused by GIP bit that was 1.
The problem was the MU which triggered endless interrupts causing timeout on Kernel side, which was waiting for FW_READY message.
Signed-off-by: Iuliana Prodan [email protected]