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

imx: clear general purpose pending interrupt #6658

Conversation

iuliana-prodan
Copy link
Contributor

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]

@lgirdwood
Copy link
Member

SOFCI TEST

@lgirdwood
Copy link
Member

@iuliana-prodan can you check here, this PR is breaking the qemu boot on IMX ?

@iuliana-prodan
Copy link
Contributor Author

iuliana-prodan commented Nov 25, 2022

@iuliana-prodan can you check here, this PR is breaking the qemu boot on IMX ?

I'm looking into it.
Most probably is a qemu problem, since this is working on the actual hw.

@lgirdwood
Copy link
Member

@iuliana-prodan any update ?

@iuliana-prodan
Copy link
Contributor Author

@iuliana-prodan any update ?

Sorry for the late reply, we had some days off (National day in Romania).
I've created a PR to fix qemu boot: #6713

@lgirdwood
Copy link
Member

@iuliana-prodan any update ?

Sorry for the late reply, we had some days off (National day in Romania). I've created a PR to fix qemu boot: #6713

Qemu update merged, not sure if container needs a manual update or not. Have asked.

@lgirdwood
Copy link
Member

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]>
@iuliana-prodan iuliana-prodan force-pushed the iprodan/fw-boot-failure-after-soft-reboot branch from 311e742 to 2748d24 Compare December 5, 2022 15:03
@dbaluta dbaluta merged commit 4a9a99a into thesofproject:main Dec 5, 2022
@marc-hb
Copy link
Collaborator

marc-hb commented Dec 5, 2022

yes docker updates are always manual (and generally rare). See discussions in

@iuliana-prodan iuliana-prodan deleted the iprodan/fw-boot-failure-after-soft-reboot branch May 4, 2023 13:55
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.

5 participants